Dear,
I wonder if the CDS (in combination with PowerApps) can be used to accommodate a complex datamodel (as a replacement for let's say SQL server)?
For example a (relational) datamodel with 100+ tables, where some tables can have more than 100+ columns...
Or is it better to stick with a relational database and connect to that from within PowerApps instead of trying to create a lot of custom entities in CDS?
And what about non-relational (nosql, document, xml) datamodels?
Thanks,
Koen
Hi @KoenJanssensPD,
Agree with @DavidJennaway and to supplement on, CDS can support complex models, for instance, I’ve implemented a few of cases with over 400 entities/tables and over 1B records in total. There are some points to consider when working with those volumes and complexity like what David mentioned and also security contraints and performance considerations particularly around activities and activity pointers. Also when designing CDS data model there’s more to consider as opposed to SQL, most importantly UX, ensure the entities/data make sense to users and can easily navigate within the apps if you’re using model-driven apps.
Querying is not as obviously as flexible as SQL Server but CDS does offer rich APIs (rest and soap), SDK and also now in preview use SQL to query data: https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/cds-sql-query
hope this helps...
CDS can work well with fairly complex relational data models, though it's not as flexible as SQL Server. The areas where you're most likely to see limitations compared to SQL Server are:
You can store file content in CDS, but have no tools to help process the content. There is also nothing to help with storing XML