This question sits at boundary of bug & how-to: is there a mechanism, within a glide app, to force a re-fresh / re-compute of the columns in a Glide data sheet? The issue that I observe is that in certain critical circumstances, computed columns (e.g., math columns) do not update with sufficient timeliness during custom actions triggered by a form entry, and this causes ‘blank’ data to be passed causing bugs. Here’s a specific use-case example:
The use case starts with the user entering information for a new calendar event in a Glide form. This data then populates a Glide data table–no issues–and my Glide data table is then meant to compute a few items from this data (e.g., Unix Timestamp), also no issues. For the desired user experience, as part of a custom action triggered by form submission, Glide should pass along certain data to a web hook. So, user enters calendar info for an event. Glide then computes a few items from this data… and then Glide app is to pass that information to a web hook to invoke an external SMS service (Integromat–>JSON–>ClickSend).
Here’s the trouble: in execution on a Glide phone app, the computed data (in this example, Unix time stamp computation) does not get passed to the web hook–it’s just left blank. The rest of the use case and data flow (and JSON/Integromat/ClickSend) work correctly. The missing data seems to occur because the computed (Unix time) column doesn’t update quickly enough on form submission.
Is it possible, within the form-triggered custom action, to force Glide to update a table’s computed columns so that the app passes along a complete set of data?
All constructive suggestions welcome!!