In make.com , if I create a scenario and all works, it will definitely break if I change the name of the field at a later time in SmartSuite. This is unusual behavior compared to competition like AirTable where it checks the name, and if it doesn't match, it updates it based on field ID. For a simple example, in SmartSuite I'll have a field called "Project Name". I'll create a make.com scenario and have a module look at "Project Name" and use it to move data. However, if I decide that in SmartSuite the column "Project Name" takes up too much width, and just "Project" is a better name, my make script will now break. I'll find out because my scripts will get errors and/or gaps in the information. If this were just 1 module I fix by hand in one scenario, no big deal. However, if I use that field in multiple places in a single scenario as well as multiple other scenarios, its a problem. In AirTable, when a field's title no longer matches, make.com has the correct programming to query AirTable and get the updated name, so a rename of a column is dynamic.