13

The requirement was to open a Lightning App page and pass some query parameters in the URL. These query parameters were then used to query data and display in a Lightning component present in the Lightning App.

Till Spring 19, it was working fine. This was the URL format:

force.com/lightning/n/Document_Upload?id=0015B00000fS9mzQAC&type=AccountDocument

where Document_Upload was the name of the Lightning App and 'id' and 'type' were the query parameters.

In Summer 19, the same URL format doesn't work.

In fact, any query parameter appended to a page is removed as the page loads.

So, this URL,

force.com/lightning/n/Document_Upload?id=0015B00000fS9mzQAC&type=AccountDocument

becomes

force.com/lightning/n/Document_Upload

How do I pass query parameters here?

22

I think there is a Critical Update that gets auto-enabled for Summer '19, that forces Lightning URL parameters to be namespaced. And the default namespace for orgs is "c".

So if you add ?foo=bar to the URL, it will get auto-stripped.

But if you add ?c__foo=bar to the URL, it will persist.

1

@Sam @CharlesT: Here is the SF critical update link that talks about this: https://releasenotes.docs.salesforce.com/en-us/spring19/release-notes/rn_forcecom_general_namespace_prefix_cruc_reminder.htm

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.