Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Stay in the Know
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Please note that on Friday, March 20, 2026, at 8:00 PM Pacific time, our Case Management System will undergo a scheduled maintenance for approximately 4 hours. During this time, case creation via SuiteAnswers will be unavailable and inbound calls will be routed to Customer Service.
Dealing with [ACCOUNT_SPECIFIC_VALUE]
Howdy,
I'm responsible for deploying from sandbox to production several complicated WorkFlows that have Set Field Value actions setting a static List/Record value. The downloaded XML of course doesn't have the internal id (or external id!) of the records, rather it has "[ACCOUNT_SPECIFIC_VALUE]". You can't deploy the objects like this, the validation system will catch and block it (good).
Putting aside the fact that setting static record reference directly in workflows is ill-advised, I wanted to ask how any of you are dealing with this if you're in the same situation?
My solution I'm running with right now is to use a PowerShell script with
Steve Klett | Senior Developer
NetValue Technology
0