Version: eXtendFiles 1.8.4 and above
Audience: Administrator, User

Overview

This article provides recommended practices and frequently asked questions for configuring eXtendFiles in Sandbox environments. Following these guidelines will help you avoid unintended impacts on your Production account when working in Sandbox.

Configuration best practices

Set up distinct storage containers or buckets

Use separate storage containers or buckets for each of your Sandbox accounts. If you use the same storage configuration for both Production and Sandbox accounts, unintended changes or deletions in your Sandbox account can impact the base file in your shared storage account, which will in turn affect your Production account.

For instance, if you use identical storage configurations for both Production and Sandbox, removing 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

To prevent unintentional file deletion or access in your storage, use 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.

Update links after Sandbox refresh

After refreshing your Sandbox account, revise 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.

Frequently asked questions (FAQs)

Q: Why aren't changes appearing on my eXtendFiles records after I approve or reject them in my Sandbox account?
A: If your Sandbox account was refreshed recently and the subdomain name in the approval URL doesn't 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.

Q: Why aren't files uploaded using the public upload link appearing in my Sandbox account?
A: If your Sandbox account was refreshed recently and the subdomain name in the approval URL doesn't 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.

Q: 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?
A: If the bucket set up in Sandbox differs from the one in the Production account, Production files won't 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.

Q: Can Sandbox users delete files stored in the Production's Amazon S3 bucket by removing the eXtendFiles records in the Sandbox?
A: Deleting eXtendFiles records from a Sandbox account won't delete the original file if the bucket configured on the eXtendFiles Setup page isn't 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.

Q: Why aren't file migrations and file conversions (preview and thumbnail generation) processing in my Sandbox account?
A: By default, file migration and file conversion processes are disabled in Sandbox and Release Preview environments to prevent unintended impacts on Production storage and to conserve resources. If you need these features enabled in your Sandbox account for testing purposes, you must explicitly enable them. For detailed instructions on how to enable file migration and file conversion in Sandbox environments, refer to Restricting File Migration and File Conversion in Sandbox & Release Preview Environments.