I’ve been reviewing the two Help topics, “Logic blocks and row actions” and “Header Detail row action configuration option”, I had a question based on some behavior I’m seeing.
I have a row action configured on a Header application, with the Link Type set to “Logic Block – Not in Trans Boundary (Save Required)”. The logic block triggered by this row action inserts a record into a different table.
When I debugged the logic, I could see that the insert step was hit, but the new record never actually appeared in the target table. However, I noticed that if I clicked “Recalculate” and then “Save and Stay”, the record did get inserted and was visible when I checked the related app.
Here’s the Help text I’m referencing:
“Requires the user to save any unsaved changes to the record before the logic block runs. Runs outside of the transaction boundary.”
Based on this description, I’m unclear why selecting Save after the row action caused the insert to succeed. In my configuration, I’m not using the setup outlined in the “Header Detail row action configuration option” topic, so I’m trying to understand the expected behavior here. Should the insert have committed when the logic block ran, or is it expected that the Save after the fact would complete that?