The number of each field within its parent table object is the unique identifier that Business Central uses internally to identify that field. We can easily change a field number when we are initially defining a table layout, but after other objects, such as pages, reports, or codeunits, reference the fields in a table, it becomes difficult to change the number of referenced fields. Deleting a field and reusing its field number for a different purpose is not a good idea and can easily lead to programming confusion.
We cannot safely change the definition of, re-number, or delete a field that has data present in the database easily. The same can be said for reducing the defined size of a field to less than the largest size of the data that's already present in that field. However, if we force the change, the force function will override the system's built-in safeguards. This action can truncate or delete data.
When we add new fields to standard Business Central...
