Unable to source:retrieve MutingPermisionSet

[bingwang0]

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)

Additional information - Environment

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

[anthonyberan]

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

Additional Information - Environment

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

[clairebianchi]

@bingwang0 we are going to investigate thank you

[FabienTaillon]

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

[clairebianchi]

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

[FabienTaillon]

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 ?

[SalesforcePetr]

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

[Daniel-Dragon]

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

[SCWells72]

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

[mdonnalley]

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

[steals]

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

[ytiq]

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

[mshanemc]

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

[rajesh-kemisetti]

I’m seeing this issue still reproducible and I have re tried after doing sfdx update and seeing the Same error.
I see the issue was closed but it’s not clear whether it was fixed and if it worked for anyone.

[dieffrei]

@mshanemc can you reopen this issue?
I agree with @rajesh-kemisetti this issue still happening even updating to the latest cli version.
CC: @clairebianchi

[shetzel]

@rajesh-kemisetti @dieffrei - what version of the salesforcedx plugin are you using? If you're pinned to an old version you won't get the updates. Multiple people on the team can not reproduce this issue after following the steps from the original post. If there are different steps to reproduce this please post what they are. Another option for force:source:retrieve and force:source:deploy is to use the VS Code extension which currently (but not for long) uses a different library for those commands.

[dieffrei]

@shetzel thank you for fast reply.

Indeed, in our docker image We had an out-of-update cli version.
After update to the latest version, got the error fixed.
Thank you

CC: @rajesh-kemisetti

[rajesh-kemisetti]

@shetzel I am still seeing this issue. Below screen shot shows the CLI version and the package that just has the muted perm set and the retrieval doesn't work. I tried running the command in VS code via ctrl+shift+p and also with the terminal and got the same error

CC: @dieffrei