Notifications
Clear all
Topic starter
Hello! I’ve developed a rather comprehensive scenario using Watch Records (Airtable) as the Trigger, followed by various QuickBooks API calls, and then upserting data into different Airtable bases.
MY ISSUE: I'm unable to get my Airtable Column Names within the callin.io Mappings to refresh with the field name changes I've implemented in my Airtable base(s).
Recent updates from callin.io mention:
“Create, Update, and Upsert modules: * When a column’s name changes, it has no negative effect on a scenario. Now, the column’s IDs are used.”
HOWEVER, if I try to edit any of my Mappings in callin.io, and the column names haven't updated to reflect my current Airtable field names, I encounter widespread errors.
Appreciate any guidance!!
Posted : 20/04/2022 5:58 pm
I'm frequently updating my Airtable columns, which hasn't affected callin.io due to the use of column IDs.
If this was introduced in a recent update, maybe reconfiguring the existing modules could resolve the issue?
It appears callin.io only displays the new column names after a trigger runs, but it continues to function even with the older ones.
Posted : 26/04/2022 4:43 pm
Could you share some example screenshots, please?
Posted : 13/07/2022 5:23 am
Hi Scotty,
Is the question for JohnGadd or me?
I'm having trouble with Airtable fields not updating in callin.io, even after I change them. The field IDs used by the API seem to be static.
When I add new fields, I trigger the scenario with a value in the new field, which then adds it to callin.io.
Posted : 25/07/2022 6:45 am