Disallow empty primary key in the master tables
Available in license(s): Finance
When this app is installed, it is strictly disallowed to create a record with an empty primary key in a master table, nor is it allowed to rename an existing record to a record with an empty key. This prevents many fouls and mistakes that may occur if records with an empty primary key would exist. It is not uncommon that if for example an Item with an empty primary key would exist, users would forget to fill a sales line with the type Item with an actual No. This leads to all kinds of issues, for example the flowfield “Completely Shipped” on a Sales Order would never be shown as True.
When you try to create a G/L account with an empty primary key, the application will prevent you from doing so.¶
If you (accidentally) attempt to create a G/L Account where the “No.” field was left empty, then this will be blocked by an error that is raised to prevent further issues.
When you try (by accident) to rename a Resource to an empty primary key, the user will encounter the following message and will not be able to continue¶
If you (accidentally) attempt to change the “No.” field for a Resource to empty, then this will be blocked by an error that is raised. This prevents that references to the Resource are renamed to an empty value, which is something that you should avoid, because otherwise you cannot make a proper distinction between an actual empty value in referencing fields or a reference to the blank resource.
