Company Blog Dynamics 365

With the release of Microsoft Dynamics 365 and Power Platform 2020 Release Wave 2, Microsoft has made several enhancements related to the email experience in model-driven apps. This post will cover the email file attachment enhancements as well as the new experience for email templates.

For anyone who has experience with Microsoft Omni channel interface, and has enabled the 2020 Wave 2 Release Plan, there is a new app that appeared with the name Customer Service Workspace (Preview). As noted in the release plan, the multisession app allows customer service agent to multitask on several customer cases simultaneously and seamlessly switch among issues without losing context of the in-progress work.

With the release of the documentation of the Portals Web API by Microsoft on July 16, I was waiting for a chance to test these features out and see how easy or hard it would be to get this working. There are a few requirements and prerequisites to get this working, which I will describe in this post. Remember that the portals are still in preview, which means that some of the content of this post might change prior to the final release of this API.

Recently in the forums, there were a few questions on how to send emails to all of my customers. While there might be different options, and the right solution to this might greatly depend on the frequency that you need to be sending this as well as the number of contacts, I thought I would demonstrate a few different approaches to implement this using Microsoft Power Automate.

Today, July 8, 2020, Microsoft released the Power Platform and Microsoft Dynamics 365 2020 Release Wave 2 plan documentation with a list of all the features that will be made available in the Wave 2 timeframe which starts October 2020 until March 2021. Going through all of the features is almost impossible unless you want a few hundred pages of documentation.

In this post, I am going to review some of my favorite and anticipated features in the Power Platform, especially Power Apps Portals and Model Driven Apps.

I have been working in the Government space for a few years now, and most implementations of the Dynamics and Azure tenants and environments are hosted in the Government Cloud. This means that there are a lot of restrictions that we have to deal with, not only from Microsoft but also from the internal IT policies.

As I was going through one of my solutions in the last few days, I noticed that there are a few changes that were made to the Solution experience, and wanted to share this with everyone. Usually we see a change appear here and there, but it seems like Microsoft is trying hard to simplify the experience and add the missing pieces that are available in classic and not yet available in the Modern experience.

I have started working with AI Builder recently and yesterday I finally took a look at the Business Card scanner. I decided to check how this works in the different apps, both Modal Driven as well as Canvas Apps.

Since the announcement by Microsoft at the Microsoft Business Applications Summit last month, and even before, I’ve been eager to take a look at the new SQL Connection for the Common Data Service Endpoint. What this means is that we can not write and execute SQL queries against the entity data.

In order to get started, the first thing that has to be done is enabling the Endpoint, so that we can create a connection from SQL Server Management Studio (SSMS) to our Dynamics/CDS environment. As of now, there are two ways to enable this endpoint.