I wrote a simple In-Transaction Data Directive BPM to set the Template flag in QuoteDtl to True. We would normally check this anyway, but if we can get it set as a default, why not?
Anyway, the BPM does set the flag to true. When we use the Engineering Workbench to pull in the method, we get an error - “The number is either invalid is is not marked as a template.” If I disable the BPM, the process to pull in the method works as expected.
Epicor Tech Support suggested that I change it to a Method Directive, but I don’t see the same type of ‘setters’, and, in addition, the BPM should only be setting the field value. I’m not sure why it would be interfering with the Get Method process.
The BPM is a ‘Start’ object, linked to a ‘Set Field’ object.
Action is - Set the ttQuoteDtl.Template field of the changed row to the true expression.
That worked. Thanks.
Just for the record, I tried ‘updated row’ and ‘all rows’, but those failed too.
I’m not sure why ‘added’ is any different from the others…
Added will only fire when a new record is created, so it would only ever happen once per record. The other criteria could fire multiple times, whenever the record is changed. That Get Method process may have been trying to change that field value for some reason (if only temporarily), and your BPM was changing it back.
New Eyes!
I’ve been looking at the BPM as something that only happens while in a quote. I didn’t really think about other processes that may be hitting the tables.
That’s one of the reasons I love this job, frustration turning into success, and learning a thing or two along the way.
Again, many thanks.