Upcoming Removal of URL Alias (storealias) Field in Site Builder Websites – NetSuite 2026.1

NetSuite is removing the URL Alias (internal field ID: storealias) from the Website Setup record starting with the 2026.1 release.

This change will not affect the functionality or accessibility of existing live Site Builder websites. The storealias value has not been used for live sites for several releases and is now considered deprecated.

However, any custom scripts, SuiteScript code, workflows, SuiteFlow, SuiteTalk integrations, or third-party connectors that explicitly read from or write to the storealias field will be impacted and may start returning or encountering null-value errors after the upgrade.

What is Changing in 2026.1?

After your account is upgraded to NetSuite 2026.1:

  • The URL Alias field will be completely removed from the UI and will no longer appear on the Website Setup record under Setup > Site Builder > Websites > [Website] > Domains subtab (Shopping Domains area).
  • Any attempt to write to the storealias field (via SuiteScript, REST, SOAP, etc.) will be ignored — the field will no longer accept data.
  • Any attempt to read the storealias field will return null (or an empty value, depending on the API).

To ensure a smooth transition, please complete the following steps as soon as possible:

  1. Search your account for references to storealias Use Global Search, SuiteScript Analyzer, or grep your codebase for the internal ID storealias.
  2. Update or remove all references
  • Replace any logic that depends on storealias with the current recommended approach (e.g., use the primary domain or custom domain configured on the Domains subtab).
  • Remove any code that writes to the field.
  1. Verify your website URLs If you previously relied on a URL alias for a site without a custom domain, confirm that your site is now accessible via its standard HTTPS domain (e.g., https://yourcompany.system.netsuite.com).
  2. Test in a 2026.1 environment
  • Use your Release Preview account (automatically provisioned before the 2026.1 upgrade), or
  • Refresh/upgrade a sandbox to 2026.1 and perform thorough regression testing of all customizations and integrations.

Leave a comment

Your email address will not be published. Required fields are marked *