Nice sharing. May I share something here? I am the first 300 insider, in Jan 2016 for PowerApps (yes in one word, not like today, Power Apps, in two word). We used CDM for the first 2 years and then changed to CDS. It was a pain to me to migrate all data for client and until last two years it was finally settled down as Dataverse. Nonetheless, the core value remains unchanged.... To serve Power Apps (and now the overall Power Platform, including Power Automate fka Microsoft Flow and the Powerbi, a cloud based PivotTable). As a non programmer background and an insider since Jan 2016, I would say that Dataverse is mature now and you may let go SPL or Lists. Just use 100%, even without Automate you may build the whole ERP system like me within short period for your client. My advice 1. Change the way typical programmer does as back end and complicated the data structure. 2. Use your own thinking instead of follow to Microsodt concept like using Lookup (not flexible at all). 3. As I am in Asia, I only use 3 type of fields to avoid USA dateformat - Text (to be used for date as well and use Powerfx to convert to your region) - Number - File However, in fact I used Dataverse only to store images and some small data due to poor delegation. 99.9% of my data are using Custom Connector OpenAPI 2.0 I have a partner with me and also with Microsoft Programme Manager supporting us to build auto generation Custom Connector OpenAPI 2.0, where this is much better than Dataverse (though not to talk about security) due to the nature of NonSQL structure as our Custom Connector is accepted by Power Apps and based on MongoDB. So I hope my sharing can benefit many. Thanks.
Dani - great video! Thank you for producing and sharing!
Useful info thankyou Dani
Really love the design of your present
Did you make them yourself ? Was it via PPT ?
Yes mostly PPT :-)
Great Work
You need to include the Column type:LookUp
What Next???
Thanks for the input 👍.
guide me - looking for depth knowledge on Dataverse
Nice sharing.
May I share something here?
I am the first 300 insider, in Jan 2016 for PowerApps (yes in one word, not like today, Power Apps, in two word). We used CDM for the first 2 years and then changed to CDS. It was a pain to me to migrate all data for client and until last two years it was finally settled down as Dataverse.
Nonetheless, the core value remains unchanged.... To serve Power Apps (and now the overall Power Platform, including Power Automate fka Microsoft Flow and the Powerbi, a cloud based PivotTable).
As a non programmer background and an insider since Jan 2016, I would say that Dataverse is mature now and you may let go SPL or Lists.
Just use 100%, even without Automate you may build the whole ERP system like me within short period for your client.
My advice
1. Change the way typical programmer does as back end and complicated the data structure.
2. Use your own thinking instead of follow to Microsodt concept like using Lookup (not flexible at all).
3. As I am in Asia, I only use 3 type of fields to avoid USA dateformat
- Text (to be used for date as well and use Powerfx to convert to your region)
- Number
- File
However, in fact I used Dataverse only to store images and some small data due to poor delegation.
99.9% of my data are using Custom Connector OpenAPI 2.0
I have a partner with me and also with Microsoft Programme Manager supporting us to build auto generation Custom Connector OpenAPI 2.0, where this is much better than Dataverse (though not to talk about security) due to the nature of NonSQL structure as our Custom Connector is accepted by Power Apps and based on MongoDB.
So I hope my sharing can benefit many.
Thanks.