I am trying to create a custom URL button to place on two different Account page layouts. My goal is: upon clicking this button, users will be directed to a specific case record type creation form and several of the fields will already be pre-populated based on the information on the account record in which they clicked the button from.
More specifically, on the Person Account page layout, if the button is clicked a "Member Initiative" (record type) case creation form would launch and the Account Name and Contact Name field on the case form would be prepopulated with the ID information from the person account record in which the button was clicked.
On the Business Account page layout, if the button is clicked a "Member Initiative" (record type) case creation form would launch and the Account Name on the case would be prepopulated with the specific business account's ID and the Contact Name field on the case would be prepopulated with the specific business account's primary contact's ID.
I have been using this SF resource (https://releasenotes.docs.salesforce.com/en-us/spring20/release-notes/rn_general_lex_navigate_to_record_dfv.htm
) for reference in doing my testing but I am having no luck. I even tried to just populate the description field on the launched case with "test test test" and that didn't work. For reference, here is an example of a custom URL I have tested (as a detail page button on the account object):
/lightning/o/Case/new?defaultFieldValues=
AccountID={!Account.Id},
RecordTypeId=0122B0000004J0JQAU
Upon clicking, while the correct case record type was popping up (although I am not sure if this is because of the custom link URL or because it is the default master record type), the Account Name field on the case was completely blank.
Am I missing something here? I need to use the custom URL button method over the quick action (which I know is much easier when it comes to prepopulating fields) because I need to give users the ability to turn off/on the "Use Active Assignment Rules" functionality and at this time, the action button feature does not allow for this.
I appreciate any and all help!!
Thanks,
Ricki
1 resposta
Screen flow which can be invoked with a flow action button is the way to go in your case.
