ANS-1477 · OTHER
How to Ensure Recent Production Changes Appear in a NetSuite Sandbox Refresh?
Understand how NetSuite's production snapshots impact sandbox refreshes and learn the best practice for capturing the latest configuration.
Short answer
NetSuite sandbox refreshes utilize production snapshots, which are not live and occur a few times weekly. If a refresh is initiated on the same day as recent production changes, those changes might not be included. To ensure all recent work is captured, it is recommended to wait 1-2 days after deployment before initiating a sandbox refresh.
Scenario
When a NetSuite sandbox is refreshed, recent changes made in the production environment may not appear in the newly activated sandbox. This discrepancy can lead to confusion and hinder development or testing efforts, as the sandbox does not accurately reflect the current state of production.
Solution
NetSuite sandbox refreshes are based on production snapshots, which are periodic copies of the production environment. These snapshots are taken a few times a week but do not represent a live, real-time copy of production data. When a sandbox refresh is initiated, NetSuite uses the most recent available production snapshot to create the sandbox copy. This means that any work or changes deployed to production after the most recent snapshot was taken, but before the sandbox refresh initiation, will not be included in the refreshed sandbox. To ensure that all recent production changes are fully captured in a refreshed sandbox, it is recommended to wait 1-2 days after deploying significant changes to production before initiating the sandbox refresh process.
Expert NetSuite Support
Need help with this NetSuite issue?
Other consulting and configuration support