search

hudec117 / sf-user-perm-report

Salesforce User Permission Report allows you to see a report of all the permissions a user has and where they are set.
MIT License
10 stars 2 forks source link

Failed to merge error #45

Closed axblain closed 8 months ago

axblain commented 2 years ago

Describe the bug Failed to merge error. Tried on 2 users. Tried on Classic and LEX.

To Reproduce Steps to reproduce the behavior:

  1. Go to user
  2. Click on "Open permission report" button
  3. Wait
  4. See error "Failed to merge, see console for details."

Expected behavior First time I use the extension. Extension did sound promising but this was disappointing.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

hudec117 commented 2 years ago

Does anything come up in the console regarding this error?

Is there anything special about your users or their profile, permission sets or permission set groups?

axblain commented 2 years ago

I haven't checked the console (I don't know how it works or what to look for).

Other than being complex permissions (which is the reason to use the extension), nothing strikes to me as "special"

On Wed, 31 Aug 2022 at 17:44, Aurel Hudec @.***> wrote:

Does anything come up in the console regarding this error?

Is there anything special about your users or their profile, permission sets or permission set groups?

— Reply to this email directly, view it on GitHub https://github.com/hudec117/sf-user-perm-report/issues/45#issuecomment-1233110802, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGHV75DMN3EP7ILARBSWF73V354WTANCNFSM57WKNGAQ . You are receiving this because you authored the thread.Message ID: @.***>

aknight1157 commented 9 months ago

@hudec117 I am running into this same issue. I don't know how to access the console to see error details. It seems to be happening on any user in some of my orgs that have complex permissions. The report works in the same browser in a different org with simple permissions.

hudec117 commented 9 months ago

@aknight1157 could you try removing all the permission sets from the user and running the report? If it works, that would indicate the issue is with one of the permission sets. If not, then it means it may be the profile.

hudec117 commented 9 months ago

I have been able to replicate this issue by putting a managed Permission Set into a permission set group and then trying to run the report. Is this the case in your scenario?

hudec117 commented 8 months ago

This should be fixed as of 1.2.4, in the process of being published to the Chrome Web Store. If you find it still doesn't work with the update, feel free to re-open!