Trigger logic doesn't make sense?

[Casper]

Hi, hope someone can help me out on this as this is driving me nuts. It might sound stupid but its actually a very simple application of matching.

I am trying to match two numbers in Table 1 (Test) and if they matched, update the result on Table 2 (Test2). My problem is when the number matches, it shows me the result "Not matched" and vice versa. The result is inverse of the logic that I have built. Of course I could live with it, just inverse all the results but I feel that I might be missing something here so hope someone can advise me. As below are the screenshots of both tables and the trigger logic for Test Table. Thanks.

 

 

 

[sandy159]

Hi @Casper,

As far as I understood you need to match numbers on insert and update and insert the status in a different table. What this trigger does, it checks if the ID is already present in the Second table. If NO - then Insert new record with the proper status, if YES - then Update existing record.

Here is tables design as well:

         

[Casper]

Hi Sandy159, it works perfectly ! so if I guess correctly, the key point here is to use #inserted.number instead of Test.number. Got it, it makes sense now. Many thanks !!

[cheonsa]

Hello @Casper,

Just to add, #inserted refers to newly inserted/ updated record. If you use Table.FieldName format, it refers to the current value in the Table. 

For more details, you can check the Additional Notes here:

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