The community member has a field called "Name" in Airtable, but is concerned that renaming it later will break the connection with Webstudio. They tried using the field ID instead, but it didn't work. The community members discuss that it's generally better to use field IDs over field names, as names can change. Some suggest duplicating the field, maintaining changes on both, and then dropping the old field once the transition is complete. Another community member mentions that in Webstudio, the expression sometimes shows the field ID instead of the name, which can appear as "gibberish" to users. Finally, a community member confirms that it is possible to bind expressions by field ID in Airtable, and provides a link to the relevant documentation.
Right now I have a field in Airtable called Name. But if I rename that later, it's going to break the connection with Webstudio. I tried placing the field ID in there instead fldi9VKxKWO7AOy6n, but didn't work.
Makes sense to prefer field IDs over names, right?
Same with variables in webstudio. If you copy the expression and paste into text field you see the name is actuall an id. And sometimes users see it as gibberish