GPGeorge
George Hepworth
- Local time
- Today, 02:18
- Joined
- Nov 25, 2004
- Messages
- 3,307
I didn't realize that Model apps exclusively use Dataverse. Or is that the intent of the statement. "And [model apps] use Dataverse."? Isn't it possible to create one from SharePoint lists, or even SQL Server? That's an area I know only a little about, though.Oh I'm sorry I should have clarified, I was exclusively referring to the context of Power Apps since that is primarily what it's for.
In power apps you can make two types of apps. Model apps, and canvas apps. Canvas apps allow people to do pretty much anything they feel like and although not every canvas app is bad or sloppy, the reverse is true, most bad or sloppy apps will be canvas apps. Model apps are different, in that they essentially enforce referential integrity on the back end. And they use dataverse. That is kind of what I was thinking about when I mentioned data verse being the mature disciplined component in the mix. People who make canvas apps are less likely to use data verse then people who use model apps.
I guess there is this whole other sidebar conversation going on about dataverse for access, which is not really what it's for and will probably always be quite limited.
BTW, I finally did figure out the mystery of the dataverse connector in my Access 2019 Pro. It turns out that I also have an MS 365 account, through which MS Access is available. However, I had to reinstall Access and specify that MS 365 version to be used. Then I could sign in with that 365 Account and get the full Dataverse experience working as it should.
Not yet impressed by Dataverse, though.
With regard to Pat's question about costs, this LinkedIn discussion sort of sheds some light on that. The gist of it is that licensing is not transparent.