Overview
NetSuite workflows do not always behave the same way during CSV imports as they do when records are entered manually. Some workflow actions may not trigger, or they may trigger differently depending on the workflow setup and import method.
Understanding this behavior can help administrators troubleshoot imported records more effectively.
Scenario
Imported records skipped workflow actions.
Solution
This usually happens because CSV imports can bypass or affect workflow execution depending on how the workflow is configured.
Review the following:
- Workflow triggers
- Execution context
- Record type being imported
- User permissions
- Whether the workflow is set to run during CSV imports
If needed, test the workflow using a manual record entry first, then compare the result with a CSV import.
Notes
- Some workflow actions may not trigger during imports by design.
- Imported records may behave differently from manually created records.
- Always test workflows in a sandbox before using them in production imports.
Want to learn more about Customization? Visit New to NetSuite: SuiteBuilder & SuiteBundler