Confusion between Dictionary overide and UI policies

[Abhinab Achary1]

Hi All,

I have a requirement to make certain field mandatory for some classes. which approach is better

if the fields to be make mandatory are not dependent on any other field just based on tables.

Dictionary override or UI policies? is a better approach for this.

Thanks,

Abhinab

[Anurag Tripathi · Accepted solution]

UI Policies work on the form, so if you just need the field to be mandatory then making ui policies (for individyual tables/forms) makes more sense.

If you want the fields to be mandatory regardless of the source(not just form)you can look for  Data Policies and see what suits you best

Dictionary override should not be considered to just make a field mandatory.

[Abhinab Achary1]

As you suggested,under what scenarios should be consider for dictionary override.

[Anurag Tripathi]

If you have to alter the behavior of the field form base table.

Typical EG: change the reference qualifier, use different attribute set etc. 

[dave_edgar]

if there is absolutely no dependancy on any thing I'd advise to make the field mandatory via the dictionary.  If there are some dependancies then use UI Policy.