Hi folks,
I have a very simple app in final testing. I’m seeing inconsistent performance of lookups from a glide big table to a glide regular table from a single relation (Row ID match for a location). Big tables (even with its limitations) was one of many selling points of jumping into Glide over alternative solutions.
In Big Tables | Glide Docs mentions limitations of “Multi Lookups into Big Tables (eg. Lookups via Multiple Relations or Lookups that target an entire Big Table column)” Emphasis on into big tables not from and via Multiple Relations. This is from a big table into a regular table and via a single relation. I have a support request open on this as well just seeking anyone else’s experiences or guidance here. This app is really important to the company and could affect as much as 30% of order volume.
Background on the app:
Two tables:
Big Table is a pickup request. Regular table is locations. Tables are related via text field “Location” in the big table which is the Row ID in the regular table. Big-Table has lookup fields via this relation for name address, city, state, zip, latitude, longitude, etc. This pick up requests big table will exceed 25,000 rows quickly when released to production. The locations regular table will likely never exceed 1,000 rows.
How the app works:
- Users scans a QR code specific to specific geographic sites with URL parameters being captured with Get Part of URL column | Glide.
- Example: http://examplesite/xyz?location=3M1-lSu-Q9KsIjOOWSvGMw Location 3M1-lSu-Q9KsIjOOWSvGMw is a row ID in the regular table.
- User completes one or two fields: image(s) upload (required) and notes (not required)
- User clicks submit and a custom action is triggered
The submit action:
- Set the column value for location in big-table based on the Get part of URL. That part executes just fine and always comes through to the webhook. This is also the key to the relation for the lookups.
- User is navigated to a confirmation tab
- Webhook is triggered to Make.com relaying data to an API for another piece of software
The challenge:
Sometimes the relation derived lookup fields are being sent to the webhook and other times not. It appears to be a performance/timing issue on the lookups in the big table into the regular table. I have introduced as much as a 10 second (!!!) wait before the webhook into the action and I am still seeing this issue intermittently. Without the lookup fields the data sent to the webhook is useless.
It is critical that the user get an accurate response that the data was successfully submitted.
Thoughts:
- I could expand the set column values part of the action to set text fields in the big table from the lookups instead of relying on lookup columns in the webhook part of the action but that seems totally redundant and backwards.
- Make the regular table also into a big table? Unclear if that has performance advantages.