Introduction
- Opportunity
- Estimate (Quote)
- Sales Order
- Invoice
- Purchase Order
- Vendor Bill
- Vendor Payment
Usage
Additional Notes
Currently, eXtendFiles supports 1:1 record
linking for the linked transaction file
flow. As an example, this means that when
eXtendFiles are added to a Sales Order, it
can only link the Sales Order's
eXtendFiles to one Purchase Order and one
Invoice. If there is a 1:N relationship,
such as a Sales Order to ten Purchase
Orders or a Sales Order to three Invoices,
the eXtendFiles record will not be
automatically linked with subsequent
Purchase Orders or Invoices after the
first one, respectively.
This limitation is due to the fact that the
reference field in eXtendFiles only allows
linking with a single transaction (as
shown in the example below).
Important Notes:
- File flow to Work Orders requires a
custom implementation project with
associated development costs.
- Additional file flow requirements
beyond standard functionality will
require custom implementation and
associated development costs.
- File flow functionality only applies
to record (body) level uploads, not to
line-level uploads.
- When a NetSuite Sandbox is refreshed
from Production, NetSuite
automatically resets the deployment
status of Map/Reduce scripts to "Not
Scheduled" in the Sandbox environment.
This is a safety measure to prevent
unintended processing, integrations,
or automations from running
immediately against freshly copied
data. To enable file flow
functionality in a refreshed Sandbox
environment, reschedule the
eXtendFiles file flow script
deployment:
- Title: eXtendTech Files
Transform AUT M/R
(SCHEDULED)
- Script
ID: customdeploy_extend_files_aut_transfer