BPMs & Data Directives Row State: Updated Row vs Changed Row

If you are new to the Epicor Technical Tools you may have run into the quandary when working with a condition or one of the Setter widgets when trying to choose between ‘the updated row’ and ‘the changed row.’  What is the difference and when should you use each?

  • Added Row – means the record is being added.
  • Updated Row – means that the record already existed and has been updated.
  • Changed Row – means that the record is either new or already existed.

So if you only want your condition to apply when an existing record has been updated, then use ‘Updated Row.’  If it is possible that your record could have been just created (new) or updated then use ‘Changed Row.’ Just want when the row is new, then use the ‘Added Row’ option.

Also don’t forget what Method directive you are specifying the condition in, if it is the Updated method then depending on how Epicor uses and calls the method the record could be use or previously existing.  If it is a GetNew method, then you would want to always use Changed, as Updated may not meet the condition and cause you lots of confusion.  Don’t assume too quickly which Method directive is the correct one to use.  Use the Trace option and be sure to understand as much as possible with what is going on when each method is called.

One Comment to BPMs & Data Directives Row State: Updated Row vs Changed Row

  1. Dinesh says:

    what is the meaning of all unchanged rows in epicor & if this is for erp.tables & not for tttables then in which case we are not using tttable.

Leave a Reply

%d bloggers like this: