trouble shoot triggered actions

[Sam23]

I am a newbie trying to write my first triggered action.

I have watched several tutorials and my trigger code validates and saves, but there is no action in the tables. I am trying to insert a record into table 2 when a record is inserted into table1. Simple enough.

What are suggestions for trouble shooting the trigger? I have validated that the tables relationship is there, that I am using the inserted data (not the table name). My trigger looks identical to examples in this forum and on Caspio videos. 

Thanks for suggestions

Sam

[Sam23]

Here is the triggered action. When I insert a record into the Contact table, I want to insert a record into the Users table taking the ContactID (primary key of the Contact table) and putting that in the User1 table as a foreign key.

[TellMeWhy]

6 minutes ago, Sam23 said:

Here is the triggered action. When I insert a record into the Contact table, I want to insert a record into the Users table taking the ContactID (primary key of the Contact table) and putting that in the User1 table as a foreign key.

that seems to be correct, try removing the the relationships first if it will work, but that should work

[Sam23]

Thanks, TellMe - Do you mean undo the table relationship and see if that helps? 

If the syntax above is correct, the issue must be something in the tables themselves. I may make some new tables and start over. 

Thanks, Sam

[kpcollier]

Another thing to note - 

• In the case of referential integrity enabled in a relationship, if a trigger executes on an insert event to the parent table, and inserts a record to the child table, the Triggered Action will fail. This is due to the action of inserting a record to the child table occurring first, thus failing the integrity check as the parent record does not yet exist.

https://howto.caspio.com/tables-and-views/triggered-actions/

[NiceDuck]

In relation to the statement by @kpcollier, The newly inserted records during trigger run are temporarily stored on a proxy table represented by "#inserted", on this case, until the trigger ends, it is not considered as a content of the parent table yet.

On additional note, make sure that you have a backup of the tables involved or do your triggers first on test tables. Trigger actions directly affects the data you have on the tables and one wrong move can make a mess of them and you will have to pay for restoration.