Hi,
As our team has grown from 1 person to over 5, we’re seeing an increasing amount of user errors, leading to costly data fixing maintenance. To some part a new user will become more proficient over time and will be able to avoid errors, but as long as it’s possible to err, humans will. The aim is to further expand, so at this point I’m taking some time to consider alternatives.
What alternatives/add-ons are there one could consider to improve the UX and data integrity? I want to stick to Airtable as the system centre, but I am willing to fork over some parts of the most used interfaces to another system, if that would bring order to the current issues. Mobile use is not critical for use, lean laptop use is.
I remember hearing about Noloco in some discussion. Would that help? What other systems comes to your mind?
At the heart of our problems are these Airtable’s inabilities:
- inability to update a record only when separate (e.g.) “OK/Save” is clicked
- inability to force interface fields to be required in record updates
- inability for data validation before saving it
- inability to build a conditional record update interface
(1) we have customer meetings which lead to recording 5-10 decision points about their needs. Only after the meeting is ready do we know the whole picture, and what path in the customer journey the customer should continue on.
I don’t want anything to happen in the back-end before everything is gathered, and I want an “OK/Save” button with notifications and warnings like we have for general interface buttons.
(2/3) since a record update interface cannot have required fields/choices, it means a lot of data validation and sanitisation will need to happen back-end. In practice it’s very cumbersome, error prone (missing “innovative” inputs the users invents), and eats up automations. Additionally it comes too late when some automations may have been initiated based on erroneus data, and reversing stuff is very time consuming.
(4) having later update record interface fields’ options defined by earlier choices is needed for same reasons as (2), it keeps the data tidier AND saves user time when not having to wade through irrelevant options.
Appreciate any and all input!
Cheers,
Björn
