A sandbox account is used to create replicas of the production account for development and testing purposes. A sandbox account is a security mechanism for separating running programs, usually in an effort to mitigate system failures or any other vulnerabilities from spreading.
Occasionally, the sandbox account is refreshed to bring the latest data and configurations from the production account into the sandbox account.
Note: There is always a risk that internal IDs and fields between sandbox and production environments are different. It is advisable to add to the production environment any mapped fields that exist in the sandbox before the refresh. You need to test in the sandbox after a refresh with new records to avoid the internal ID mismatch issue.
Refresh and relink the Salesforce sandbox
Depending on the state of the Salesforce production environment, you need to ensure the following steps before the Salesforce - NetSuite Integration App can sync to and from the refreshed Salesforce sandbox.
- Install the latest Integrator Distributed Adaptor and Celigo NetSuite Package Salesforce managed packages.
Note: You can skip this step if the Salesforce production environment has the managed packages installed before the Salesforce sandbox refresh.
- Search Real Time Sync in Salesforce and delete all the real time sync records that contain sfns-io in the connector ID field.
For more information on the Real Time Sync object, see
- Re-register your Salesforce connection by clicking on Salesforce connection [Salesforce - NetSuite Connector(IO)] in the Connections tab and verify your Salesforce credentials.
- Turn off and back on any desired Salesforce to NetSuite flows for force creation of the corresponding real time sync record.
- Verify all the real time sync records are present in Salesforce.
Please sign in to leave a comment.