Conditional Branching is here for Lists! 🎉 Here's how to use it.

[@martinschlenker6145]

Thanks Christine ! Nice work.....

[@GaborCsorba]

It worked! When I created a new list, as you suggested, the branching option appeared on all existing list forms, many thanks for the tip. Just to note, the branching doesn't work on multiple choice columns either, which would be useful when you have 'Other' as one of the multiple choices, for instance.

[@bi-ome]

That's a good tip on the multiple values, I didn't think to check that!

[@daveboylan247]

Nice to know this feature is starting to land. I'm still waiting 😮. Thanks for sharing!

[@daveboylan247]

Hey again Christine! I'm wondering what the best practice is for 'required fields' with conditional branching. For example, When I branch to a section that does NOT include some of the "required" fields, the form submission works, but the angry list view then flags those fields with yellow "Required info" warnings. I want the fields to be required within the branch where they appear on the form, but not required in the overall list view. Is there a way to accomplish this? Thanks again for you great work here! Dave

[@bi-ome]

That's a really great question. I am pretty sure you'd have to give up the "new form" experience and go with either the classic form or a Power App form. You can use "content types" to create multiple forms in a single list - where you can set which fields are required on each content type and even have different fields on each. This is how I used to handle different types of tickets in a list - instead of a conditional branch on a dropdown, you make your content types your dropdown and each content type can have different combinations of fields. Just make sure to add the fields to your content types in list settings or site settings instead of from the list view - the modern list view doesn't recognize when you're trying to add fields to a specific content type and trips on itself. Or use the Power Apps forms to handle the branching/required fields, but that's a bit of a pain. Unfortunately content type doesn't show up on modern forms (?! why why why... hopefully they add it!). Not sure if there's a video out there on using these in lists or not, maybe I should put that on my list...

[@Ploplox]

Guessing we can't make a field mandatory based on previous value selection yet? Having to keep using power apps for that which is fine, but it's definitely more work haha

[@bi-ome]

Naw, it's simply letting you jump to questions essentially. I wouldn't hold my breath for that anytime soon - I hear you on the Power Apps though, once you go there the maintenance becomes a bit of a problem lol.

[@Ploplox]

@bi-ome yeah for sure! Hard to go back once you make the jump though 🙃