Airtable Field Names Not Updating in Routers

Hi

Hover over both the variables and check if the raw variable name matches. If it's the same, it should function correctly. If not, you'll need to map the new variable.

Regards,
Msquare Automation - Platinum Partner of callin.io

Hello,

Note: I’ve also detailed my testing outcomes as understanding is required first. Kindly review the information carefully.

I have cross-verified these points. This functionality is designed for users who frequently modify field names.

---

Background

What I’ve found

During my testing, I utilized Airtable’s Get Record Module to retrieve a single row from Airtable. The table initially contained only two fields: Email and Status. Subsequently, I employed a Router to set up a filter based on the Email field.

Initial Test with “Use Column ID → No”

→ In this scenario, I configured the setting as Use Column ID → No.
→ The execution proceeded normally, and it passed the filter as it was the initial run.
→ I then renamed the Email field to Emails.
→ Upon re-running, it failed to pass the filter because the field name used in the router filter had been altered.

You are correct here. When Use Column ID → No, one must be cautious with specific field names.

After this test, the field name was reverted to Email.

Important Test with “Use Column ID → Yes”

→ First, I disconnected the Airtable’s Get Record module from the Router.
→ Prior to this test, I ensured all field references in other modules linked to this module were cleaned up.
→ Next, I set Use Column ID → Yes.
→ I then ran only the Airtable’s Get Record module again. If it was the initial module, I provided a static recId; otherwise, I supplied the recId when prompted.
→ After completing all other necessary settings for filters and field mapping to subsequent modules, I executed the workflow normally. It passed the filter, again, as it was the initial run.
→ Subsequently, I renamed the Email field to Emails.
→ Upon re-running, the outcome was the same as the previous test, even though the field name had been changed. This is because, this time, it was referencing the field ID.
→ An important observation is that the router filter setting still displayed the field name Email.

→ You are also correct that the field name did not change. However, I cross-checked the results from Airtable’s Get Record. A field was shown as Email.
→ Even if you rename the field again from Emails → EmailUpdated, it continues to function.
→ My finding here is that they utilized the field ID as a reference, and the field name (label) stored in the module settings was captured during the first run. Regardless of how many times you alter that field name, the results of the Airtable’s Get Record module consistently display Email.

---

Up to this point, we are in agreement regarding your original topic about how to update or change those field names within the router.

Solution: How to change those names on the filters and other mappable fields.

→ Disconnect the Airtable’s Get Record module from the Router module.
→ Set the module settings to Use Column ID → No.
→ Run the module again.
→ Then, set the module settings back to Use Column ID → Yes.
→ Reconnect the Airtable’s Get Record module to the Router module.

<<<BLOCKQUOTE:
After performing these steps, check the field names in the filters used in other modules.
You will observe that all field names have been updated to reflect the recent changes.
>>>

Kindly try this, and I hope it yields the same results for you.

---

P.S.: Always perform a search first. Consult the callin.io Academy. If you found this helpful, please mark it as a solution

and

Need expert assistance or have questions? Feel free to contact or comment below!

Hi,

Thank you for the detailed explanation. For anyone else encountering this issue in the future, here are the recordings I captured during the tests you described: