Create power app from dataverse tables

[Tal22]

I successfully exported 5 tables from Access into dataverse.  Unfortunately, there are two barriers trying to build Power Apps using dataverse tables. 

1) There is not a way to automatically create a power app from a dataverse table(s).

2) Power Apps only supports 3 links / 3 tables. 

I was under the impression that I could use Dataverse as a relational database using power app forms. Apparently Power Platform is still in beta development. Does anyone know when the platform will be ready to deploy apps using Dataverse tables?

[dpoggemann]

Hi @Tal22 ,

I have migrated many Access databases to Dataverse over the years with great success.  One application combined 13 access databases together into a single Model-Based Power Apps.

If you have the dataverse tables built you can add forms, views, business rules, etc. within the Dataverse environment per table and then create an Model-Based Power App that brings these together.

Can you explain your point on the "Power Apps only supports 3 links / 3 tables?  Most of my environments have 10s to over 100 tables with many relationships (1:N, N:1, N:N).

[Tal22]

Thanks Drew. I guess I should have mentioned that I am an Access developer that does not know Power Fx which is required to build Model Based or Canvass apps.

As for tables, the Power App environment only connect to three tables on my end, so I am astonished that somehow you manages to connect 10 to 100 tables, given that Dataverse is not a fully developed product. 

In any case, I am looking for a no-code/low code tools, but Microsoft doesn't seem to offer this at the moment. That said, until I learn Power Fx, I will distribute my Access using Dataverse tables as the data sources and splitting the Access DB for the front end forms. Can you suggest the best practice to split my Access DB for distribution in this context? 

[LinnZawWin]

@Tal22 

For building model-driven apps, you do not need the knowledge of Power Fx and you can configure with no code. Power Platform is a pretty mature platform and not in beta development and there is no such limitation for the apps to only support 3 links / 3 tables. 

Here are some useful information for you to get started with model-driven apps in Power Apps using your Dataverse tables.

• https://learn.microsoft.com/power-apps/maker/model-driven-apps/build-first-model-driven-app
• https://learn.microsoft.com/training/paths/create-app-models-business-processes
• https://youtu.be/LIC8DFW8fOE?si=zQiqu8bH2KskRuFG

[dpoggemann]

Hi @Tal22 ,

Dataverse has been around for MANY years, before the name was Dataverse it was part of the XRM framework which supported the Dynamics 365 for Sales applications.  This is a very robust product...  I build model-driven applications in this platform regularly.  See the following blog I wrote a while ago on this:  Power Apps: Azure SQL vs Dataverse - Heartland Business Systems (hbs.net) 

Hopefully this helps.  There are a number of Learn resources from Microsoft to help you build model-based applications with no-code / low-code and even incorporate Canvas apps within this if needed for specific functionality (or pro-code if needed).  See here:  https://learn.microsoft.com/en-us/power-apps/maker/#model-driven-apps 

[Tal22]

Thanks for the links, but I have looked at these before. Unfortunately, my knowledge with VBA and Access does not translate in the Power Apps language. Perhaps I have confused the term Power FX with IT/Software engineering knowledge which is required to use Power Apps. 

[Tal22]

Thanks, dpoggemann, but I just mentioned, I don't have a degree in IT and computer sciences, so I am not able to use Power Platform, which is designed for users with computer science degrees.  And, as I just discovered, Dataverse does not support the rich tool sets that Access does, like queries and reports, referential integrity and cascading events. DV is not a true relational database. Maybe it will be someday. 

[dpoggemann]

Hi @Tal22,

If you would like to talk in more detail on Power Apps, please private message me.  This is truly a no-code / low-code environment and I have built many systems with no code and very quickly!  I would be happy to review with you and verify it makes sense on a call.

[Tal22]

Hi, I can create basic three page Power Apps from Sharepoint lists but not from Dataverse tables. I am thinking that I may have a different Power Apps license than you. I have used a lot of software including complex visual effects software for film and television and have easily built low code apps using Kintone (which is light years ahead of Microsoft.)  Apparently, my Power App license does facilitate creating apps from Dataverse. 

Notice the Dataverse table created below from the Access table. The Primary and Foreign Keys are displayed but, unlike in the Access form, the names are not. This means I cannot use a Dataverse form because users would have to cross reference the Keys to ascertain the names, which is not at all even remotely user friendly. My conclusion is that Dataverse can serve as a backend data source for Access but it cannot serve as a stand alone cloud app because the there is not a practicable form solution. And this eliminates the prospect of creating mobile Power apps from Access - Dataverse tables. 

I want to build data base apps using Access and not Dataverse. I will revisit Dataverse if and when Microsoft figures out a way to create usable forms from Dataverse tables imported from Access. I appreciate your offer but I am going to explore cutting my organizations Power App subscription cost from our budget. Instead, I will propose a tried and true SQL solution. Can you recommend an easy to use, affordable SQL server solution?

[dpoggemann]

Hi @Tal22 ,

Again, offering up that this is an education thing.  I have done this a lot in the past and you can create great applications with no code.  Yes, you would need at least a Power Apps Per App license ($5 per user / month) to create the model based Power Apps on top of Dataverse.  Any user that would utilize the application would also require a minimum of the same license.

I would be happy to explain more in a 30 min or 1 hour call if you would like.  

If you want to continue using Access, you can put a SQL Server backend behind this and continue utilizing that platform if desired.