We run into an issue while using Make.com Grist module to update table data. While Make has lot of dynamic items like variables which can carry things like strings and normally all modules work nicely ie. we are able to deliver values using the variables.
But, not in case of Grist ‘Update Records of a Table’ module. Passing the table name as a variable shows up an error and obviously the issue is that the content of the variable is not “unfold” as it should. We do see something else as the value for the table name?
Issus is opened on Make.com and below is their answer. It might be that there is nothing we can do about this and it is not really a show stopper, just an annoyance and incompleteness detail.
Best Regards, Tomas
In such cases, for feature requests, it is usually posted here as our teams do regularly visit this site and review based on the number of demands: [link removed]
In general, for apps/features that are not yet supported, it is highly suggested to use the universal HTTP module and be sure to follow the app’s endpoint/API docs so that even if it’s not yet supported, you can still use it in you Scenario: [link removed]
If let’s say if a module needs some upgrades (for example, in your case), we will need to check first if lots of the customers are affected as well, otherwise, the request will be posted in the [link removed] If the module has an issue then we will escalate the case to higher departments for investigation and possible enhancement/fix.
About your case, the thing is that the Grist API might need to have the exact name so that the API connected to that module would then be able to read the fields and be able to get detected, if mapped dynamically, the problem is that in that actual configuration, those fields under that table won’t be detected.
So for now, I would suggest adding a router then add a filter pointing to each specific predefined (Table Name specified) modules.