When adding or editing an Interaction, if a Category is chosen, a Subcategory becomes required even if the Field characteristics on the add/edit form are set to required = no.

When going to the data form instance that produces the form for adding or editing and Interaction, and setting the parameters for the Interaction Subcategory to not be required, the Subcategory remains required when you add a Category. 
This is a limitation of Field characteristics in the face of UIModel logic. For the specific form, a subcategory is required when a category is supplied.

Environment

 3.0.516.54

Was this article helpful?