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.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Update: Narrative Insights has been restored and is now available.
Narrative Insights is Temporarily Unavailable due to an Infrastructure Issue. Learn how This Impacts Your Account and What to Expect While the Feature is Disabled.
Narrative Insights is Temporarily Unavailable due to an Infrastructure Issue. Learn how This Impacts Your Account and What to Expect While the Feature is Disabled.
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