Lock fields instead of entire tables when custom programming uses a table.
Currently, if professional service does any custom work (i.e. triggered action, etc) the entire table is locked and the user cannot do any further development using that table (i.e. cannot add fields, etc.). This causes users to have to submit tickets just to have a new field added. That can take from hours to days to get done through that process. This directly contradicts the use-case for Caspio which should allow users to develop their own apps.
Previously users may have changed a field used in custom programming which would break the programming. A support ticket would then go in and they would have to fix that. Either way Caspio has to be involved to do a fix. Why, then, do you put the bulk of the inconvenience on your customers when Caspio has to do the work either way?