subtables do not update from link & load even with sync enabled

Support
, ,
1

This is a strange issue, but essentially I have Table A with a subtable that link and loads to records in Table B. I have enabled sync so when I edit a Table B record directly, it will update in the Table A subtable. However, if I run a script that modifies a record in Table B, even when including entry.setIfDoLnls(true), it will not update at all in Table A subtable.

This behavior is consistent for every subtable I have that relies on Link & Load.

I have double checked that sync is enabled for all relationships in the subtable.

2

I consistently have this problem as well and as a work around reload the file manually to get it to display the correct information
I think this is a major issue as none of the instructions I have followed have resolved it. The solution needs to be a youtube video so it is easily understood and followed.
As my updated files relate to product costs, if the file does not update I can sell a product at the old price not a revised price so it is a big concern to me.
Thanks
David

3

After testing, the functionality itself is working as expected. The test procedure is as follows:
Step 1: In Form A, the subtable links to records in Form B.
image

Step 2: In Form A’s Link & Load settings, the “Keep loaded value sync with source” option is selected.
image

Step 3: The design of Form B.
image

Step 4: A action button named ChangePrice is created.

image
image765×423 7.79 KB

Step 5: Executing the action button sets the Price field of a specific record to 0.

image
image769×424 7.67 KB

Step 6: The linked data in Form A is updated accordingly.
image

workflow：
function changePrice(id){
var query = db.getAPIQuery(“/order/5”);
var entry = query.getAPIEntry(id);

entry.setFieldValue(1000024, “0”);
entry.setIfDoLnls(true);
entry.save();
}

If this still does not resolve your issue, please contact our support team(support@ragic.com) and provide the relevant form and detailed steps to reproduce the issue.

4

Interesting. I will do some additional testing and see if I can isolate the issue,

5

for anyone encountering this issue, I have isolated it to the post-workflow.

Executing a standard call like in the example above will always work, but if you modified this to execute in the post-workflow of another sheet, regardless if you use param.getUpdatedEntry or param.getNewNodeId, regardless on how you call the source record (db.getAPIEntry, db.getAPIResultsFull) the change will no longer propagate to the subtables that are listening to changes.

6

@steven2 I have submitted a support ticket though