-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
User Selection not displaying user information #211
Comments
Hi @mackarovSF, Could you check chrome dev console and see if there's any error ? |
@tprouvot, sure! Here's the dev console error:
|
Same issue here starting today |
Hi @mackarovSF @RebbePod , Apologies for the inconvenience I'm really sorry |
@tprouvot Thank you so much! I installed the reloaded version about two weeks ago and love it. You rock! |
@mackarovSF @RebbePod if you are on a sandbox you can also enable digital experience and it will solve the issue Be careful this will enable my domain, use this option at your own risks 😄 |
The fix is waiting for review on the Chrome web store, it should be ok tomorrow 🤞 |
Thank you |
@RebbePod @mackarovSF |
Yep! It's working, already used it this morning. Thanks! |
Same here. Thank you! |
When using Salesforce Inspector Reloaded and trying to view a specific user, the drop down shows users matching the search. However, when selecting the desired user, the usual user information and buttons to login, view details, etc., doesn't appear and it shows "No user details available".
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expected to be able to view the user details and buttons to login as the user, view user details, view permission sets, and view permission set groups.
Screenshots
No screenshots because it would show user PII.
Desktop (please complete the following information):
Additional context
This started happening today (11/8/2023). I have uninstalled the extension and reinstalled the extension. I updated Chrome from an older version to the up to date version. Other features work as expected.
The text was updated successfully, but these errors were encountered: