This notice is intended for customers who have at least one integration 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 ends on March 15, 2026, for the sandbox and release preview 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 | 2026.1 release |
Production | June 15, 2026 |
Required Actions
You must update your integrations to use standard URI parameters instead of NLQS decoding parameter before June 15, 2026, to make sure they work correctly in production accounts, March 15, 2026 in sandbox and release preview accounts. 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, in production accounts, and March 15, 2026 for sandbox and release preview accounts. If you require assistance or more information, please contact NetSuite Customer Support.