This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
I have an action that occasionally writes incorrect data to the sheet when I test it as a single user. The following factors seem to be at play:
The action counts the number of virtual columns with a certain value, which in turn, depends on a LOOKUP() expression that looks up a value in another table.
The action can occur before a sync is complete
If the sync has not been completed before the action is invoked, an erroneous value is written. If, on the other hand, the sync has been completed, all is well.
One other possible factor is the lack of a parent-child between the tables. That was pointed out to me when I contacted support@appsheet.com and that led me to post the following:
I plan to contact support about this again but, in the meantime, I find it hard to believe that I’m the only creator for whom this is a potential issue. So, I thought I would ask about your experiences and opinions about this sort of matter.
My own feeling is that after a user changes a value, any value that is dependent on the changed value should not be written to the sheet in an action invoked by the same user until a recalculation has been done, with or without a parent-child relationship between tables. Would you agree? Please let me know if I’m missing something. Also, have any of you experienced similar issues with cascading calculations that occur before a sync?
LinkedIn
Twitter
