When we insert a header record in a new HD, the header pre-triggers fire. Then, when we insert a new detail record, both the header and detail pre-triggers fire again. Finally, when we save the HD, the same triggers are executed once more. What’s the most optimal way to reduce this redundant proces…

Best Practices for Reducing Redundant Trigger Execution During HD Saves

brendan.b July 15, 2025, 7:25pm 4

@kendra.b’s Option 1 or @prema.vivekanand’s suggestion are both preferred over Option 2. See here for some more discussion of the potential data integrity risks associated with Option 2.

Topic		Replies	Views
Is it OK to directly update Detail records outside of a H/D structure? No-Code Platform	5	45	July 8, 2025
How can I copy only Header record in a HD Structure when using Copy Action on an App? No-Code Platform logic-blocks , Feature-Request	8	46	September 5, 2025
Clarification on Logic Block Action Behavior: In-Memory vs. Database Transactions No-Code Platform logic-blocks	4	33	October 7, 2025
How well does NW handle deletion of HD entries where a particular header has a very large amount of detail lines No-Code Platform	1	25	December 2, 2025
Post Process logic block customizations and table triggers No-Code Platform	4	44	October 16, 2025

Best Practices for Reducing Redundant Trigger Execution During HD Saves

Related topics