I know the "Fixed custom list" validates that the transaction level entries must come from the list, but this applies only to transaction entry and not when defining the custom values.
- Is the ability to create duplicate tag values in a custom list configuration expected behavior, or could it be a bug?
- If this is expected behavior, are there any native/out-of-box validation features I am missing that would prevent duplicate values?

Report
All responses (
Answers (