We would like to hide any Option or Enum values that we don't want users to enter. A simple example is the Debit/Credit field in the Chart of Accounts. There is an option value "Both" that we don't want used. We have some GL reporting that looks at this field, and based on if the value is Debit or Credit, the calculation is different. If Both is used, it throws off the formulas. It is my understanding this field has no functional value in BC.
There are other fields where we don't want to show Options or Enums that should not be used.
It does not appear that the ValuesAllowed or OptionMembers properties can be modified in VS Code for standard fields. I know it can be done for custom fields in Table Extensions.
What is the correct approach to limiting the value options? Do we have to add new fields to tables and pages, hide the existing Page fields, then add triggers to update the base fields with the correct values? Seems a bit much.
Thanks.
517
Share
Report
All responses (
Answers (
