Recommended Practices for Sandbox
Configuration
Set up distinct storage containers or buckets for each of your Sandbox accounts.
Unintended changes or deletions in your Sandbox account can impact the base file in your shared storage account if you use the same storage configuration for your Production and Sandbox accounts. This will in turn affect your Production account.
For instance, if you use identical storage configurations for both Production and Sandbox, the removal of an eXtendFiles record from your Sandbox account will lead to the file's deletion from your cloud storage. Consequently, the file will become inaccessible from your Production account.
Use unique storage credentials in your Production and Sandbox account(s).
- To prevent unintentional file
deletion or access in your
storage, we advise using different
credentials for your storage
configuration in the Production
and Sandbox accounts. This is
especially critical if someone
alters the containers or buckets
used in your Production
account.
- To prevent unintentional file
deletion or access in your
storage, we advise using different
credentials for your storage
configuration in the Production
and Sandbox accounts. This is
especially critical if someone
alters the containers or buckets
used in your Production
account.
- After updating your Sandbox account, we suggest revising all public upload links and eXtendFiles multi-approval and single-approval links.
- A Sandbox refresh duplicates the
data from your Production account
into your Sandbox account as it
is. All public upload links,
multi-approval links, and
single-approval links in the
Sandbox account will direct to the
Production account. Any file
uploads or approval/rejection
actions done using these links
will alter the data in your
Production account. To avoid this,
refer to eXtendFiles
Approval and Public Upload
Link Configuration after
Sandbox Refresh for
instructions on creating new
public upload links,
multi-approval links, and
single-approval links for
Sandbox.
- A Sandbox refresh duplicates the
data from your Production account
into your Sandbox account as it
is. All public upload links,
multi-approval links, and
single-approval links in the
Sandbox account will direct to the
Production account. Any file
uploads or approval/rejection
actions done using these links
will alter the data in your
Production account. To avoid this,
refer to eXtendFiles
Approval and Public Upload
Link Configuration after
Sandbox Refresh for
instructions on creating new
public upload links,
multi-approval links, and
single-approval links for
Sandbox.
Frequently Asked
Questions about Sandbox
Configuration
- Why aren't changes appearing on my eXtendFiles records after I approve or reject them in my Sandbox account?If your Sandbox account was refreshed recently and the subdomain name in the approval URL does not align with the subdomain set up in your Sandbox account, then changes made to the eXtendFiles records in Sandbox may reflect in your Production account. This happens because the Sandbox approval links need to be updated after a Sandbox refresh. For more details on how to update approval links in Sandbox, refer to eXtendFiles Approval and Public Upload Link Configuration after Sandbox Refresh.
- Why aren't files uploaded using the public upload link appearing in my Sandbox account?If your Sandbox account was refreshed recently and the subdomain name in the approval URL does not align with the subdomain set up in your Sandbox account, then files uploaded using the public upload feature may be reflected in your Production account. This happens because the Sandbox approval links need to be updated after a Sandbox refresh. For more details on how to update approval links in Sandbox, refer to eXtendFiles Approval and Public Upload Link Configuration after Sandbox Refresh.
- When using private files, can Sandbox users access eXtendFiles files stored in the Production Amazon S3 bucket, even if the Sandbox is set up for the Sandbox's Amazon S3 bucket?
If the bucket set up in Sandbox differs from the one in the Production account, Production files will not be visible. However, if both buckets use the same credentials and someone modifies the eXtendFiles Setup page with the same bucket used in your Production account, the files will become visible in your Sandbox account. To avoid such scenarios, we recommend using different credentials for Production and Sandbox buckets.Note: Public files will remain accessible from your Sandbox account. - Can Sandbox users delete files stored in the Production's Amazon S3 bucket by removing the eXtendFiles records in the Sandbox?
Deleting eXtendFiles records from a Sandbox account will not delete the original file if the bucket configured on the eXtendFiles Setup page is not the same Amazon S3 bucket as in Production. The NetSuite eXtendFiles record will be removed from the Sandbox account, but the original file will remain in the Amazon S3 storage.