Happy Business Starts Here

Highlighted
Zuora Support

Salesforce critical update to production on 1/11/2019

Salesforce will roll out a critical update to production on 1/11/2019 which affects managed packages in SFDC. The details of the update are below.

Update Details from Salesforce:

Add a Namespace Prefix to Query Parameters and pageReference.state Properties
Starting in Spring '19, query parameters and pageReference.state properties must have namespaced prefixes. If they don't have namespaced prefixes, they will be removed from the org's URLs. A namespace prefix distinguishes your package and its contents from other developers' packages. Namespace prefixes prevent conflicts between components on the state or query parameter name. To add a namespace prefix, see Register a Namespace Prefix.

To test and ensure that your namespace prefixes work, enable this critical update. 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.

This feature rolls out to sandbox orgs starting on December 3, 2018. It rolls out to production pods starting on January 11, 2019.

Example
If you have components or pages that rely upon a “foo” query parameter, prefix the “foo” parameter with a namespace. In this example, update /lightning/<page>?foo=true to /lightning/<page>?ns_foo=true. Likewise, if you store values in pageReference.state, update the properties to include a namespace. In this example, update pageReference.state = { foo: true } to pageReference.state = { ns_foo: true }.

If you don’t have Lightning Components in a package, add c__ as the default namespace.

 

Can we confirm that this update will not impact Zuora Quotes and Zuora 360?






If you found my answer helpful, please give me a kudo ↑
Help others find answers faster by accepting my post as a solution √

1 REPLY 1
Zuora Support

Re: Salesforce critical update to production on 1/11/2019

Engineering team have confirmed that We have not found any issues with the package through any testing with this setting enabled, and due to the explanation from Salesforce, we are not expecting any issues in Visualforce pages.






If you found my answer helpful, please give me a kudo ↑
Help others find answers faster by accepting my post as a solution √