-
Notifications
You must be signed in to change notification settings - Fork 77
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
Custom Object Name Links Don't Work #218
Comments
Hi @SimonKaya , I don't know how are you dev skills but you may check if everything is going fine during the retrieve of the EntityDefinition objects. If you could share me the results via a video or gif it could be great, if not we can see if we can schedule a short meeting |
Thanks for the fast response @tprouvot I don't use the chrome inspector or debugging tool for my line of work but think I've caught what you were looking for. I seemed to have to refresh the tab to catch the debug however now sure if that makes a difference or not based on your video. Looks like my count is 2620. SF.Inspector.Debug.movIf you need more information or a better example it might be easier to plan a call. |
@SimonKaya To be able to do that you'll have to put a conditional breakpoint by testing the record.QualifiedApiName with your custom object |
The potential cause is due to the following code where it expects In my troubleshooting it seems to be caused by So, a potentially fix is to add this check. |
Hi @SRosewood , After that check if the link in the popup is functional |
Yes, I did the test manually on my browser before the PR. That is the same code and it fixed the issue. |
## Describe your changes Add a check if `durableId` was not previously set but the entry is already added into the map. ## Issue ticket number and link #218 ## Checklist before requesting a review - [ X ] I have read and understand the [Contributions section](https://github.com/tprouvot/Salesforce-Inspector-reloaded#contributions) - [ X ] Target branch is releaseCandidate and not master - [ X ] I have performed a self-review of my code - [ X ] I ran the [unit tests](https://github.com/tprouvot/Salesforce-Inspector-reloaded#unit-tests) and my PR does not break any tests - [ X ] I documented the changes I've made on the [CHANGES.md](https://github.com/tprouvot/Salesforce-Inspector-reloaded/blob/master/CHANGES.md) and followed actual conventions - [ N/A ] I added a new section on [how-to.md](https://github.com/tprouvot/Salesforce-Inspector-reloaded/blob/master/docs/how-to.md) (optional)
@SRosewood I'm closing the issue since Jeferson provided a fix, please feel free to reopen it if you're issue is still running |
Sorry for the delayed response @tprouvot . Yes has worked thanks @jefersonchaves look forward to the fix making a release soon. 👍 |
Make sure to read the troubleshooting section before creating an issue
Describe the bug
When clicking an object name via SF inspector, this should take the user to the object manager page for that object in setup. Instead the url object name is undefined and navigates the user to the object manager home page in setup.
This works for standard objects but not custom objects.
To Reproduce
1 - Open an org
2 - Open SF Inspector
3 - Search for a custom object
4 - Click Object Name (URL Link)
Expected behavior
Should take user to custom object manager page for that object.
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: