Skip to main content

Beware: Automations trigger on field type change

  • May 12, 2026
  • 2 replies
  • 13 views

nroshak
Forum|alt.badge.img+11

Be careful updating field types!

I have a few automations that watch a field for updates to set a field-last-updated timestamp. I discovered that if you change the field type of a watched field from multi-user to single-user, if there is data in the field, it will consider the field “updated” and trigger the automation.

This is not documented anywhere that I could find!  And it messed up my timestamps 😑

 

 

2 replies

DisraeliGears01
Forum|alt.badge.img+22

Interesting! I suppose I would kind of expect this, as single selects and multi-selects are handled differently. This sparked me to play around with this a little bit… Going from Single Select to Single Line Text also shows as an edit, but changing from Single Line Text to Long Text doesn’t unless you add RTF then it is an edit


ScottWorld
Forum|alt.badge.img+35
  • Genius
  • May 13, 2026

Yeah, Airtable is the only database app that I have ever encountered that treats a BASE SCHEMA MODIFICATION as a FIELD DATA MODIFICATION. (Yet, as ​@DisraeliGears01 pointed out, it only happens with SOME schema changes, not all.)

This is a real problem because it can be so disastrous.

The best we can do is report this problem to support@airtable.com, and suggest for Airtable to change this behavior by filling out the product feedback form at this link.

- ScottWorld, Expert Airtable Consultant