Thank you for choosing Microsoft Community.
It sounds like you’re facing a common issue where the Yes/No column in Dataverse is being interpreted incorrectly in Power Apps.
Here are a few steps to troubleshoot and resolve this issue:
Verify Column Type in Dataverse:
Double-check that the column in Dataverse is indeed set as a Yes/No type. Sometimes, it might appear correct but could have been misconfigured.
Check DataCard Default Property:
Ensure that the Default property of the DataCard is set to a boolean value. For a Yes/No column, it should be true or false. If it’s showing as a choice, it might be due to a misconfiguration or a bug.
Recreate the DataCard:
Sometimes, deleting the existing DataCard and adding it again can resolve the issue. This forces Power Apps to re-evaluate the column type.
Use a Toggle Control:
If the toggle control isn’t available, you can manually add a toggle control and bind it to the Yes/No column. Set the Default property of the toggle to Parent.Default and ensure the Update property of the DataCard is set to the toggle’s value.
Check for Known Issues:
There have been known issues with Yes/No columns in Power Apps. Ensure your Power Apps environment is up to date, as some bugs might have been fixed in recent updates.
Use a Patch Function:
If the issue persists, consider using the Patch function to manually update the Yes/No column. This can sometimes bypass the UI issues.
If these steps don’t resolve the issue, it might be helpful to look at specific error messages or logs for more detailed troubleshooting.
Let me know if you need further assistance!
If this fixes the issue, please mark as resolved to help others with find it.
Happy to help
Robu 1
