Add a Namespace Prefix to pageReference.state Properties and Query Parameters

As mentioned in the Spring ’19 release notes, this critical update addresses an issue with naming conflicts between package components. A namespace prefix distinguishes your package and its contents from other developers' packages. The namespace prefix prevents conflicts between components on the state or query parameter name. Query parameters and pageReference.state properties must have a namespace prefix. If they don’t, this critical update removes them from the org's URLs. This critical update is enabled for Summer ’19 on May 17, 2019.
Where: This change applies to Lightning Experience and the Salesforce app in all editions. This change does not affect Visualforce or Salesforce Classic URLs, Communities, or report URL that contain non-custom query parameters.


If your org displays an auto-activation date of January 10, 2019, ignore it. This date was the original activation date for the critical update before it was postponed. When your org updates to the Spring ’19 release, the displayed auto-activation date will be correct.

How: To add a namespace prefix for a managed package, see Register a Namespace Prefix. If you don’t have a registered namespace, add the default namespace of c__. To test and ensure that your namespace prefixes work, enable this critical update. Test any pages that have custom query parameters and that navigate to a URL containing /lightning/. If you have managed packages, test pages from within and outside of managed packages. If you run into issues, ensure that you've prefixed the values with a namespace. If you continue to have issues, contact Salesforce Customer Support.

After you add namespace prefixes, enable the critical update. From Setup, enter Critical Updates in the Quick Find box. Then select Critical Updates. For Add a Namespace Prefix to Query Parameters and pageReference.state Properties, click Acknowledge.