This may already be a known issue in the community, but this week was the first time I encountered the problem. You will notice when creating a table within a scoped application, as you create fields the field names in the dictionary do not begin with u_ .

This is great, but this week I encountered a customer naming a True/False field type a value that started with a number. They were seeing INVALID_CHARACTER_ERR as an error upon commit. I am not sure what other field types may have this problem, but maybe as best practice don't name any columns starting with numerics. There can be several weird form rendering side effects with formatters and other things.

Remember you can use a label for a column field, if you want, that is different than the field name (labels can include or start with numerics).

Avoid starting field names with numerics.