The Field Type You Pick in Ten Minutes Is a Ten-Year Decision
Mei runs procurement at an equipment manufacturer with about 700 people. Their platform went live three years ago. Last month she asked me a question that sounded like a two-minute request. "Sales wants to sort the contract amount from high to low. Right now it sorts like text. Can we just change the field type?" The field is amount. It was created in the second week of the project, in a workshop…
Choosing a field type in a low-code platform may seem like a minor decision, but it can have far-reaching consequences that last for years. In a platform where the field type is the structure itself, picking the wrong type can lead to significant headaches down the line. An analyst's choice of single-line text for an amount field three years ago has now turned into a six-week project due to the limitations of that type.
The field type determines what the database can do, affecting indexing, sorting, and reporting. For example, single-line text is a bounded string, while a decimal type would allow for precise calculations and sorting. Additionally, the type can impact the number of states an object can have, such as the three states of a procurement approval (approved, rejected, and unviewed) being stored as null instead of a third state.
When changes are made to a field type, the impact is far-reaching, requiring data rewrites, updates to expressions, and even migrations. In a low-code platform, the natural tendency is to add new fields, but removing or changing existing field types can be a costly and complex process. This creates an environment where decisions made in a few minutes can have long-lasting effects, often without the original decision-maker fully understanding the implications.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
