Forum Stats

  • 3,687,013 Users
  • 61,198 Discussions
  • 206,901 Comments

Discussions

Check out Oracle NetSuite upcoming events and conferences here
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now!
RUN, DON’T WALK...Registration for #SuiteWorld 2022 is officially OPEN! This special early bird price won’t last long, so make sure you don’t miss out: https://lnkd.in/gGRN78A3
YOUR VOICE MATTERS! VOTE FOR OUR NEXT WEBINAR TOPIC NOW.
Click on this link for the poll.

Phantom Workflow Triggering

edited Dec 3, 2019 2:50PM in General 5 comments

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:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

This Week's Leaders

This Month's Leaders

All Time Leaders