Home      FAQ      Forum      Idea Exchange      Ask a Question      My Stuff      Help   
Workflow Action problem
Hi, I wondered if anyone can help with the following.

I have a workflow trigger setup to that when a new record if created that meets certain criteria, 5 new records within the same table are created. That works fine.

What I cannot get to work is the nest stage ....

When a new record is created in this table, there is a calculation field which (via another trigger) takes the product of that field and copies it 'hard' into another field within the same record. (basically otherwise this product would move as it is based on current # of records.).

It works fine for the 'instigating' record, but it doesnt kick in for the 5 'auto' created records.

Am I pushing this too far? Do workflow trigger of the type 'recorded added' not recognise new records themselves a result of a workflow?

Thank you!

Rebecca Sell
Date Created
12/19/2016 9:14:07 AM
Date Updated
2/14/2018 5:49:28 PM
Rebecca Sell 12/19/2016 9:15:38 AM

is the next stage, .... not nest stage.
'record added' .... not 'recorded added'
Slava Shinderov  Staff  12/19/2016 9:25:35 AM
@Rebecca: cascade triggers are not supported by design. In other words, workflow action creating a record in table "B" won't raise record change trigger in that table. This is done intentionally to avoid infinite loops.

Please consider calling your workflow action using time-dependent trigger on 0 days after/before "Date Created" for these newly created 5 records.
Kim 2/14/2018 5:24:46 PM
@Slava Shinderov: This is an amazing workaround for cascade triggers, that we would like to use quite often. However, it would be amazing if it would be possible to set the same filters as on 'Record Change' triggers (the 'when value changes in') column, because the workaround now is to have the initial trigger action also set a specific date field for that action, so the correct time-dependent trigger can be triggered. Having that filter would make that a lot easier.
Kim 2/14/2018 5:49:28 PM
Or, allow a setting on a record-change trigger that allows it to run on cascade...
Back to Search Results