We’re experiencing a critical issue with our asset transfer workflow in NetSuite 2023.1. When initiating asset transfers between subsidiaries (specifically from US subsidiary to EMEA subsidiary), the SuiteFlow approval workflow isn’t triggering at all.
The workflow initiation conditions are set to trigger on asset record status change to ‘Pending Transfer’, but nothing happens. I’ve verified the subsidiary field mapping in the asset transfer form, and both source and destination subsidiaries are properly populated. The requesting user has the Asset Manager role with full permissions to the asset records.
This is causing significant delays in our intercompany asset movements, and we need transfers approved within 24 hours per our internal controls. Has anyone encountered workflow initiation failures related to subsidiary-specific asset transfers? Are there hidden field dependencies or role permission requirements we might be missing?
Have you checked the role permissions for workflow execution? Asset Manager role needs specific permissions beyond just asset record access. Navigate to Setup > Users/Roles > Manage Roles > Asset Manager role, and verify these permissions are granted: ‘Workflow’ permission level set to Full, ‘Asset Transfer’ transaction permission, and critically - ‘Cross-Subsidiary’ permission if you’re doing intercompany transfers. Without cross-subsidiary permission, the workflow engine can’t evaluate records spanning multiple subsidiaries.
Thanks for all the suggestions. I checked the workflow execution logs and found entries showing ‘Condition evaluation failed - field not accessible’. This pointed me to the subsidiary field mapping issue you mentioned.
Another common culprit is the asset transfer form customization. If you’ve customized the asset transfer form and the subsidiary fields aren’t properly sourced, the workflow can’t read them during initiation. Check Customization > Forms > Transaction Forms > Asset Transfer form. Make sure both ‘Subsidiary’ and ‘Transfer To Subsidiary’ fields are visible and not set to ‘Hidden’ or ‘Inline Text’. The workflow engine needs these fields accessible at the form level to evaluate initiation conditions. I’d also recommend checking your workflow execution logs under Setup > Integration > Workflow Execution Log to see if there are any silent failures.