Building Dataverse Apps in Teams?

[Tal22]

I am evaluating Dataverse for Teams. Started building an app. First I built a Table called Families

I then created a form based on the Families table. 

When I play the form I get this. 

Since the Properties menu does not have a logic control to link the Families table to the Form in Dataverse for Teams, is even it possible to build apps in this environment? Or should I stick with SQL? 

[Amik]

@Tal22 - forgive the assumption, but I am not sure if you understand how the Form control works. You are seeing that message because you simply have not supplied the Form with a record to display. It has nothing to do with the Canvas Apps for Teams environment.

As a basic example, insert a Gallery control and set the Items property of that Gallery to your Families table.

Then set the Item property of the Form to:

Gallery1.Selected

[Tal22]

The form is based on the Families table. I entered data into the Families table hoping that the Form would read the data. So, what I am hearing is that I have to create a form before the table and then enter data in the form? In Access, you can enter data directly into a table and then easily create a form of a query from the table and enter or edit data from both. In any case, I need to import existing data and it doesn't look like Dataverse app in teams allows that. I also discovered that I cannot delete Dataverse tables and Power apps in the Teams environment. They just sit there, so, to speak, as clutter.

From the standpoint of an Access developer, I find the rudimentary Form controls in PA lacking, not to mention the inability to natively create Queries. Power Apps is not even close Access.  Dataverse for Teams is not going to work for me. At least not until the platform matures to a professional grade level. 

Thanks, I do appreciate your input. 

[Amik]

@Tal22 - every single point you have made in your post is wrong. There is a fundamental misunderstanding of how Canvas Apps work.

I notice your community rank is "Helper IV" and this was surprising to me. I then had a look at your previous posts and noticed you've been posting similar questions for the past year, and then responding to other community members with the same complaint over and over again - usually along the lines of "Access/SQL/etc is great, Power Apps is limited".

I would suggest learning about Power Apps in general. Videos from Reza Dorrani, Shane Young and Lisa Crosbie provide very good fundamental learnings of the platform.

https://www.youtube.com/@ShanesCows 

https://www.youtube.com/@RezaDorrani 

https://www.youtube.com/@LisaCrosbie 

Until then, please be mindful that community users are taking their own free time to help other community users, and your posts are, respectfully, an unnecessary distraction when there are others who need genuine support.

[Tal22]

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. 

[Amik]

@Tal22 - I am not a gatekeeper on this Forum, you can post and rant as much as you need.

I just do not know what it is you hope to benefit from your posts professionally and mentally. I have seen talented super users respond to some of your questions with carefully thought out answers and your default response is to rant about the platform.

I have even seen a post where one extremely talented super user offer to call you for an hour to discuss your concerns for FREE! 

I wish you the best of luck with your career and I hope you get the outcomes you need, be it from the Power Platform or elsewhere.