This notice intended for customers who access NSQL encoded URLs successfully and the NLQS URLs are not media objects (files in file cabinet).
You are receiving this notification because you have at least one integration or webstore that is using NLQS decoding. As of June 15, 2026, including the NLQS decoding syntax in the URL will no longer be supported in production accounts. The support is ending because NetSuite can handle standard URI parameters.
What is Changing?
Integrations using the NLQS decoding syntax will no longer work correctly in production accounts. All integrations should use decoded links with standard URI parameters that can be handled by the system without decoding. See the following table for the exact dates when the support ends in different account types:
Account Type | End of Support Date |
|---|
Sandbox / Test Drive | Ended with 2026.1 update |
Production | June 15, 2026 |
Required Actions
You must update your integrations or webstore to use standard URI parameters instead of NLQS decoding parameter before June 15, 2026, to make sure they work correctly. You must rewrite calls in the integrations to replace the underscore with a question mark and remove the dot nlqs extension.
See the following example: NLQS encoded link:/javascript/NLUtil.jsp__NS_VER=2017.2.0&minver=137&locale=en_US.nlqs
Decoded link using standard URI parameters:/javascript/NLUtil.jsp?NS_VER=2017.2.0&minver=137&locale=en_US
You should update any integrations that use the nlqs syntax before support ends on June 15, 2026. If you require assistance or more information, please contact NetSuite Customer Support.