Dataverse Explained: Upscaling from Sharepoint

preview_player
Показать описание
Building Model Driven Apps that leverage SharePoint lists and libraries have limitations. Here are 5 key considerations when weighing Dataverse as a data repository for your business apps.

Check out these other videos we mentioned:

If you’re interested in details on delegation limits, I’ve got some links for you below.

Also including some links here to some content to help you with ALM

Here’s a link to help you get started with SharePoint Integration...

If you found this video helpful, subscribe to always be in the know of O365. This whole channel is focused on creating content around the Microsoft space. We create videos on Sharepoint, Power Platforms, Planner, Outlook, and other M365 tools. Technology should be an enabler, not a barrier, to productivity and happiness at work. Our mission is to empower your workforce through technology.

Other Free Resources + Guides 👇

👋 See you on the next video!
0:00 Are you a Citizen Developer, Office Developer or Tech Leader?
0:50 Reason One - Changes Everything
1:56 Reason Two - Questions to ask
3:13 On Dataverse Liscensing Costs
3:50 Reason Three - Delegation Limits
6:28 Reason Four - Application Lifecycle Management
9:00 Code Reviews, App QA team, Planned Outages
9:50 Reason Five - Detailed Permissions
12:04 *NEW* The Workplace
12:30 Encouragements and Personal Story

#modeldrivenapps #sharepoint #sharepointonline #dataverse #microsoft365 #powerapp #powerautomate #m365 #citizendeveloper #alm #applicationlifecyclemanagement
Рекомендации по теме
Комментарии
Автор

Dataverse can feel intimidating! What encouragement do you have or what is holding you back?

BulbDigital
Автор

The first point in this video really hits home for me, it's so nice once you get over all the initial hurdles of getting used to Dataverse. What really kicked things off for me was the "Dataverse for Teams" option, which is free as long as you run the applications inside of teams and can live with the limitations.

qaazz
Автор

Probably the biggest difficulty in changing to dataverse is the conversion process from Sharepoint. If Powerapps could handle the mapping, not just of all the Sharepoint Lists, but also updated the Canvas app code, then that would be great. I do think Dataverse has a lot of potential, but will wait for more improvements to the conversion process. It has come a long way since I looked it 5 years ago, and hopefully we will be on the Dataverse boat soon!
The other major issue is that we deal with Documents, and Dataverse cost in dealing with documents is cost prohibitive. This also needs to be sorted out.
Bottom Line: If Microsoft wants users to switch to Dataverse from Sharepoint, then the obligation is on them to make it so that it would be silly not to.

Bekesam
Автор

This video is remarkable! Wow! He is so well-spoken and clear. Thanks!

joel.engelhardt
Автор

It would be helpful to see a detailed price breakdown with a realistic scenario. Yes using Sharepoint is really time consuming and inefficient compared to Dataverse. You can do poor mans ALM with Sharepoint. You can do poor mans security with Sharepoint. You can do a relational database with Sharepoint. Managers with control of the purse often don't really care if life is hard for a highly paid dev. What would help is a realistic scenario showing real number cost savings due to using Dataverse, or a project that is truly impossible in SharePoint but possible in Dataverse.

closedchill
Автор

Can you point to some documentation or examples where it shows that the Power Apps is aware of the relationships when using Dataverse as the Datasource?

navarrocloud
Автор

Does dataverse not have a 5000/2000 row limit within powerapps as well?

Ploplox
Автор

One big issue I have with moving away from SharePoint is version history. Being able to quickly check who and when changes were made and roll back to a previous version is extremely key in my organization. Any way to move over to dataverse and still have this?

EdirinImiruaye
Автор

You make a good case for why Dataverse makes sense as a backend over cludged sharepoint lists. But what undermines this sensible story is powerapps - there are very few who understand it in deeply enough to get the benefit. Can dataverse be used with React as the front end?

nevilleattkins
Автор

Do you have any videos on dataverse management and upkeep?

alexk
Автор

I like the concept of Dataverse, but I can do so much more with SQL Server. Is there a way to create views with Dataverse like you can with SQL Server? We have on prem sql server and the gateway is as slow as molasses on winter day. But dataverse seems like a little more complex SharePoint and I truly hate SharePoint as a datasource.

tonya
Автор

Dataverse isn't very viable when you are building apps for company wide (400-800 staff) use, since every user that uses that app has to have a power apps premium license ($20/user/mo)

ZombieEtiquette
Автор

Unfortunately no logarithm functions are supported in Dataverse

ENG.Kelvinffxgchfhg
Автор

moving table in 18 min? couldnt you do it in 2?

FenixFenix-pp
Автор

Managed to convince a multi billion dollar company to FINALLY invest in the licenses - can finally move out of Sharepoint 🎉

Plainace
Автор

Mathematical functions have a long way to go. Excel is better in calculation by far

ENG.Kelvinffxgchfhg