Install & configure

Install the SuiteApp, enable the prerequisite NetSuite features, and grant permissions to the roles that need to upload, view, or delete files.

Module requirements

File Storage needs the following NetSuite features enabled. Go to Setup → Company → Enable Features to turn them on:

SuiteCloud tab

  • Custom Records
  • Server SuiteScript
  • Token-Based Authentication

SuiteApp dependencies

File Storage depends on the Portal SuiteApp. Portal provides the AWS infrastructure that File Storage uses — it must be installed and registered before you install File Storage. See Portal for installation and registration instructions.

File Storage also depends on Code Library, which installs automatically as part of any FullClarity SuiteApp install.

Installing the SuiteApp

Install File Storage via the SuiteApp Control Centre. The deployment process installs all files and objects contained in the SuiteApp.

You will receive an email confirming that your account has been provisioned and is ready for installation. Once you receive it, follow the steps below to install FullClarity's File Storage for NetSuite.

Walkthrough coming

A step-by-step Scribe walkthrough for installation is being recorded. Track its status in the Scribe register (internal).

Having completed the installation, you now need to nominate which records you want File Storage to work on. See Enable on a record type.

Configure permissions

Specific permissions are required to view or edit File Storage data. A full per-role permission breakdown is available at Permissions reference; however, we strongly recommend using the automated permission allocation utility:

Walkthrough coming

A step-by-step Scribe walkthrough for the permission allocator is being recorded. Track its status in the Scribe register (internal).

The automated allocator is update-safe — when File Storage is upgraded, any new custom records or fields are automatically granted to roles that already have File Storage access, and hidden from roles that don't. Manual permission configuration is not update-safe, so it should only be used for unusual cases. See the Permissions reference for the manual tables and the View / Create-only / Read-and-write permission sets.

Modify forms

When File Storage is installed, a custom field is automatically added to the main body of each enabled record type. The specific location of the field can be adjusted by editing the form template for that record — see NetSuite's standard help on customising form layouts.

To stop File Storage from functioning on a specific record type, an administrator can disable the deployment for that record. Locate the FC Storage Record UE script, go to its Deployments tab, edit the deployment for the relevant record type, and untick Deployed.

Sandbox accounts

File Storage is safe to use with sandbox accounts, with two things to be aware of:

  • Re-register the sandbox each time you refresh it. NetSuite deletes all access keys during a sandbox refresh, so the Portal registration needs to be re-run. See Portal.
  • Files uploaded in production are accessible (read-only) from the sandbox. You can view files from production in your sandbox but you cannot delete them. New files uploaded in the sandbox go to a separate test bucket and are deleted automatically after about six months.

Supported record types

File Storage supports almost all standard NetSuite record types — see the "Supported Records" configuration screen for the full list. Custom records are also fully supported; see Enable on a record type.

What success looks like

  • The File Storage drop zone and file list appear on the body of every enabled record type.
  • Uploading a small file from a saved record completes successfully and the file appears under Documents on the record within a few seconds.
  • Granting a role File Storage access via the allocator produces a visible role-permissions change on that role's record.

Gotchas

  • Files cannot be added during the "Create" process. Because File Storage stores files against an existing NetSuite record, the record must be saved at least once before a file can be uploaded. Save the new record first, then add files.
  • Portal must be installed and registered first. File Storage will install without Portal but the upload widget will not work — every operation routes through Portal's API endpoints.
  • Manual permissions are not update-safe. Use the allocator unless you have a specific reason to manually grant permissions.
Last Updated: