Cli: Unable to source:retrieve MutingPermisionSet

Created on 10 Mar 2020  路  12Comments  路  Source: forcedotcom/cli

Summary

_A Muting Permission Set in a Permission Set Group in a sandbox cannot be retrieved by source:retrieve _.

Steps To Reproduce:

  1. Create a Muting Permission Set in a sandbox
  2. Try retrieving it by sfdx force:source:retrieve -m "MutingPermissionSet:permission_set_api_name"
  3. The command failed with "cannot read property 'metadataName' of undefined"
  4. Org Browser can see the permission set but retrieving it ended up with the same result (not surprisingly)

Screen Shot 2020-03-08 at 11 49 35 PM

Additional information - Environment

SFDX CLI Version:
7.49.1
SFDX plugin Version:
48.4.1
OS and version:
Windows 10

bug waiting for internal reply

Most helpful comment

We're working on a fix for this now and plan to have it included in our next release

All 12 comments

Verifies it fails with force:source:pull as well.
image

Additional Information - Environment

SFDX CLI Version:
7.49.1
SFDX plugin Version:
48.4.1
OS and version
Mac 10.14.6

@bingwang0 we are going to investigate thank you

I assume it's not that easy to have a "CLI supported" column in the Metadata Coverage Report ?

@FabienTaillon sadly no, we have had internal discussions, but it is a lot more work than it would seem.

Also, MutingPermissionSet is listed as supported by the Metadata API, so letting aside the CLI, shouldn't this mean that it should be documented here, and available through at least a package.xml ?

Or is it just a bug on the API side, it's listed as available in the Metadata API but it's not ?

Hi there, when do you plan to support muted permission sets please? This ticket is a sleeping beauty ;-)

Going on 9 months now, is there an update on this? We just got bit by the gap in functionality.

Hey, @clairebianchi. Any ETA on this by chance?

We're working on a fix for this now and plan to have it included in our next release

Is this fix for retrieve|pull only command or the deploy|push will also be fixed?

As for a side note. I used MutingPermissionSets on project and we put them in separate metaDataApi folder and used mdapi:deploy /retrive for them

Given the fix, and the comments (seems to work for all operations) I'm closing this one. Someone reopen if you still see problems with mutingPermSets

Was this page helpful?
0 / 5 - 0 ratings