Love that we have JSON formatting of form layouts. However, the lack of ability to do anything meaningful when formatting the body is frustrating! One of the most common use cases for form development is completely missing, specifically the ability to selectively display selected fields based on values of other fields. Some real-world use cases include:
hide administrative fields on a form unless the current user is listed as the item owner or a status field is set to a particular value.
Enable cascading dropdown fields that selectively hide when a value is selected in a different dropdown.
It looks like this could be there except for the approach of adding fields not listed in the layout at the end of the body. Sometimes it is OK for fields to not be displayed in the body. Declarative customization should support this!
Caleb
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
ID: 0f6aeedd-a76d-88b0-7ed5-93e20ac218bc
Version Independent ID: 64315895-1103-d5f6-0195-9b5b61211132
Vesa,
Love that we have JSON formatting of form layouts. However, the lack of ability to do anything meaningful when formatting the body is frustrating! One of the most common use cases for form development is completely missing, specifically the ability to selectively display selected fields based on values of other fields. Some real-world use cases include:
It looks like this could be there except for the approach of adding fields not listed in the layout at the end of the body. Sometimes it is OK for fields to not be displayed in the body. Declarative customization should support this!
Caleb
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.