Adding a second record for the same ID to a Table using a Trigger

[vanderLeest]

I am trying to add via an Insert trigger a second row of data, based on the first row of data which is inserted by a trigger associated with another table.

The Awards table has an start date and end date of the project, and on insert creates the first milestone in a Milestone table,  based on the entered start and end dates for the Award.

On insert of the first milestone, I would like to add (if at all possible) a second milestone if the remaining period for the period is bigger than 12 months (which is calculated in a formula field in the first record).

I get a "Triggered Action cannot be enabled because it exceeds maximum nested level of 1" Error message.

Any help appreciated

 

[Brasovan]

Howdy Vander.  I would suggest adding the InsertAction shown here as a second action of the awards table trigger.  This way you aren't cascading triggers, it's all done in one place.

Question, are you trying the Milestones to the Awards?  If yes that might create some challenges but there are solutions for that also.  I hope that helps.

[vanderLeest]

Thanks Brasovan,

your comment put me in the right direction.

I have created a multi-step trigger on the Awards table which generates the financial milestones for up to 6 years, and any shorter period in between, based on a set of IF statements and a calculated value of the next financial year end (and start of the next one); the budgets are attributed based on the total award divided by the  number of months of the project duration.

[IamNatoyThatLovesYou]

Hello Everyone, just wanted to share this documentation that you can refer to regarding the nested levels. https://howto.caspio.com/tables-and-views/triggered-actions/#:~:text=Maximum number of nested levels

[NiceDuck]

From what it looks, it is not a cascading issue but a recursion error. 

Your current trigger is set to run on insert. This means that it will run when a record is inserted on your parent table which is the 'T_PA_Milestones'. However, you have an insert block your trigger that insert records to your parent table.  Cases like this are not possible since it will cause a self recursion or infinite loop. 
 

.

[NiceDuck]

The same can be said on update triggers and delete triggers.

Update triggers must not have an update block that update records on its parent table and delete triggers must not have a delete block that deletes records on its parent table.

To be short, your trigger should not be set to activate itself.

[IamNatoyThatLovesYou]

On 8/31/2022 at 4:10 PM, IamNatoyThatLovesYou said:

Hello Everyone, just wanted to share this documentation that you can refer to regarding the nested levels. https://howto.caspio.com/tables-and-views/triggered-actions/#:~:text=Maximum number of nested levels

Hi Guys! Here is an updated documentation for the nested levels as the old one is no longer available. https://howto.caspio.com/triggered-actions/triggered-actions-2/#:~:text=Date%2C and Variables. -,Limits,-Depending on your