Power Platform Community Forum Thread Details

Hi,

I have set up a basic Power Apps page as a test internally but have an issue on how the Dropdown fields are working when we have a "Depends on" set up on these fields. I have tested this using the file on my One Drive and also set up in Teams and both cause the same issue. Any help would be appreciated on this

The way this has been set up is as follows

1: Two Drop down fields have been added to the form looking at tables in an excel document.

2: The second field is dependant on what is selected in the first field

This works locally when testing via Preview, but when publishing this app, the issue occurs where it seems to be trying to load dropdown 2 before dropdown 1 has been loaded so we get the following error message

"The requested operation is invalid. Server Response: Processes failed: Expression "ProcessAppID eq null" is not supported. clientRequestId: c2d63ee7-dd64-4244-990b-176c9a8f7405 serviceRequestId: ac154110-c1fd-464d-be89-3d9dc493d625;ce360e1e-8f27-42a3-8161-52bb112c780e;01954908-3846-45c6-a434-392808a88c7a"

When reviewing this via the Monitor, when the depends on is added, it changes the way the processes load. If we have no depend on setting, the first field is loaded, then the second field but as soon as you have the Depends on set up, this changes.

Hopefully these screen shots will help - The Bad Request Monitor information is when we have the Depends on settings in place.

This is the Dropdown FieldsDepends On settingsBad RequestGood Request when no Depends on value