gfkrot.blogg.se - Microsoft dynamics 365 crm advantages and disadvantages

#Microsoft dynamics 365 crm advantages and disadvantages drivers#
#Microsoft dynamics 365 crm advantages and disadvantages update#

And it is possible to rollup “simple” calculated fields. it is possible to include rollup fields in calculated fields. (1:N only!) Filtering on the related table can be applied. The values on the parent are rolled up from child records.

#Microsoft dynamics 365 crm advantages and disadvantages update#

Like calculated fields they are read-only, they are calculated (re-calculated) based on a update schedule or on demand. They can be based on fields within the table or its parent. The Dataverse provides us with options to create calculated or rollup fields.Ĭalculated fields are populated on the retrieve of records. (Although you could consider some control by limiting which entities are available to users in your model-driven app!) (Including your custom activity.) Activities can be regarding any table that is enabled for activities, meaning a custom activity could be regarding “anything”. So if a user is given the ability to delete tasks, this would actually mean they can delete any activity type. But you need to be aware that security is applied consistently across all activities. The advantage of creating a custom activity is that they show in the timeline lists with other activities. But custom activities can be created as required.

Out of the box we have activities like phone call, email and task.

Localization – Multi-region, multi-lingual, multi-currency requirements.

Existing systems – are we going to connect with any existing systems or does any existing data need to be “squeezed” into the new data model.

Roadmap – what are the plans for the future?.

Self-service reporting – if the data model becomes complex can a “regular” user still extract the data for their reporting purposes? Or will all reports end up needing a data architect to design them?.

Retention policies – not all data can be stored indefinitely!.

Data location – some data must be stored in a given GEO.

User experience – it’s easy to forget that as we add normalization and relationships we create new constructs users need to navigate to be successful.

#Microsoft dynamics 365 crm advantages and disadvantages drivers#

There are many drivers which may influence data model decisions, including Supports accessing external sources to make their data available in apps. Connectors – great for leaving the data where it is.Azure Data Lake – ideal for data from other / multiple systems, read focused and can leverage the common data model.Structure typically based on the common data model. Dataverse – used for transaction data that apps will consume and maintain.The huge scale of the Data Lake may help support complex scenarios like machine learning, AI and complex reporting when extremely large data volumes maybe required. Azure Data Lake can store data from all disparate sources, including cloud and on-premise sources of any size and structure. The Data Lake can include CDM and can be integrated with Dataverse. Creating as connector that is then available by users for re-use is a great way to empower then to extend the solution using the Power Platform.ĭata modelling on the Power Platform should therefore look at the whole data architecture picture and include a logical look at data from the Dataverse, Data Lakes and external sources using connectors.Īzure Data Lake is a hyper-scale repository for big data analytics. Connectors can be packaged and deployed via solutions. The connectors can be make use of OAuth (including Azure AD), API key and basic auth. Or you may need to create a custom API and define your own actions. This might work by making use of an existing API. When an “off the shelf” connector does not exist a custom connector can be created. These connectors allow us to leverage existing data source and services.

Additionally custom connectors can be created as required. However Power Automate, Power BI and Power Apps (Canvas Apps) can leverage data connectors to access data from many hundreds of sources. Often a Dynamics 365 application will simply access data that resides in the Dataverse. I have tried to apply updates but a few “outdated” references may still exist! I created this blog post before the revised terms were announced. Meaning in the short term either term could be used. In terms of the exam I would expect them to begin using the term DataVerse at some point but that change is unlikely to be immediate. Therefore we should consider the terms like CDS and Dataverse as interchangeable. Note: Microsoft have recently updated some of their terminology. In this second post I will dive deeper into complex scenarios and discuss the more technical aspects of Dataverse (CDS) security. Or “MB 600” for short! As I prepare I plan to write revision notes in this post I will cover topics around designing the data and security models.ĭata is a big topic! I therefore plan to split this information into two post. I am currently preparing to take the Microsoft Dynamics 365 + Power Platform Solution Architect certification.