Unanswered

Turn on 'Improved data source experience and Microsoft Dataverse views'

(0) Share

Report

Posted on by hsfournier

106

I am hoping someone can help me, because I am about to pull my hair out. I have followed everything here, https://www.iammancat.dev/2023/03/enable-features-in-older-power-apps/, and I am still getting this,

And now I am getting sign-in errors. None of my apps use Dataverse, they all use SharePoint, so if I am missing some nuisance here, please enlighten me. I have had so many users contact me over the last week, they can get in, but then the App asks them to sign-in over and over again. I spent all of last week trouble shooting this and nothing is working. I thought this was the issue, but even after following I Am Man Cat's instructions (and so many other things) I am still getting the Turn On message. When I look at the ParseJson file, I have no idea which Flag is the right one to turn to True or False. I am so frustrated, and i have spent hours on my Sunday off trying to figure this out. Anyone? Any help would be appreciated.

Categories:

Building Power Apps

All responses (2)

Answers (0)

Sort by

dbmamaz 19 on at

Like
a
(0)

Report
Copy link

Link copied!

I'm also having this issue. I looked at this page: https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/use-native-cds-connector and i dont have the option in general where this indicates it could be. Wondering if government cloud hasnt gotten the feature but has the warning? I literally just created a brand new app with no dataverse connectors.
Commander_Data 67 on at

Like
a
(0)

Report
Copy link

Link copied!

Apps are still working for us, but I get this message every time I go into Settings in the design studio. There is no option to turn this on, and I also have no direct DataVerse connections. We use SharePoint list as data sources for most of our Apps. Wondering if this is a combination of 'different' settings that is causing this, or PowerApps is looking at it's internal connections that might be DataVerse, and therefore prompting this issue.
It's frustrating, as I hate warnings I cannot identify or resolve, although doesn't appear to be affecting our Apps in a negative way. We often use one App as a template for a new Apps, so this is proliferating amongst out App builds.
If you get a solution to this, please post back here, as it may help others facing this message.