You’re offline. This is a read only version of the page.
A while ago a customer came to use asking about the dataverse and whether it could be beneficial to invest in settting it up.
We did a small research into the dataverse and came to the conclusion our current Power BI solution was enough for their small scale data warehouse.
But it made us wonder, what are the use cases of the dataverse in large organisation who already has multiple SQL databases, azure and power BI solutions? Is it really just the online cloud based database or are we missing something?
And should we migrate the few dataflow we have in Power BI (Extraction dataflow > Transformation Dataflow > Dataset) to using the dataverse instead?
I agree with @AhmedSalih (btw, nice article reference). I was a hard-core SQL fan back when client-server apps were king, and even in the early days of web apps. But the benefits of building on the Dataverse foundation far outweighs the cost of building and maintaining a custom application on SQL. One thing the article did not really bring forward is that you could take an incremental approach to implementing solutions in the Dataverse by implementing an "on-prem" version (aka D365 Customer Engagement) where you have full access to the back-end SQL, but once you learn the depth of the stack and its capabilities, you will want to go for the full online implementation.
Good morning, @Easydash_Jelle, I have a very similar use case and the main reason that we decided to migrate to Dataverse was the need to build Model-Driven apps, Dataverse for Teams Apps, and AI models. All those require Dataverse as your data source. Also, note that Dataverse is way more than a Cloud Database. Check this article out:
#1
WarrenBelz
146,731
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
66,077
Most Valuable Professional
Share
Report
All responses (
Answers (