Hi, I am surprised and yet not surprised by my Helper IV rating. That is just another example of just how poor Microsoft tech can be. That said, my post here was contained to using Dataverse in Teams and not outside that environment. As to learning Power Apps, I don't see the value in that. As an Access developer, PA falls flat as a solution for the rapid creation and deployment of Database apps. I just don't see the value in having to learn code to create and customize forms from data tables that easily can be done in Access. Yes, I can create apps from SharePoint lists using the Integrate function. It is building an app from scratch that I find way too difficult - way more cumbersome than it should be.
With the exception of Lisa Crosbie's video, which I have not seen yet, many other videos assume viewers have advanced coding skills. In short, and this is a common complaint, there is not a clear, methodical pathway to learning PA that I know of.
I learned Access first by exploring Access template DB's to see how they work. And then by tutorials by Richard Rost. The Access GUI is logical, well organized and fairly easy to learn as well as the basics of VBA code. Conversely, the Power Apps GUI and logic is convoluted and not well organized. It took my only a few weeks to learn Access and build pretty nifty apps. Not so with Power Apps. This is because Access was built for citizen developers while Power Apps was built for people with heavy coding experience. From my experience Access/SQL UX, very good. Power Apps UX, confounding.
Microsoft cobbled Power Platform together with legacy applications, which is why the UX and UI sucks.
I apologize for being inconvenient. This will be my last post here.