Solved: Grouped Action To Multiple Tables - Page 2

RenatoE · 02-27-2020 04:09 PM

Business transactions are first recorded in the journal and then they are posted to respective ledger accounts in the general ledger. This requires the use of two tables and the simultaneous recording of the transaction in two different tables.

I my case in particular, which is an inventory app, I need and action to deduce a quantity to the inventory, then I need to register this action on a Journal Table, then I need to add this product to the shipping table which contains multiple items for shipping.

A Grouped Action would solve this problem as follows:
Action 1: Deduct from Inventory = (on hand) - (shipping qty)
Action 2: Record this transaction on the journal: LINKTOFORM(JOURNAL_FORM,ETC,ETC)
Action 3: Record this transaction on the shipping Table: LINKTOFORM(SHIPPING_FORM,ETC,ETC)
Action 4: etc etc

Unfortunately only one LINKTOFORM() action can be executed. Action 3 is never reached.

To do this I need another separate action, which seems wasteful and adds more clutter to the app.

RenatoE

After much digging around I finally got it to work. Why is this stuff not clearly spelled out somewhere?

You are correct about the ability to trigger the next action, this can be done from the previous action once it is completed.

How can this be accomplished?

The end of the previous action is when the form is saved by the user.

Where can this form be found?

This form is not automatically shown, it is hidden in the UX interface and you have to click on the “Show system views” near the bottom of the page.

Once this opens you will see the form view specific to the current table, this form is automatically generated and is responsible for the interface and fields that need to be completed before the save button is applied by the user.

In this form under the Behavior section can be found the Event Action “Form Saved” and next to it is the drop down menu where the next action can be found. As you said before this action has to be pre-configured in the Main Behavior Section for the current table.

So yes, thanks for the help. Now I can cascade these actions as needed,
but it would be much easier if the LINKTOFORM() could be used directly on the beginning table.

And… yes you gave the solution but for the sake of clarity I have marked my post as the solution. Hope that is ok with you.

View solution in original post