It looks like Text formatted list properties can be marked as required fields in the New UX forms which is great. However, we'd like to be able to expand required field types to include:
An example of why we'd like the additional formats to be required is that we are using a form to allow Sales Managers to create a "TBH" (to-be-hired employee) on a Sales Rep list. We'd like to have a clear way of indicating that the list item created with this form was a TBH so that we can generate a specific TBH code. If we had a required boolean property, this would be very easy as the Sales Manager would have to select "Is a TBH?" in order to create the item. Alternatively, if we had a required list formatted property we could force the Sales Manager to select either "TBH" or "Sales Rep" thus definitively indicating what type of item has been created.
Even though we can still include these fields today, they are optional and not required, therefore there's risk of user error. We can also create a required text field, but have no way of ensuring data is entered in a consistent format.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.