Scenario
A customization works correctly in a Sandbox account but behaves differently after deployment to Production.
Common symptoms include:
- Workflows triggering differently.
- Scripts working in Sandbox but failing in Production.
- Fields or forms appearing differently.
- Saved searches returning unexpected results.
- Permissions behaving inconsistently between environments.
This is a common issue in NetSuite because Sandbox and Production environments can differ in configuration, data, features, permissions, and installed customizations.
Solution
Review the differences between the Sandbox and Production environments to identify what is affecting the customization behavior.
Common causes include:
- Configuration Differences
- Features enabled in Sandbox may not be enabled in Production.
- Accounting, inventory, approval, or subsidiary settings may differ between environments.
- Missing Customizations
- Workflows, scripts, custom fields, forms, or records may not have been migrated completely.
- Dependencies between customizations are often overlooked during deployment.
- Role and Permission Differences
- User roles may not match exactly between environments.
- Permission restrictions can affect workflows, field visibility, and script execution.
- Different Data Conditions
- Sandbox records may contain cleaner or simplified data.
- Production data often includes edge cases, inactive values, historical records, or approval restrictions.
- Script Deployment Settings
- Script deployments may differ between accounts.
- Execution contexts, audiences, statuses, or record types may not match.
- Workflow Version Differences
- Sandbox workflows may contain unpublished changes not present in Production.
- Multiple workflow versions can also create inconsistent behavior.
- Bundle or SuiteApp Variations
- Installed bundles or SuiteApps may differ between environments and affect customization logic.
- Form and Preference Differences
- Preferred forms, field display settings, and company preferences may vary between accounts.
Notes
Even small environmental differences can significantly affect customization behavior in NetSuite. A workflow or script that appears stable in Sandbox may behave differently in Production due to real transaction volume, permissions, or existing automation.
When troubleshooting:
- Review deployment records carefully.
- Validate workflows and script versions.
- Compare forms, roles, and permissions directly.
- Test using the same role and transaction scenario in both accounts.
Always validate deployments thoroughly in Sandbox before migrating to Production, especially in highly customized accounts.