Share
Report
652Hi,
I would like to know the whole picture around the "Record ID Query String Parameter Name", so I am reaching out to folks, who may know more.
From the little experience I got, I came to notice the following:
- For using an entity form in edit mode, I can set almost anything to be the "Record ID Query String Parameter Name", e.g. "id" or "opportunityid"
- If I want to call another entity form from the first entity form /e.g. edit an associated entity record), the framework is quite sensitive about the "Record ID Query String Parameter Name" --> here is an example:
- From an entity list, an opportunity record is opened via an entity from
- That edit entity form can have any random "Record ID Query String Parameter Name", but let's use "opprtunityid" in this example
- On that entity form, there is a subgrid and from that subgrid list an opportunity product record is opened via another edit entity from
- Now the fun starts, because I found that the "Record ID Query String Parameter Name" for calling the opportunity product record can only be "id" - nothing else works
In summary, the framework can be sensitive about the definition of the ID.
My question to you now is if you have the full picture why and how the framework works like this.
I basically want to understand this also a bit "under the hood".
Thanks for sharing your knowledge.
*This post is locked for comments
I have the same question (0)
All responses (
Answers (
