Error message for cascading Dropdowns with Null value

[Charliemacdmv]

Hey all,

I have Cascading dropdowns. Obviously, the dependent dropdowns are blank until the previous one is selected. My app throws up this error every time I use it. The app works perfectly fine. Any way to remove this error?

[BCLS776]

To address this error, add a way to handle the situation where the first dropdown has no selection. This can be done either through a Default property, or using an If() statement on the second dropdown to control what happens when there is no selection on the first one.

Hope that helps,

Bryan

[sgtsnacks]

Hi Charliemacdmv,

Can you share how you're defining/populating the items of your child Drop Down menus? Are you running any error handling like IsBlankOrError()?

[Charliemacdmv]

This is what i have for one of the cascading... 

Filter(CauseResolution,LOB= LOBdd.Selected.Result).Cause

I don't have an IsBlank or Error.

[AmDev]

Hi @Charliemacdmv 

I see you have LOBdd.Selected.Result - are you using a distinct function to define the items in your drop down? - If so, your app is having to work harder to surface those items in the dropdown, which could be causing a sequencing issue.

If this is the case, can you try creating a collection to compile your drop down items OnVisible of that screen and bind that collection to the items property of your dropdown.

I'm assuming this is SharePoint and I'm sure you are aware that distinct and clearcollect are not delegable so this will only work properly in the long term if your item count does not grow beyond your delegation limit.

Hope this all makes sense / is relevant to your case - Good Luck!

[Charliemacdmv]

I will give that a try. Thank you!!