[fix]: Custom object setup links redirect to Object Manager root instead of specific object#1193
Open
RubenHalman wants to merge 1 commit into
Open
Conversation
…f specific object Replace durableId with sobjectName in ObjectManager URLs for custom objects. The durableId (entity ID) is not a valid URL segment for ObjectManager — it causes Salesforce to fall back to the Object Manager root page.
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the bug reported in beta where clicking Fields/Details/Record Types for a custom object navigates to the Object Manager root instead of the specific object.
Root cause
The ObjectManager URLs for custom objects used
durableId(from the Tooling API EntityDefinition query). If that query hasn't completed yet,durableIdisundefined, producing a URL like.../ObjectManager/undefined/FieldsAndRelationships/view, which Salesforce redirects to the Object Manager root. Standard objects already usedsobjectNamedirectly and worked fine.Fix
Use
sobjectName(e.g.MyObject__c) consistently in all ObjectManager URLs — it's always available immediately and works for both standard and custom objects.Affected functions
getObjectSetupLinkgetObjectFieldsSetupLinkgetRecordTypesLink