Jed BrownGuest
For a lot of workflows, the data is already there, whether it's in Dataverse, SharePoint list, SQL Server, or longstanding line of business systems.

The challenge has always been turning that data into something that people can easily interact with.

You bring the data, and it builds the app structure for you, screens, navigation, relationships included.

I'm in the Power Apps maker portal at make.powerapps.com, and I want to build a model-driven app for our human resources team.

They've been tracking open roles and candidates in a spreadsheet for far too long, and that data is already imported into Dataverse.

Now I can set up new data, and I already have a Dataverse table for candidates, so I'll search for that.

This data can be from SharePoint lists, Dataverse, Excel, SQL databases, or you can even upload a CSV file as a data source.

In just a second, it inspects the schema, and it generates a fully working model-driven app.

I can see all of my candidate data, their roles, profile completion percentage, current status, days on current stage, and more based on the underlying table.

I automatically get a top navigation bar for each page, as well as forms for adding and editing records.

This looks good, and to make it a working app, I can just save and publish, and then I'll open the app full screen.

And you'll see that I can drill into each candidate and view their details, and this is the same view you get if you were to add new candidates as well.

For a lot of workflows, the data is already there, whether it's in Dataverse, SharePoint list, SQL Server, or longstanding line of business systems.

The challenge has always been turning that data into something that people can easily interact with.

You bring the data, and it builds the app structure for you, screens, navigation, relationships included.

I'm in the Power Apps maker portal at make.powerapps.com, and I want to build a model-driven app for our human resources team.

They've been tracking open roles and candidates in a spreadsheet for far too long, and that data is already imported into Dataverse.

Now I can set up new data, and I already have a Dataverse table for candidates, so I'll search for that.

This data can be from SharePoint lists, Dataverse, Excel, SQL databases, or you can even upload a CSV file as a data source.

In just a second, it inspects the schema, and it generates a fully working model-driven app.

I can see all of my candidate data, their roles, profile completion percentage, current status, days on current stage, and more based on the underlying table.

I automatically get a top navigation bar for each page, as well as forms for adding and editing records.

This looks good, and to make it a working app, I can just save and publish, and then I'll open the app full screen.

And you'll see that I can drill into each candidate and view their details, and this is the same view you get if you were to add new candidates as well.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.