Permission Set Group Issue

[grahampcurran]

Hi there,
I am getting the following error when trying to run the permissions report in Production:
Uncaught (in promise) TypeError: Cannot read property 'Name' of null at B.getPermissionSetNames (build.js:2) at async i.runReport (build.js:2) at chrome-extension://gkibdicghcpcikhjpgjoijpobdipklnp/public/async chrome-extension:/gkibdicghcpcikhjpgjoijpobdipklnp/build.js:2
The User has permission sets and a permission set group assigned.

[hudec117]

Hello @grahampcurran, could you please run:

SELECT PermissionSet.Name, PermissionSet.Type FROM PermissionSetAssignment WHERE AssigneeId = 'USERID' AND PermissionSet.IsOwnedByProfile = false

Where "USERID" is the ID of the user you are trying to open the report for. Please censor anything confidential.

[grahampcurran]

Hey, see below

[hudec117]

And then if you run:

SELECT PermissionSet.Name FROM PermissionSetGroupComponent WHERE PermissionSetGroup.DeveloperName = 'CPQ_Standard_User'

This will allow me to see what data the code is working with.

[grahampcurran]

Sure. There is a (null PermissionSet) in there which is quite odd. Probably the source of the issue. Ill have a look at that on my side.

[hudec117]

Looks like the 3rd from bottom is the issue, I should probably add an additional condition to filter it out.

SELECT PermissionSet.Name, PermissionSet.Type, PermissionSet.IsOwnedByProfile FROM PermissionSetGroupComponent WHERE PermissionSetGroup.DeveloperName = 'CPQ_Standard_User'

Sorry I keep asking you to run queries, this should be the last one. I added 2 more fields and I expected PermissionSet.Type or Permissionset.IsOwnedByProfile to be usable on filtering out the "(null PermissionSet)"

[hudec117]

Looks like this is due to a muting permission set in the permission set group. In the query it shows up as an empty PermissionSet.Name. I have added a fix and will put it in the 1.2.1 release.

[grahampcurran]

hey sorry for the delay.
See below. Hope thats in line with your thinking

[hudec117]

Thanks! That confirms my suspicion, it's the muting permission set that causes the trouble, I've patched it and include it in a hotfix release.

[hudec117]

@grahampcurran I appreciate it has been nearly a year, but I've released a fix for this now haha. I'm going to close this as fixed.