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!
Update your Profile with your Support type to get your Support Type badge.
Don't miss out on our Question of the Week! You only have until tomorrow, October 23, 2025, 2PM ET to comment your answers and earn rewards! Click here for more details.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
Phantom Workflow Triggering
All,
Has anyone else see the following happen? We had a Mass Update somehow trigger a Workflow that never had it's criteria met. Let me explain.
The Mass Update was a super simple one. It simply copy the status of a Customer record to a custom field. That's it.
When it ran, however, the a bunch of fields on the Customer record were modified. In fact, the field changes were EXACTLY that of a State1 in a Workflow who's criteria would have never fired against this record. I know this to be true as there are static values that only the Workflow enters into these fields.
Tagged:
0