I did many attribute rule that upon condition return an "Edit object" like those describe in this article
However, sometimes I need to trigger an edit but without the need to actually perform a calculation on a field on the current object.
For example : When a new record is create or if the field_A of an old one is modified then create a new record in another table. The Field_A is not modified by the calculation. It could have been a more complex check that is done upon a Insert, Update, Delete Trigger, but with no real calculation.
I currently assign a dummy field for that "calculation"
My Idea is: Be able to create a rule that is not attached to a specific Field in a triggered Feature/Table to perform an edit on another Feature/Table
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.