Assume a new record needs to be created a many columns of the record need to be updated. In a Tulip trigger, this is done using multiple “Data Manipulation” steps. This can cause bad performance because each record column is updated individually. An example can be seen here:
Work Order Tracking / Production Control - Show and tell - Tulip Community
Notice how after clicking on “Create Order”, the entries on the right hand side are slowly populated individually.
I am proposing a mechanism for the App creator to say they want to update a table record and list multiple columns in one go. Example:
Data Manipulation
Store
Table Record
[Value 1] to location [Column 1]
[Value 2] to location [Column 2]
[Value 3] to location [Column 3]
Today, this can be achieved by creating a Table API connector function. However, it would be better to offer this in the trigger editor.
Benefits:
- Trigger logic is simpler
- Updates could be created in a transactional way (e.g. all or nothing)
- Triggers execute faster