Top request by customers: scanning business cards and capturing the information will be available in the upcoming Dynamics 365 release and is now available in instances with early access enabled. It worked remarkably well except for my own business card ...
The functionality seems to be provided by the new "AI Builder Business Card control" which is added on the quick create contact form. Next on the todo list - testing out modifying the mappings.
Monday, August 19, 2019
Saturday, August 17, 2019
D365 CE 2019 Wave 2 Preview: enable contextual email communication
One of the upcoming enhancements that a lot of my colleagues were excited about is Contextual email communication in Dynamics 365 for Sales & Customer Service. Contextual email communication allows you to overlay an email composition screen on top of the existing Dynamics 365 forms without having to navigate away from the screen that you are on. After you have enabled your environment for early preview access you can go to App Settings > Enhanced email to enable this new functionality. (You might need to do a hard refresh after enabling use CTRL-F5)
After you enable this feature, adding an e-mail to the timeline will open the composition overlay allowing you to consult information on the contact while creating your e-mail.
After you enable this feature, adding an e-mail to the timeline will open the composition overlay allowing you to consult information on the contact while creating your e-mail.
Labels:
CRM,
d365fall2019,
Dynamics 365,
Dynamics CRM,
msdyn365,
msdyncrm
Thursday, August 15, 2019
Early opt-in to Dynamics 365 CE release wave 2
You can now enable the features coming in the 2019 release wave 2 update by opting in to the updates in the Power Platform Admin Center. Opting in will enable all changed user experience updates for Dynamics 365 for Customer Engagement.
Don't do this on your production environment but test it out on a copy of production - once enabled you can not turn this off
From October 2019, all environments will be enabled for 2019 release wave 2. Opting in now, allows you to get hands on experience with wave 2 changes and testing out the impact on your specific solution setup.
Don't do this on your production environment but test it out on a copy of production - once enabled you can not turn this off
From October 2019, all environments will be enabled for 2019 release wave 2. Opting in now, allows you to get hands on experience with wave 2 changes and testing out the impact on your specific solution setup.
- Details Early opt in to 2019 release wave 2 - https://docs.microsoft.com/en-us/power-platform/admin/preview-october-2019-updates
- Dynamics 365 release schedule and early access – key dates for 2019 release wave 2 - https://docs.microsoft.com/en-us/dynamics365/get-started/release-schedule
- Overview of Dynamics 365 for Sales 2019 release wave 2 scenarios - https://docs.microsoft.com/en-us/dynamics365-release-plan/2019wave2/dynamics365-sales/
Labels:
CRM,
d365fall2019,
Dynamics 365,
Dynamics CRM,
microsoft,
msdyn365,
Power Platform
Tuesday, August 13, 2019
Dynamics 365 monthly reading list July 2019
Technical topics (Configuration, customization and extensibility)
- Announcing the general availability of embedded canvas apps in model driven forms
- Automatically validate your solutions using the PowerApps solution checker PowerShell Module
- Preview instant Flow steps in business process flows
- Use of React and Office UI Fabric React in the PowerApps Component framework is now available in public preview
- Comparing the three main ways to get Dynamics 365 data into Power BI
- Source code for Google Address Autocomplete PCF control
- How to trigger a Microsoft Flow from a custom button in Dynamics 365
- Using Admin PowerShell cmdlets with Power Platform
- Preview: Integration between Finance and Operations and Common Data Service – Phase 1
- Dynamics 365: Notification error message – “You are using apps designed for the legacy web client”
- Dynamics 365 FastTrack Techtalks – FastTrack TechTalks provide technical and functional best practices and guidance for Dynamics 365 deployments
- How to user Solution Layers in Dynamics 365 v9.x
- Service Update 72 for Microsoft Dynamics 365 9.1.0
- Unified Interface Community
- Increase productivity of CRM users by using Dynamics 365 Virtual Agents
- Remove “The email below might contain script …” warning in Dynamics 365 by modifying orgdbsettings
Topics for Dynamics 365 Business Application Platform analysts, project managers and power users
- Introducing the PowerApps Center of Excellence Starter Kit
- Does staffing the Microsoft Power Platform practice need a refresh?
- PowerApps Portals Licensing October 2019
- Top 10 anti-patterns in sprints, daily scrums, sprint planning, review and retrospectives
- Power Platform and growth mindset of learning – part 1 and Power Platform and growth mindset of learning – part 2
- Satya Nadella demos Microsoft Dynamics 365 Customer Insights (Youtube 00:05:25)
- Building an SFD in Dynamics 365 and the Power Platform
- Make a great first impression with your virtual agent
- Unilever’s digital journey leads to real results for consumers and employees
Labels:
CRM,
Customer Engagement,
Dynamics 365,
Dynamics CRM,
microsoft,
msdyn365,
Power Platform,
PowerApps
Thursday, August 01, 2019
Azure Databricks training material on Microsoft Learn
Still on my todo list – reviewing the 15 modules on Azure Databricks and the learning paths for data engineering with Databricks.
Modules : https://docs.microsoft.com/en-us/learn/browse/?products=azure-databricks
Learning Path : https://docs.microsoft.com/en-us/learn/browse/?products=azure-databricks&resource_type=learning%20path
Modules : https://docs.microsoft.com/en-us/learn/browse/?products=azure-databricks
Learning Path : https://docs.microsoft.com/en-us/learn/browse/?products=azure-databricks&resource_type=learning%20path
Labels:
azure,
BigData,
Data+engineering,
Databricks,
microsoft,
Spark
Code tip: Nullable datetime in C#
Nullable types are used when you need to represent the value of an underlying type. By default DateTime is not nullable in C# because it is a Value type, but using the Nullable construct (or the ? shorthand), you can assign the null literal to the DateTime type. Syntax is below:
DateTime? dt = null;
Nullable<DateTime> dt = null;
Labels:
C#,
development,
microsoft,
programming
Wednesday, June 19, 2019
Dynamics 365 monthly reading list May 2019
Technical topics (Configuration, customization and extensibility)
Topics for Dynamics 365 Business Application Platform analysts, project managers and power users
- Subscribe to AD changes using Microsoft Flow and Graph API
- Sprinkle some DevOps on your PowerApps & Dynamics 365 Customer Engagement projects – BRK3093 (Youtube 00:53:22)
- Build 2019: new accelerators bring Dynamics 365 and Power Platform ISVs to AppSource and Azure Marketplace
- Understand record references and polymorphic lookups in canvas apps
- Dynamics 365 Sales Insights – how relationship analytics values are calculated
- Building the platform for every developer
- Import or export records from PowerApps for Dynamics 365 CE
- Dynamic country maps in PowerApps
- Microsoft Dynamics 365 Banking accelerator is now in private preview
- Why would you use “Stage for upgrade” with managed solutions?
- On the Fasttrack to a Dynamics 365 for Customer Engagement on premise to online migration
- ALM at scale: new features and automation capabilities
- Announcing the general availability of the new view designer
- Dynamics 365 integration with Microsoft Flow
- Unearthing the “solution layering” feature of Dynamics 365. How are good old concepts of patching and cloning related to it?
- Flow vs Azure Logic Apps why am I a convert?
- Provisioning and administration of CDS instances is getting easier
- Geocode a custom entity with Microsoft Flow
- Using Azure Active Directory groups to manage user access to Dynamics 365 apps and data
Topics for Dynamics 365 Business Application Platform analysts, project managers and power users
- Power Platform and the definition of done … or why SOWs are fundamentally broken
- Common Data Service – Strategies and silos
- PowerApps – Why spreadsheets suck
- Are you brave enough to ask your customers how you are doing?
- Dynamics 365 & Power Platform timeline for the 2019 release wave 2
- Steve has a chat with Jeff York – interesting podcast where Steve Mordue interviews Jeff York (CFO – Microsoft Business Applications)
- Dynamics 365 Virtual Agent for Customer Service is available for preview
- The future of Dynamics 365 for Project Service Automation (PSA) also check out A letter to our Microsoft Project community
- Microsoft Dynamics 365 Marketing Insights Podcast – Know what your consumers say, seek and feel
Labels:
CRM,
Customer Engagement,
Dynamics 365,
Dynamics CRM,
Flow,
microsoft,
Power Platform,
PowerApps
Wednesday, June 05, 2019
PowerApps Component Framework available in public preview
On April 23th the PowerApps Component Framework (PCF) and the PowerApps CLI was finally made available for public preview. The PowerApps Component Framework (PCF) is the foundation for all controls used in the new Unified Interface released with Dynamics 365.
PCF allows 3d party developers to build visual components using the same framework which is used internally by Microsoft (see picture below for some examples) in the unified interface.
Components created using the PowerApps Control Framework are solution aware and can be used to build a more compelling user experience. The Dynamics365 developer community immediately picked up on this exciting news and Andrew Ly already shared the source code for 3 different controls - Progressbar control , keybinding example and countdowntimer.
Guido Preite @crmanswers also set up PCF Gallery which contains a list of different controls like a timeline control, data card and UK postcode validator. Everyday new controls based on PCF are added.
The PowerApps Component Framework has been in private preview for quite a while but some details were already shared on a number of occasions in 2018. Initially the framework was called Custom Controls Framework and I you encourage to take a look at some interesting post from Bob Guidinger on this topic (see references below). Do keep in mind that there are some changes between the private preview and public preview – see Update existing custom components for more details.
You will notice from the documentation that most samples are using Typescript to implement custom components so I added also some other reference links below which might help you to get started. For a brief introduction you might also want to take a look at the PowerApps April community call recording (PCF presented from 00:47:00 onwards). One thing to note though is that this is a framework which is clearly targeted at professional developers so the Dynamics consultant who occasionally writes some Javascript web resources or some simple plugins in C# will face a steep learning curve. I even think that pure Javascript/.NET developers even have an edge on the average Dynamics consultant when trying to learn the necessary skills required for PCF development.
References:
PCF allows 3d party developers to build visual components using the same framework which is used internally by Microsoft (see picture below for some examples) in the unified interface.
Components created using the PowerApps Control Framework are solution aware and can be used to build a more compelling user experience. The Dynamics365 developer community immediately picked up on this exciting news and Andrew Ly already shared the source code for 3 different controls - Progressbar control , keybinding example and countdowntimer.
Guido Preite @crmanswers also set up PCF Gallery which contains a list of different controls like a timeline control, data card and UK postcode validator. Everyday new controls based on PCF are added.
The PowerApps Component Framework has been in private preview for quite a while but some details were already shared on a number of occasions in 2018. Initially the framework was called Custom Controls Framework and I you encourage to take a look at some interesting post from Bob Guidinger on this topic (see references below). Do keep in mind that there are some changes between the private preview and public preview – see Update existing custom components for more details.
You will notice from the documentation that most samples are using Typescript to implement custom components so I added also some other reference links below which might help you to get started. For a brief introduction you might also want to take a look at the PowerApps April community call recording (PCF presented from 00:47:00 onwards). One thing to note though is that this is a framework which is clearly targeted at professional developers so the Dynamics consultant who occasionally writes some Javascript web resources or some simple plugins in C# will face a steep learning curve. I even think that pure Javascript/.NET developers even have an edge on the average Dynamics consultant when trying to learn the necessary skills required for PCF development.
References:
- What is the Custom Control Framework and why should Dynamics 365 developers be excited about it
- Custom Controls Framework – Introduction by Bob Guidinger
- Custom Controls Framework – Miscellaneous (Part 7) by Bob Guidinger
- PowerApps component framework (Microsoft documentation)
- Getting started with the PowerApps Component Framework (Youtube webinar 00:58:30) – webinar with the PowerApps development team
- Credit card Validator PCF Control with Hands On Lab and demo code
- Typescript SDK for Visual Studio 2017
- Typescript in 5 minutes
- Getting started with Typescript in 2019
- How to create a PowerApps PCF control (Youtube 00:13:05) by Todd Baginski
- Develop your custom control using PowerApps Component framework and use it on your CRM interface
- PowerApps Component Framework – frosting on the cake
- Microsoft PowerApps CLI – time for the non-citizen developers to get more involved
- Create custom controls using the PowerApp Component Framework
Labels:
CRM,
development,
Dynamics 365,
Dynamics CRM,
microsoft,
msdyn365,
msdyncrm,
PCF,
PowerApps,
Typescript
Tuesday, May 21, 2019
General availability of PowerApps Solution checker makes it easier to check Dynamics 365 solution quality
On May 2th Microsoft announced the general availability of the PowerApps Solution Checker, tooling which allows you to run a static code analysis of your CDS and Dynamics 365 solutions against a set of best practice rules. By running these checks, you can identify problematic patterns in your code base which might impact performance or maintainability/upgradeability of your code.
Tooling like this is a must have for Dynamics 365 CE Online where releases are delivered on a continuous basis (with bi-weekly releases). With this release schedule, the risk of low quality solutions (from ISVs or SIs) interfering with Microsoft updates becomes more probable.
But this is not only about Microsoft safeguarding their Dynamics 365 SAAS platform but also about delivering value quicker and in a reliable fashion. I truly believe that code quality is a good indicator about how quickly developers can add business value to a software system. Static code analysis tools such as PowerApps solution checker might not be the holy grail but they at least give you an indication of the amount of technical debt that you have amassed within your Dynamics 365 instances.
I have been using PowerApps solution checker since a couple of months now and for projects with lots of different teams working on solution it allows you to have some indication of code quality without having to delve through 10.000 lines of code. I also think that announcements such installing the solution checker by default, introduction of the Solution Health Hub and the announcement of PowerShell script support coming soon are showing Microsoft’s commitment on finally delivering on a good DevOps story for Dynamics 365.
References:
Tooling like this is a must have for Dynamics 365 CE Online where releases are delivered on a continuous basis (with bi-weekly releases). With this release schedule, the risk of low quality solutions (from ISVs or SIs) interfering with Microsoft updates becomes more probable.
But this is not only about Microsoft safeguarding their Dynamics 365 SAAS platform but also about delivering value quicker and in a reliable fashion. I truly believe that code quality is a good indicator about how quickly developers can add business value to a software system. Static code analysis tools such as PowerApps solution checker might not be the holy grail but they at least give you an indication of the amount of technical debt that you have amassed within your Dynamics 365 instances.
I have been using PowerApps solution checker since a couple of months now and for projects with lots of different teams working on solution it allows you to have some indication of code quality without having to delve through 10.000 lines of code. I also think that announcements such installing the solution checker by default, introduction of the Solution Health Hub and the announcement of PowerShell script support coming soon are showing Microsoft’s commitment on finally delivering on a good DevOps story for Dynamics 365.
References:
Labels:
CRM,
Dynamics 365,
Dynamics CRM,
microsoft,
Power Platform,
PowerApps
Monday, May 13, 2019
Dynamics 365 monthly reading list April 2019
Technical topics (Configuration, customization and extensibility)
Topics for Dynamics 365 Business Application Platform analysts, project managers and power users
- Integrating Dynamics 365 with Azure Function using Managed Identity
- Create Model Driven Apps for CDS environments
- PowerApps sample – visualization of beautiful mathematics
- Using the new Top and Bottom operators in views and fetchxml – part of the April 2019 release
- Working offline with PowerApps
- Understanding data loss prevention policies in Power Platform admin center
- Activating Field Service Mobile app licenses
- Dynamics 365 & Azure DevOps – Unit testing
- Does enterprise scale Dynamics 365 require multiple instances?
- Solution history entity in Dynamics 365 CRM
- PowerApps solution designer vs classic solution designer
- Power Platform & Azure enable developers to build applications faster than ever
- View solution layers (docs.microsoft.com)
- Dynamics 365 CE – set classic UI and navigate to classic UI
- Mobile offline for Dynamics 365 CE apps available in public preview
- Updates for the basic list and campaign management capabilities for Dynamics 365 applications (Mar-May 2019 release)
- Use Flow to monitor multiple Dynamics 365 instances
- PowerShell scripts to discover and manage specific features in the Power Platform
- Tricky application ids in Dynamics 365 apps
- Using a service principal with the CDS connector
- Demystifying PowerApps environments – Part 1 – default instance
- Demystifying PowerApps environments – Part 3 – production environments
Topics for Dynamics 365 Business Application Platform analysts, project managers and power users
- Microsoft, Adobe CEOs detail latest data sharing efforts and here the official announcement Adobe, Microsoft and SAP announce new Open Data Initiative details
- Microsoft product priorities that will shape Dynamics 365 partner efforts
- Power Platform – the Uncommon Data Service
- Dynamics 365 – Dead is a strong word
- Business Applications ISV news at Build 2019
- You don’t have to be a developer to turn a great idea into an app
- Microsoft steps up to Salesforce’s AppExchange
- Has Microsoft just introduced a 20% tax on Dynamics 365 ISVs?
- Upcoming program for Business Applications ISVs
- Use playbooks for guided selling in Dynamics 365
- Project accurate revenue with sales forecasting in Dynamics 365 CE (Preview)
Labels:
Adobe,
CRM,
Customer Engagement,
Dynamics 365,
Dynamics CRM,
Flow,
microsoft,
Power Platform,
PowerApps
Sunday, May 12, 2019
Quick tip: solving rendering issues in PowerPoint presenter mode
After upgrading to a newer version of Office, my PowerPoint slides displayed incorrectly in presenter mode – see screenshot below. I googled around but did not find anything useful.
Fortunately I remembered a similar issue that I had in Internet Explorer 11 see Solve image rendering problems in Internet Explorer 11 on HP ZBooks. It seems that PowerPoint has a similar setting – go to Options>Advanced and underneath the Display section I had to check the “Disable Slide Show hardware graphics acceleration."
Fortunately I remembered a similar issue that I had in Internet Explorer 11 see Solve image rendering problems in Internet Explorer 11 on HP ZBooks. It seems that PowerPoint has a similar setting – go to Options>Advanced and underneath the Display section I had to check the “Disable Slide Show hardware graphics acceleration."
Labels:
fix,
microsoft,
Office,
PowerPoint,
troubleshooting
Monday, March 25, 2019
Dynamics 365 monthly reading list March 2019
Technical topics (Configuration, customization and extensibility)
Topics for Dynamics 365 CE business analysts, project managers and power users
- Getting model-driven app record id in the embedded canvas app
- How to spot negative comments in NPS surveys
- Increase sales with Dynamics 365 AI for Sales
- Guidelines on working with embedded canvas apps
- Dynamics 365 UXI app icons blueprint
- Keeping Dynamics 365 Apps up to date – very interesting read with background info on how Microsoft releases new functionality by @jukkan
- Microsoft Dynamics 365 (online) – Asynchronous Service Quotas
- Dynamics 365 AI for Customer Service Team Blog
- Power BI URL Query in Dynamics 365 for Customer Engagement (CE)
- Monitoring Dynamics 365 front to backend activities with Azure Application Insights
- Solving login issues with Dynamics 365 mobile app on iOS
- Alexa, ask Microsoft Flow to read out my latest e-mail
- Lightweight geospatial in Dynamics 365 for phones
- Autonumber fields are now supported by the modern entity designer
- PowerApps components patterns
- Avoid model driven failure – short checklist to use when a user can’t see an app or certain parts of an app
- Camera capabilities or how to add a photo id capturing to a contact screen in Dynamics
- Replacing a Dynamics 365 dialog with an embedded canvas PowerApp
- Embed Power BI Visuals in Dynamics 365 – with Secure Embed
- Send Action card from Dynamics 365 CE as Actionable Message via Email
Topics for Dynamics 365 CE business analysts, project managers and power users
- I wish there was no scrum master in my Dynamics CRM team
- Customer Success Executives Need to Answer These 3 Critical Questions
- Microsoft quietly sets new data storage pricing for PowerApps, Dynamics 365 Customer Engagement
- Out-of-the-box LinkedIn profiles and simplified Sales Navigator installation
- The future of Microsoft Dynamics 365 projects
- Forrester names Microsoft PowerApps a leader in low-code development platforms
- The Microsoft Power Platform – Empowering millions of people to achieve more
Tuesday, March 19, 2019
Dynamics 365 certifications and course material update March 2019
Warning: I will update this blog post on a regular basis as new material becomes available or changes on certification are made by Microsoft
Updated March 31th: Added information on new roles (field service functional consultant and marketing functional consultant) and exams
For consultants wanting to certify on Dynamics 365, quite a few changes have been announced the last couple of months. In December 2018, Microsoft announced that they were retiring a whole set of Dynamics 365 exams (see Exam and Certification Retirement Roundup, December 2018). Microsoft stated that many of the upcoming changes are part of the evolution to focus more on role-based certifications – for Dynamics 365 CE there are following roles defined but some content is not there yet (these roles were announced on Introducing New Certifications for Microsoft Dynamics 365 Customer Engagement Functional Consultants )
A new exam which has been introduced is Exam MB-900 Microsoft Dynamics 365: Fundamentals
References:
Updated March 31th: Added information on new roles (field service functional consultant and marketing functional consultant) and exams
For consultants wanting to certify on Dynamics 365, quite a few changes have been announced the last couple of months. In December 2018, Microsoft announced that they were retiring a whole set of Dynamics 365 exams (see Exam and Certification Retirement Roundup, December 2018). Microsoft stated that many of the upcoming changes are part of the evolution to focus more on role-based certifications – for Dynamics 365 CE there are following roles defined but some content is not there yet (these roles were announced on Introducing New Certifications for Microsoft Dynamics 365 Customer Engagement Functional Consultants )
- Dynamics 365 for Sales Functional Consultant Associate
- Dynamics 365 for Customer Service Consultant Associate
- Dynamics 365 for Field Service Functional Consultant Associate
- Dynamics 365 for Marketing Functional Consultant Associate
| Exam Number | Exam Name | Retirement Date | Replace Exam | Course material |
| MB2-715 | Microsoft Dynamics 365 customer engagement Online Deployment | June 30, 2019 | MB2-200 | Dynamics 365: Power Platform applications (8 hrs) Dynamics 365: Power Platform automation (8 hrs) Dynamics 365: Power Platform integrations (8 hrs) Dynamics 365: Power Platform test and deploy (8 hrs) Dynamics 365 core exam study guide created by @JonasWauters1 Revision guide for MB2-200 |
| MB2-717 | Microsoft Dynamics 365 for Sales | June 30, 2019 | MB-210 | Dynamics 365 for customer engagement for sales (8hrs) Dynamics 365 for sales exam study guide created by @JonasWauters1 |
| MB2-877 | Microsoft Dynamics 365 for Field Service | June 30, 2019 | MB2-240 (Beta – published March 31th) | |
| MB2-718 | Microsoft Dynamics 365 for Customer Service | August 31, 2019 | MB2-230 (Beta) | Dynamics 365 for customer engagement for customer service (8 hrs) Dynamics 365 for customer service exam study guide created by @JonasWauters1 Study guide for MB230 by @BenHosk |
| MB2-719 | Microsoft Dynamics 365 for Marketing | August 31, 2019 | MB-220 (Beta – published March 31th) |
A new exam which has been introduced is Exam MB-900 Microsoft Dynamics 365: Fundamentals
References:
Labels:
certification,
Dynamics 365,
Flow,
microsoft,
msdyn365,
Power Platform,
PowerApps
Friday, February 22, 2019
Making sense of XRM, PowerApps and some other acronyms (CDS, CDM, …)
With the July 2018 update of Dynamics 365 (9.0), Microsoft released an interesting architecture update to Dynamics 365 Customer Engagement where they separated the “core” features of the platform and the various business modules (Sales, Customer Service, Marketing, Field Service, etc…). This separation of the “core” platform features allows not only Microsoft Business Applications to leverage the platform capability but also third party providers and ISVs.
The term XRM was used in the past to describe the ability to built business applications with minimal development effort (relying on configuration and customization) on top of the Dynamics CRM platform. These applications allowed you to model business entities and their relationships (xRM or any Relationship Management) and keep track of this information in a database without having to develop everything yourself. With the platform separation, we can now finally think about XRM and CDS in the same way (check out Yes, XRM is the new Common Data Service (2.0) by @Jukkan for more information).
From a solution architecture perspective we can see a number of main building blocks in the schema above:
I had a number of interesting conversations with Microsoft about the Microsoft Power Platform when attending the Microsoft Fasttrack bootcamp for solution architect in January 2019 which convinced me that this is not something that you can dismiss as a Microsoft Dynamics partner. The future toolkit for customization and extending Dynamics 365 CE will be PowerApps and Flow. But it seems that non-Dynamics partners are amongst the first movers to take a large part of this new market opportunity. As a Dynamics 365 partner (or consultant) take a look at Why Microsofts Power Platform is one of its biggest bets for 2019 which explains where Microsoft is moving to and how they plan to leverage the data captured in the Power Platform/CDS to provide more actionable insight - see https://aka.ms/allaboutbase
Background information:
The term XRM was used in the past to describe the ability to built business applications with minimal development effort (relying on configuration and customization) on top of the Dynamics CRM platform. These applications allowed you to model business entities and their relationships (xRM or any Relationship Management) and keep track of this information in a database without having to develop everything yourself. With the platform separation, we can now finally think about XRM and CDS in the same way (check out Yes, XRM is the new Common Data Service (2.0) by @Jukkan for more information).
From a solution architecture perspective we can see a number of main building blocks in the schema above:
- Common Data Service (CDS)
- Common Data Model (CDM) - is a standardized, modular, extensible collection of data schemas published by Microsoft that are designed to make it easier for you to build, use, and analyze data. All entities (and fields) used by Microsoft Dynamics 365 applications are described in the CDM schema. For more info see https://docs.microsoft.com/en-us/common-data-model/ as well as https://github.com/Microsoft/CDM. Actually check out the Common Data Model Poster (A3 format) for a high level view of the different entities. Other vendors such as Adobe and SAP will also start levering the CDM as part of the Open Data Initiative - https://www.microsoft.com/en-us/open-data-initiative
- Common Data Service for Apps framework - https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/data-platform-intro which plugs in to the CDM model (and associated storage) but also provides standard framework functionality such as security (authentication/authorization), auditing as well as extensibility points (workflows, business rules and other extensibility points such as plugins) and an API and connector framework for these entities.
- Power Platform
- Power BI - interactive data visualization platform
- PowerApps – allows you to build canvas driven apps and model driven apps. Canvas driven apps are apps that you can build using a drag and drop design interface without requiring a developer - especially very productive to built mobile/tablet applications. Model driven apps also allow you built business applications without requiring a developer but unlike canvas apps you don’t have full control on the user interface but with additional functionality such as process support, full extensibility, etc … This was previously referred to as the xRM capability – sometimes also referred to as CDS for Apps. Initially PowerApps was a completely separate platform but with the Spring 2018 update Microsoft decided to merge the two different platforms. Read PowerApps Spring Update – if you want to get your heads around the new CDS for Apps and to understand how everything seems to finally come together. Definitely also subscribe to the PowerApp blog to keep up to date on the fast pace at which this platform is evolving. Microsoft is on a weekly release schedule for PowerApps which is also visible in the Released versions of Microsoft PowerApps
- Flow - an easy to use workflow and integration platform. A power-user can use this platform. Programming skills are not mandatory https://flow.microsoft.com/en-us/ . With over 250+ connectors and a huge number of templates, Microsoft Flow allows you to automate your daily work.
- Azure – Microsoft’s cloud platform powering all of the above. The Power Platform as well CDS for Apps also have built-in capabilities to integrate with a lot of Azure building blocks – an interesting read on this topic is https://powerapps.microsoft.com/en-us/blog/create-business-apps-using-powerapps-and-azure-functions/
I had a number of interesting conversations with Microsoft about the Microsoft Power Platform when attending the Microsoft Fasttrack bootcamp for solution architect in January 2019 which convinced me that this is not something that you can dismiss as a Microsoft Dynamics partner. The future toolkit for customization and extending Dynamics 365 CE will be PowerApps and Flow. But it seems that non-Dynamics partners are amongst the first movers to take a large part of this new market opportunity. As a Dynamics 365 partner (or consultant) take a look at Why Microsofts Power Platform is one of its biggest bets for 2019 which explains where Microsoft is moving to and how they plan to leverage the data captured in the Power Platform/CDS to provide more actionable insight - see https://aka.ms/allaboutbase
"The true value of Microsoft Business Applications platform is the ecosystem it resides in, the
AI signals (internal and external) that enrich it, and the overall
outcomes it creates for your business."
Background information:
- Microsoft takes off its xRM platform-as-service gloves
- Making sense of Microsoft’s Common Data Service makeover
- Common Data Service for Apps Developer Overview
- Accelerating digital transformation with the Spring 2018 release for Dynamics 365 and Business Application Platform
- xRM = CDS, building powerful business apps
- New features in the Common Data Service for Apps! (Spring update)
- Introducing model-driven apps – a new way to create
- Exploring CDS for Apps platform licensing
Labels:
CDS,
Dynamics 365,
Flow,
Power BI,
Power Platform,
PowerApps,
XRM
Wednesday, January 23, 2019
Check Dynamics 365 solution quality with the new PowerApps Solution Checker
End of November 2018, Microsoft quietly launched a preview of the Solution checker for Dynamics 365 as part of the Common Data Service for Apps platform update. The solution checker analyzes the different solution components for unmanaged solutions within your Dynamics 365 tenant. I accidently stumbled upon it when reading this interesting article from Steve Mordue – How about some solution quality?. The solution check will analyse the different artifacts or components within your solution like plugins and custom workflow activities, web resources as well as Dynamics 365 configuration such as SDK messaging steps.
The solution checker has been built based upon the experience and internal tooling of Microsoft Premier Field Engineers (definitely check check out the Dynamics 365 PFE blog Dynamics 365 Customer Engagement in the Field) and has been already used quite extensively at big customers in the past couple of weeks.
Solution checker currently only works for Dynamics 365 Online and is only accessible from within the https://web.powerapps.com user interface but I suspect that Microsoft will make this accessible using an API since it makes sense to integrate this check in your Dynamics 365 continuous build process.
Solution checker for Dynamics 365 is made available within https://web.powerapps.com and to install you can follow the steps as outlined in Make higher quality apps with solution checker. It is installed from within AppSource but can only be found in AppSource when starting from the PowerApps web portal. The solution checker will need to be installed per instance for which you want to check the solutions. Since it only checks unmanaged solutions - you will typically only install it on your development organization/instance.
It might take a couple of minutes before the PowerApps Checker solution is installed - on this page you will also see when it is completed successfully.
It is a good idea to run the solution checker on a regular interval as Microsoft is continuously expanding the code quality rule sets which are used.
The result of the solution check is a zip file which contains the result in CSV and Excel format. The excel will contain an overview page with a summary of the issues and a second sheet with details of the different issues.
For each issue you will have a detailed description of the issue explained using multiple fields. Some values in fields are only relevant to plugins/workflow assemblies whereas other apply to all types of artifacts/components.
Solutions which do not follow the guidance will cause lot of support issues down the line especially with Microsoft rolling out a steady stream of updates of the Dynamics 365 platform. So start using solution checker to make sure that you can concentrate on adding value with your Dynamics 365 solutions and apps.
The solution checker has been built based upon the experience and internal tooling of Microsoft Premier Field Engineers (definitely check check out the Dynamics 365 PFE blog Dynamics 365 Customer Engagement in the Field) and has been already used quite extensively at big customers in the past couple of weeks.
Solution checker currently only works for Dynamics 365 Online and is only accessible from within the https://web.powerapps.com user interface but I suspect that Microsoft will make this accessible using an API since it makes sense to integrate this check in your Dynamics 365 continuous build process.
Solution checker for Dynamics 365 is made available within https://web.powerapps.com and to install you can follow the steps as outlined in Make higher quality apps with solution checker. It is installed from within AppSource but can only be found in AppSource when starting from the PowerApps web portal. The solution checker will need to be installed per instance for which you want to check the solutions. Since it only checks unmanaged solutions - you will typically only install it on your development organization/instance.
It might take a couple of minutes before the PowerApps Checker solution is installed - on this page you will also see when it is completed successfully.
It is a good idea to run the solution checker on a regular interval as Microsoft is continuously expanding the code quality rule sets which are used.
The result of the solution check is a zip file which contains the result in CSV and Excel format. The excel will contain an overview page with a summary of the issues and a second sheet with details of the different issues.
For each issue you will have a detailed description of the issue explained using multiple fields. Some values in fields are only relevant to plugins/workflow assemblies whereas other apply to all types of artifacts/components.
| Report field | Examples | Description | Applies to |
| Issue | il-avoid-specialized-update-ops | The title of the issue identified in the solution – take a look at .. to see an overview of the different types of issues which are being checked |
All |
| Category | Performance, Maintainability, UpgradeReadiness, Supportability | Categorization of the issue identified | All |
| Severity | Low, medium, high,informational | Represents the potential impact of the issue identified. | All |
| Guidance | http://go.microsoft.com/fwlink/?LinkID=398563&error=meta-remove-inactive&client=PAChecker | Link to the guidance articles – most of them link to a section underneath the new Best practice and guidance for the Common Data Service Apps but some links point to older reference articles which still apply. Microsoft plans to consolidate all the guidance relevant for CDS in one location in the end but this is a work in progress |
All |
| Component | Configuration, plugin, webresource, … | The solution component where the issue was identified | All |
| Location | The location and/or source file of the component where the issue that was identified occurred, such as the assembly or JavaScript file name. | All | |
| Line# | ... | The line number reference of the issue in the impacted web resource component. | Web resource |
| Module | Module name where the issue identified in the assembly was detected. | Plug-in or custom workflow activity | |
| Type | Type of the issue identified in the assembly. | Plug-in or custom workflow activity | |
| Member | Member of the issue identified in the assembly. | Plug-in or custom workflow activity | |
| Statement | The code statement or configuration that resulted in the issue. | All |
Solutions which do not follow the guidance will cause lot of support issues down the line especially with Microsoft rolling out a steady stream of updates of the Dynamics 365 platform. So start using solution checker to make sure that you can concentrate on adding value with your Dynamics 365 solutions and apps.
Labels:
Dynamics 365,
Dynamics CRM,
microsoft,
msdyn365,
msdyncrm,
Power Platform,
PowerApps
Thursday, January 17, 2019
Microsoft cloud IT architecture resources available
Summary: Learn core cloud architecture concepts for Microsoft identity, security, networking, and hybrid. Review prescriptive recommendations for protecting files, identities, and devices when using Microsoft's cloud. Learn how to deploy a modern and secure desktop with Windows 10 and Office ProPlus.
These architecture tools and posters give you information about Microsoft cloud services, including Office 365, Windows 10, Azure Active Directory, Microsoft Intune, Microsoft Dynamics 365, and hybrid on-premises and cloud solutions. IT decision makers and architects can use these resources to determine the ideal solutions for their workloads and to make decisions about core infrastructure components such as identity and security.
https://docs.microsoft.com/en-us/office365/enterprise/microsoft-cloud-it-architecture-resources
These architecture tools and posters give you information about Microsoft cloud services, including Office 365, Windows 10, Azure Active Directory, Microsoft Intune, Microsoft Dynamics 365, and hybrid on-premises and cloud solutions. IT decision makers and architects can use these resources to determine the ideal solutions for their workloads and to make decisions about core infrastructure components such as identity and security.
https://docs.microsoft.com/en-us/office365/enterprise/microsoft-cloud-it-architecture-resources
Labels:
architecture,
azure,
Cloud,
Dynamics 365,
microsoft,
msdyn365,
Office365,
solution+architecture
Monday, January 14, 2019
Dynamics 365 monthly reading list December 2018
Technical topics (Configuration, customization and extensibility)
Topics for Dynamics 365 CE business analysts, project managers and power users
- Enrich your model-drive forms with embedded canvas apps (Public preview) – official announcement on the PowerApps blog (December 12th)
- Embedded canvas apps and passing a dynamic Dynamics 365 context which is similar to Embedding Canvas app on a model –driven app’s form (preview) – passing list of related records as context
- Updated tools to build and configure Dynamics 365 applications
- Power Apps Canvas App coding standards and guidelines
- Introducing the new WYSIWYG model driven form designer (Public Preview)
- Announcing: the Dynamics 365 for Marketing December 2018 update is now available
- Implementing Dynamics 365 using the Scrum Framework Technical Lead Perspective
- Previewing April 2019 release functionalities and updates for Dynamics 365 for Customer Engagement
- General availability: Dynamics 365 Channel Integration Framework – bring your own channel provider with ease
- PowerApps: Understanding what it is and why to use it?
- Enable and configure Relationship assistant
- Dynamics 365 Knowledge Article Versioning
- PowerApps: sending text/sms messages
- Creating custom icons in Dynamics 365 (Youtube video)
- Upgrading to Dynamics 365 v9 – the experience of @ramontebar with the upgrade
- Office 365 + Dynamics 365 + LinkedIn = Microsoft Dynamics 365 Relationship Analytics for sales demo (Youtube)
- Optimum batch size and thread while deleting records using SSIS integration toolkit for Dynamics 365
- QueryExpression and how to boost performance !
- Overview of Dynamics 365 AI for Market Insights (Youtube 00:25:04)
- Chrome browser best practices for Dynamics 365 Customer Engagement projects
- Dynamics 365 Tip: do not delete system components
- Dynamics 365 Server – version 9.0 download link
- Dynamics 365 v9.1 Enable Unified Interface UI updates on upgraded organizations
- Power Platform – Ryan’s Five things – feedback from Steve Mordue’s interview with Ryan Jones – Group Program Manager at Microsoft
- How to configure Dynamics 365 AI for sales in CRM?
- PowerApps and Microsoft Flow Governance and Deployment Whitepaper is now available
Topics for Dynamics 365 CE business analysts, project managers and power users
- The biggest Microsoft Dynamics stories of 2018
- Dynamics 365 and Power Platform product roadmap – after having disappeared a new version of the product roadmap has been made available to the public.
- Microsoft Business Applications – breaking down the landscape
- PowerApps quick overview mind map
- Dynamics 365 – when you should clear your browser cache and how
- Top 3 themes for Dynamics 365 in 2018
- The brand new org chart in Dynamics 365
- If Bob Paisley managed a CRM team
- Be prepared with the new playbooks in Dynamics 365 for Sales
- Playbooks for Dynamics 365 Activity Templates
Labels:
CRM,
Customer Engagement,
Dynamics 365,
Dynamics CRM,
microsoft,
PowerApps
Whitepaper– Artificial Intelligence in Belgium and Luxembourg: Outlook for 2019 and beyond
Microsoft recently commissioned a study with over 277 European companies on how companies currently manage their AI activities and how they see the challenges and opportunities ahead – 21 companies out of Belgium and Luxembourg have participated in this study amongst them Ageas, Afga Gevaert, Alpro, Arcelor Mittal, Katoe Natie, KBC Group, Proximus and Solvay – some interesting findings:
- Machine learning (81%), smart robotics (62%) and NLP (48%) are most useful for companies in Belgium and Luxembourg. Smart robotics ranks considerably higher than the European average (44%)
- Current use cases highlighted by executives include predictive maintenance, using demand forecasting to optimize supply chain operations and automation of logistics
- Advanced analytics is considered to be one of the most important capabilities (out of 8 capabilities) necessary for AI success in Belgium and Luxembourg
Labels:
advanced+analytics,
AI,
Artificial Intelligence,
microsoft
Thursday, January 10, 2019
Integrate Dynamics 365 for Customer Engagement apps with Microsoft Teams (Preview)
Warning: This preview is currently only fully available for organizations in the North American region.
Microsoft Teams is a chat-based collaborative tool, where people can work on documents, exchange information using chat – check out the what is Microsoft Teams video from the Microsoft teams video training series if you have not worked with it previously. One of the interesting capabilities of Microsoft teams is that it allows you to add new apps within your team workspace – these apps are available in the Teams store, and can be custom built by you for distribution through the store or directly to your users (also Take a look at 30 invaluable integrations that you should be using with Microsoft Teams for some great examples of apps that are available)
In November 2018 Microsoft added a “Dynamics 365” app to this ever growing list of apps – it currently provides 3 important capabilities:
Working with the Dynamics 365 bot in Teams
After you have installed the Dynamics 365 App from the Teams store (See Install and setup the Dynamics 365 App for Teams for more details) , you will be able to use the new sales bot functionality within the Conversations tab of the app
When you first open the bot you need to connect it to a specific Dynamics 365 organization instance – afterwards you are able change this setting.
For the moment the functionality is still rough on the edges basic but more functionality will probably be added throughout the preview. The bot allows you to lookup information in Dynamics 365 using natural language – e.g. you can search for an opportunity “Audio equipment” by just typing “search audio equipment” or “lookup audio equipment” or “find audio equipment” which will surface a card with information about that opportunity. Behind the scenes the bot will connect to the LUIS Azure Cognitive Services to understand the intent of your message to retrieve the most important information. Through the bot you will also be able to update basic information of this opportunity like the amount, close date, etc… This functionality is also available from within the Microsoft Teams mobile app
Working with Dynamics 365 records from within Microsoft Teams
You can now also add a new tab to the top of your channel which uses a specific app – if you link the Dynamics 365 app here you can connect it to a specific Dynamics 365 record.
Users who do not have a Dynamics 365 license or not a valid security role in Dynamics 365 will not be able to access the information but will receive a warning
Linking Microsoft Teams files to Dynamics 365 records
When you create a new Microsoft team behind the scenes a SharePoint Online site is being used, and each channel in a team gets a folder within the default team site document library (Read How SharePoint Online and OneDrive for Business interact with Microsoft Teams for more details and watch the video Foundations of Microsoft Teams to get an architectural overview) So basically the integration between Dynamics 365 and files in Teams is being built on top of the existing SharePoint integration for which the fundamentals already existed.
To be able to link Microsoft Teams files to Dynamics 365 records you will first need to activate preview functionality within your Dynamics 365 system settings (Settings>Administration>System settings)
Next a new button will appear in your mean which allow you to link to a specific team and channel.
The linked Teams documents will appear in the same place as linked SharePoint documents (under the cover they actually are stored in SharePoint - take a look at Showing SharePoint document properties in Dynamics CRM views for a more detailed explanation of how this is done).
For the official documentation on this preview see Preview: Integrate Dynamics 365 for Customer Engagement apps with Microsoft Teams
Microsoft Teams is a chat-based collaborative tool, where people can work on documents, exchange information using chat – check out the what is Microsoft Teams video from the Microsoft teams video training series if you have not worked with it previously. One of the interesting capabilities of Microsoft teams is that it allows you to add new apps within your team workspace – these apps are available in the Teams store, and can be custom built by you for distribution through the store or directly to your users (also Take a look at 30 invaluable integrations that you should be using with Microsoft Teams for some great examples of apps that are available)
In November 2018 Microsoft added a “Dynamics 365” app to this ever growing list of apps – it currently provides 3 important capabilities:
- Provide Dynamics 365 chat bot functionality in the team conversations
- Work with Dynamics 365 records directly from within Microsoft Teams. Teams now has the possibility to link an existing Dynamics 365 record so that users are able to both view and edit information about this Dynamics 365 within Microsoft teams and even navigate to related records without leaving Microsoft teams.
- Link Microsoft Teams files to Dynamics 365 records
Working with the Dynamics 365 bot in Teams
After you have installed the Dynamics 365 App from the Teams store (See Install and setup the Dynamics 365 App for Teams for more details) , you will be able to use the new sales bot functionality within the Conversations tab of the app
When you first open the bot you need to connect it to a specific Dynamics 365 organization instance – afterwards you are able change this setting.
For the moment the functionality is still rough on the edges basic but more functionality will probably be added throughout the preview. The bot allows you to lookup information in Dynamics 365 using natural language – e.g. you can search for an opportunity “Audio equipment” by just typing “search audio equipment” or “lookup audio equipment” or “find audio equipment” which will surface a card with information about that opportunity. Behind the scenes the bot will connect to the LUIS Azure Cognitive Services to understand the intent of your message to retrieve the most important information. Through the bot you will also be able to update basic information of this opportunity like the amount, close date, etc… This functionality is also available from within the Microsoft Teams mobile app
Working with Dynamics 365 records from within Microsoft Teams
You can now also add a new tab to the top of your channel which uses a specific app – if you link the Dynamics 365 app here you can connect it to a specific Dynamics 365 record.
Users who do not have a Dynamics 365 license or not a valid security role in Dynamics 365 will not be able to access the information but will receive a warning
Linking Microsoft Teams files to Dynamics 365 records
When you create a new Microsoft team behind the scenes a SharePoint Online site is being used, and each channel in a team gets a folder within the default team site document library (Read How SharePoint Online and OneDrive for Business interact with Microsoft Teams for more details and watch the video Foundations of Microsoft Teams to get an architectural overview) So basically the integration between Dynamics 365 and files in Teams is being built on top of the existing SharePoint integration for which the fundamentals already existed.
To be able to link Microsoft Teams files to Dynamics 365 records you will first need to activate preview functionality within your Dynamics 365 system settings (Settings>Administration>System settings)
Next a new button will appear in your mean which allow you to link to a specific team and channel.
The linked Teams documents will appear in the same place as linked SharePoint documents (under the cover they actually are stored in SharePoint - take a look at Showing SharePoint document properties in Dynamics CRM views for a more detailed explanation of how this is done).
For the official documentation on this preview see Preview: Integrate Dynamics 365 for Customer Engagement apps with Microsoft Teams
Labels:
CDS,
chatbots,
collaboration,
Customer Engagement,
Dynamics 365,
microsoft,
msdyn365,
msdyncrm,
MSTeams,
Teams
Monday, January 07, 2019
Must read Dynamics 365 App for Outlook blog series
Great series from Aaron Richards on the Dynamics 365 App for Outlook
- Dynamics 365 App for Outlook Part 1 – The basics
- Dynamics 365 App for Outlook Part 2 - What is supported – some interesting gotchas on Outlook App on mobile and OWA as well as supported scenarios for hybrid setups.
- Dynamics 365 App for Outlook Part 3 – Settings that affect tracking and correlation
- Dynamics 365 App for Outlook Part 4 – Working with Emails
- Dynamics 365 App for Outlook Part 5 – Working with Appointments
- Dynamics 365 App for Outlook Part 6 – Working with Contacts
- Dynamics 365 App for Outlook Part 8 – Email governance
- Adding custom entities to the Dynamics App for Outlook and official documentation Filter entities and views that appear in the Dynamics 365 App for Outlook - when the Outlook App for Dynamics 365 (9.0) was initially released, it was not possible to customize the Outlook app module now it is
- Make the most of the new Dynamics 365 App for Outlook
- How to initiate the Outlook App deployment
Labels:
CRM,
Customer Engagement,
Dynamics 365,
Dynamics CRM,
microsoft,
Outlook
Subscribe to:
Posts (Atom)





