File Cabinet

NetSuite File Cabinet is the simplest possible destination. There's no authentication, no external network, no app registration, no client secret to rotate. You pick a folder and Outpost writes to it. That simplicity is the best thing about it, and also its limitation: once the file is in File Cabinet, getting it out to a BI tool is harder than any of the other destinations.

Use File Cabinet when you want an internal archive, when another SuiteScript is going to consume the file, or when your security policy forbids writing to external storage. For anything a human is going to open in Excel or Power BI, pick SharePoint or Google Drive.

Create the Connection in Outpost

1. Open Outpost by VCG → Connections
2. Click New Connection and pick File Cabinet
3. Fill in:
   • Connection name. e.g. Outpost Internal Exports.
   • Folder internal ID. The numeric ID of the target folder.
4. Click Save. There's no Test connection button for File Cabinet. If the folder exists and your role can see it, the Connection works.

That's the whole setup.

Configure folder and filename on the export template

File Cabinet Connections support the same filename tokens as every other destination, plus three extras that are only meaningful in the File Cabinet context:

• {date}, {datetime}, {search_id}. Same as everywhere.
• {year}, {month}, {quarter}. File Cabinet only.

For example, ar_aging_{year}_{month}.csv resolves to ar_aging_2026_04.csv. These are convenient when you want to organize archival files by accounting period rather than by calendar date.

What to expect on delivery

• File format: CSV, UTF-8, with a header row
• Location: The file appears in the File Cabinet folder you specified, owned by the role that ran the template
• Overwrite behavior: Outpost overwrites an existing file with the same name. If you include a token in the filename, each run creates a new file.
• Versioning: NetSuite File Cabinet keeps file versions by default. You can see history on the file record.

The "Available Without Login" decision

File Cabinet files can be marked Available Without Login, which generates a stable public URL anyone with the link can open. This is a NetSuite feature, not an Outpost feature. You toggle it on the File Cabinet record itself after Outpost creates the file, or you enable it on the folder so new files inherit the setting.

If you do turn it on, the URL is stable across deliveries. Outpost overwrites the file in place, so the URL doesn't change. That's the "stable URL" property that makes File Cabinet viable as a lightweight BI source in some setups.

Tips & gotchas

• No auth means no external token to expire. File Cabinet is the only destination in Outpost that can't fail because of credential drift. It will always run as long as the saved search runs and the folder exists.
• No setup cost. If your first goal is to prove Outpost works end-to-end before setting up a cloud destination, File Cabinet is the fastest path to a green run.
• Folder internal ID, not name. The Connection stores the numeric folder ID, not the human-readable folder name. If you move the file cabinet folder or rebuild it under a new ID, update the Connection.
• File Cabinet storage is not free-tier. NetSuite charges for File Cabinet storage. For high-volume archives, offload to Azure Blob or SFTP.
• "Available Without Login" is a folder or file property, set outside of Outpost. Outpost does not toggle it for you. Configure it on the NetSuite folder record if you want every file inside to inherit it.

Permissions & access control

Access to the file is controlled by File Cabinet folder permissions. Any NetSuite role that can see the parent folder can open the file. If you need tighter control, put the Outpost folder inside a permissions-scoped subfolder and restrict that subfolder to specific roles.

The role that runs the export template needs write access to the folder. If deliveries fail with a permission error, check the template owner's role against the folder's restrictions.

When to pick File Cabinet (and when not to)

Troubleshooting

• Connection saves but export template fails with INSUFFICIENT_PERMISSION. The role that owns the export template doesn't have write access to the File Cabinet folder. Update folder permissions or use a role that can write to it.
• File lands in a different folder than expected. The folder internal ID in the Connection is pointing at the wrong folder. Open the folder in File Cabinet, confirm the ID in the URL, and update the Connection.
• Power Query can't read the file. File Cabinet URLs require authentication by default. Either enable "Available Without Login" (understand the exposure first) or switch to SharePoint.