Hi guys,
I noticed Airtable field names don’t automatically update in routers.
For example, in this router the mapped Airtable field is called Messages Count, but I changed the field name back on Airtable and it’s now called Message Count.
I circumvent that update issue in Airtable modules by toggling on the ‘Use column ID’ feature.
But it doesn’t look like there’s such a feature on routers. Any workaround to suggest?
Thanks.
Hi @JBJ
Hover over both the variables and see if the raw variable name is same or not. if it is same, it will work. If not, then you need to map the new variable.
Regards,
Msquare Automation - Platinum Partner of Make
@Msquare_Automation
Hello @JBJ,
Note: I’ve also explained my testing results because it requires understanding first. Please read things carefully.
I’ve cross-checked these things.
This is a feature for users who change the field names frequently.
During my testing, I’ve used Airtable’s Get Record Module to get a single row from Airtable where the table has only 2 fields(Email, Status).
Then use Router after that setup filter using the field Email;
→ On this one, I’ve tried things with the setting Use Column ID → No
→ Then run it as normally. It passes the filter because it’s just a first run.
→ Then change the field name Email → Emails.
→ Then run it again, and this time it didn’t pass the filter. Because the field name is changed which is used on the router filter.
You’re right here. when Use Column ID → No you’ve to be careful about specific field names.
After testing this the field name is back to Email.
→ Now first thing is disconnect that Airtable’s Get Record module from Router
→ Before I do this test I know that I’ve to clean up all field references from all the other modules where used based on this module.
→ Now set Use Column ID → Yes.
→ Run only this Airtable’s Get Record module again. If this is the first module then give some static recId OR if it’s not the first module then give the recId when it asked.
→ Now do all other necessary settings about filters and fields mapping to other modules.
→ Then run it as normally. It passes the filter because it’s just again a first run.
→ Then change the field name Email → Emails .
→ Then run it again, now it’s run the same as last time. Even though we know that the field name has been changed. Because this time it uses field ID reference.
→ Another important thing is in the router filter setting it still shows the field name Email.
→ Here you’re also right that the field name has not changed but then I’ve cross-checked the results of Airtable’s Get Record. There is a field shown as Email.
→ Even though if you again change the name of the field from Emails->EmailUpdated it still works.
→ What I found here is they used field ID as a reference and the field name(label) they stored in the module setting that comes on the first run. No matter how many times you change that field name it always shows you Email on the results of Airtable’s Get Record module.
Until now this is a point where we are on the same thing that you mentioned on the original topic how to update/change that field name on the router.
→ Disconnect the Airtable’s Get Record from the Router module.
→ Set module settings to Use Column ID → No.
→ Then run it again.
→ Then Set module settings to Use Column ID → Yes again.
→ Now again reconnect the Airtable’s Get Record to the Router module.
After that check the field names of the filters used in other modules.
You wonder that all the field’s name is changed according to new changes.
Just try it and I hope it also works for you as well.
P.S.: Always search first, Check Make Academy. If this is helpful, mark it as a solution 
and 
Need expert help or have questions? Contact or comment below! 
Hi @dilipborad,
Thanks for the extended explanation. If other people run into the same problem in future, here are the recordings I made of the tests you lay out:
