Archive for the ‘Dynamics 365’ Category

[PowerApps Portal (preview)] Build your first portal

PowerApps Portalsprovides ability to build low-code, responsive websites which allow external users to interact with the data stored in the Common Data Service.

Refer article for introduction. PowerApps Portals are in Preview now and lets see how to get started with a simple portal.


Steps to build your first Portal:

  • Login to PowerApps maker Portal
  • Pick the right ‘Environment’. Refer ‘Notes’ section below to know more about ‘Environments’.
  • Click on ‘Portal from blank (preview)’ link.


  • In the pop-up, fill ‘Name’, ‘Address’ and ‘Language’ and click ‘Create’.


  • Portal provisioning takes time and you will be notified once done.


  • Post provisioning, click on ‘Edit’ which will redirect you to Portal editor.


  • You get pre configured ‘Home’ page and ‘Child Pages’.
  • To add a new Page,
    • Either click on ‘+New page’ from ribbon
    • Or Right Click , ‘Home’ and add a New Page.


  • I have added a new ‘Accounts’ page and filled the details on the right side ‘Component’ panel.
  • To create a new ‘Account’ form, click on ‘Form’ and choose Entity, Form and Mode from the ‘Component’ panel.


  • To add a new ‘Entity List’ control, click on ‘List’ and on the right hand side, select ‘Entity’ and ‘Views’
    • Note: In the screen below, I’ve added an existing ‘List’. The properties are same for new ‘List’ as well.


  • To map the Account ‘Form’ with ‘List’, set properties as below


  • At any point of time, to view the changes, click on  ‘Browse website’ on top right corner.
  • Home Screen


  • Accounts Screen



  • To use the Dynamics CE entities, you have to select the CE ‘Environment’ in your maker portal, before the start of Portal creation.
    • A ‘default’ environment gets created by default. If you pick ‘default’ environment, you will need to create a new Environment with CDS database.



New Environment

  • We can still create Portal from the ‘Dynamics Admin Center’.


  • PowerApps portal got ‘’ as domain and regular portal will be of ‘’ domain.


  • You can still create/update portal components (i.e., Entity List, Forms, Web Templates) from Dynamics web application.
  • Clear cache using ‘/_service\about‘ is still available in PowerApps portal.






Office 365 Groups + Dynamics 365

In Dynamics 365 online, records can be owned by ‘Office 365 Groups’. Refer my previous article and following are quick notes.

  • The administrator can create Azure AD group teams that are associated to the Azure AD groups in each of the Customer Engagement and Common Data Service environments and assign a security role to these group teams.
  • When members of these group teams access these environments, their access rights are automatically granted based on the group team’s security role.

If you notice, to get the benefits of AAD group ownership, Users must have assigned ‘Dynamics 365 Customer Engagement Plan’ license.

What if the User don’t have ‘Dynamics 365 Customer Engagement Plan’ license. For example, when a sales team has a major opportunity requiring input from several people who don’t have access to Customer Engagement apps.

Office 365 Groups provides a single location to share documents, conversations, meetings, and notes.

Office 365 Groups can be enabled for any entity.

Install Office 365 Groups solution:


  • Install ‘Office 365 Groups’ solution.


Enable entities for Office 365 Groups:

  • Connect to your Dynamics instance.
  • Go to Settings -> Office 365 Groups
  • Add required entities.


Create Office 365 Group:

  • Make sure users must have ‘Office online’ license and Mailbox configured.


  • Create a Group and add the Users.


  • Users get notifications in their Outlook web app
  • From Outlook, Users can click on ‘Discover’ to explore more available groups.


  • Also a new SharePoint Sitemap collection gets created for each Group, which allows Users to share documents.


Use Office 365 Groups from Dynamics App:

As we enabled ‘Office Groups’ for ‘Account’ entity

  • Open any account from Dynamics App.
  • From sitemap, click on ‘Office 365 Groups’
  • You can either ‘Create a new group’ or use an existing group.


  • Once the configuration is completed, you can start Conversation and share documents which would be available for all members of the group.





Working with Azure Active Directory (AAD) Groups in Dynamics Customer Engagement

July 6, 2019 1 comment

In Dynamics 365 online, along with ‘Owner’ and ‘Access’ type, following types have been introduced in ‘Teams’.

  • AAD Security Group
  • AAD Office Group


With these new ‘Team Types’, records in Dynamics 365 can be owned by AAD Groups.

Lets understand what is Azure Active Directory (AAD) group and what’s the significance of making AAD group as owner of a Dynamics record.

  • The administrator can create Azure AD group teams that are associated to the Azure AD groups in each of the Customer Engagement and assign a security role to these group teams.
  • When members of these group teams access these environments, their access rights are automatically granted based on the group team’s security role.

Create AAD Group:

  • Make sure you have Office 365 account (Subscribe to 30 days trail here)
  • Connect to Microsoft 365 Admin Center using Office 365 credentials.
  • Create Users and assign ‘Dynamics 365 Customer Engagement Plan’ license.


  • Now connect to Azure Active Directory Portal
  • Create a new Group of type ‘Office’ and add the Users.
  • Copy the ‘Object ID’ which we need in next steps.


Create Team of type ‘AAD Office Group’:

  • Connect to Dynamics instance
  • Navigate to Settings -> Security -> Teams -> New
  • Select ‘Team Type’ as ‘AAD Office Group’ and paste the AAD Group ‘Object Id’ copied in above section.
  • Save and assign a role.


Access the Dynamics as ‘AAD Group’ Team Member:

As we created a AAD Group and a Team in Dynamics App with ‘Sales Manager’ security role, it’s time for ‘Test User 1’ to access the Dynamics Application.

  • Login to Dynamics Application as ‘Test User 1’
  • Post login, Dynamics App greeted me with ‘You need a Microsoft Dynamics 365 security role to continue’ message.


  • From the message, its clear that Dynamics App expecting ‘Test User 1’ to have a User level Security role and not honoring the Team level Security Role which he is member of.
  • We can resolve this issue by assigning ‘Sales Manager’ role to ‘Test User 1’ which means for every User of AAD group we have to on-board by assigning them an individual security role.
  • But we can make ‘Test User 1’ access Application with out assigning a Role, as we got a cool ‘Member’s privilege inheritance’ feature introduced in ‘Security Role’.

‘Member’s privilege inheritance’ in Security Role:

  • Navigate to ‘Settings -> Security -> Security Roles’
  • Open the ‘Sales Manager’ security role.
  • Change the ‘Member’s Privilege Inheritance’ to ‘Direct User (Basic) access level and Team privileges‘ and Save.


  • Refresh the Dynamics application, ‘Test User 1’ can access the records and application.


  • By setting ‘Member’s Privilege Inheritance’ to ‘Direct User (Basic) access level and Team privileges‘ makes the ‘Sales Manager’ role as both User role as well Team role.
  • This feature eliminates the need of AAD Admin to assign User level roles to individual group members.

Assign Records to ‘AAD Group’ Teams:

  • We can assign the record to ‘AAD Group’ Teams similar to ‘Owner’ Teams.





D 365 Managed Solutions – Delete Components from target instance using ‘Stage for Upgrade’ option

July 3, 2019 1 comment

Assume that you have exported and imported a Managed Solution ‘A’ from DEV to TEST. The solution ‘A’ has 2 entities (E1 and E2) and got imported to Test instance.

Now, because of a change in requirement, you no longer required E2 entity and need to delete that from TEST instance.

How would you delete E2 using Solutions approach?

With ‘Upgrade Solution’ behavior of ‘Managed Solution’ (Refer flow below), solution components only gets updated but not the deletion of the components.


And the answer to this is ‘Stage for Upgrade’ option of ‘Managed Solutions’.

Lets take following scenario to understand it better

  • DEV instance has an entity ‘Interest Rate’
  • Export a Managed solution with ‘Interest Rate’ entity from DEV and import to TEST.
  • Delete the ‘Interest Rate’ entity from DEV
  • Prepare a Managed solution and import to TEST using ‘Stage for Upgrade’ option.
  • ‘Interest Rate’ entity should get deleted from TEST

Below is my TEST instance which has managed solution by name ‘Loan Management’ got installed with ‘Interest Rate’ entity.


Steps to use ‘Stage for Upgrade’ option:

Below are the usage steps of ‘Stage for Upgrade’ option.

Export Solution from DEV:

  • Connect to the DEV instance and delete the ‘Interest Rate’ entity.


  • Increase the version number of the ‘Loan Management’ Solution and export as Managed Solution.


Import Solution to TEST:

  • Connect to TEST instance and click on ‘Import’ solution and make sure versions are different.


  • Click ‘Next’
  • Select ‘Stage for Upgrade’ checkbox and click ‘Import’


  • Up on successful import, As a last step, you would get ‘Apply Solution Upgrade’.


  • Don’t click the ‘Apply Solution Upgrade’ yet as we need to check few things.
    • Note: You can always click ‘Apply Solution Upgrade’ and complete the upgrade. I refrained to do as I want to explain more.
  • Close the ‘Import Solution’ wizard.
  • Now on TEST instance, go to Advanced Find -> Interest Rate and you will still get the entity and data. Which means the Upgrade hasn’t happen yet.


  • Lets complete the Upgrade by go to Settings -> Solutions and you will see 2 solutions
    • Solution with ‘_Upgrade’ is Stage solution.


  • Select the old solution (i.e., Solution with no ‘_Upgrade’) and click on ‘Apply Solution Upgrade’.


  • The process takes time and once completed you would see a single solution with increase in version.


  • Now, go to Advanced Find -> Interest Rate and you will not get the entity and data.


Refer this White Paper for more details on Solution Life Cycle Management.


[Step by Step] Dynamics 365 – Microsoft Forms Pro Survey Solution

Microsoft Forms Pro is an enterprise survey capability powered by both Office 365 and Dynamics 365.

Forms Pro is built on Microsoft Forms, and it offers new capabilities that make capturing and analyzing customer and employee feedback simpler than ever.

‘Forms Pro’ will eventually replaces the existing Dynamics Voice of the Customer Survey

Steps to subscribe:

  • Connect to
    • Either subscribe for a free 30 days trail or alternately you can also use Dynamics 365 30 days trails credentials.
  • Provide your Office 365 Email ID and click on ‘Submit’ to complete registration.


Create a new Survey:

Once you completed the subscription, from the FormsPro portal

  • Click on ‘Create a new form’ to configure your survey.


  • Click on ‘Theme’ to choose the Survey Theme. This is an optional step.
  • Provide the Survey Details like Name and Description.


  • Next, to add Survey questionnaire, click ‘Add Option’ to add the available control options


  • I’ve chosen ‘Choice’ control for this simple survey.
  • Fill the Questions and Choices.
  • Click on ‘Preview’ to preview the survey in both Computer and Mobile.


Send The Survey:

After your survey is ready, send it to your respondents and collect their feedback. You can send your survey in the following ways:

  • Email: Send the survey link by using the built-in email capability.


  • Microsoft Flow: Configure a business trigger by using Microsoft Flow to send the email.
  • Embed: Embed the survey in a webpage.
  • Link: Copy a link to the survey that you created, and paste it into a shared area.
  • QR code: Send a QR code for your survey.

Respond to Survey:

  • To show how the Survey would render to recipients, I’ve used ‘Link’ option and copied the Survey URL in browser tab.
  • It renders as follows.


  • Choose your response and ‘Submit’.

Analyze Responses:

  • Click on ‘Responses’ tab to analyse the responses.


Survey Settings:

Click on ‘…’ and ‘More Settings’ to configure Survey settings.

  • To deactivate the Survey (i.e.,Stop collecting the responses) uncheck the ‘Accept Responses’ checkbox.


  • Deactivated Survey would show up as follows to Recipient.


  • You can set the Date range of the Survey.

Entities that get added:

Following entities get added with ‘Form Pro’ survey solution



Refer this article for more details.




[Fix] Rollup field error – Record currency is required to calculate rollup field of type currency

I have added a new Rollup field of type ‘Currency’ to my existing custom entity ‘Customer’, which ‘SUM’ up the currency field’s data from related entity ‘Loan’.


Post customization, when I open the existing Customer record, following error showed up on Rollup field.



  • This error would occur, only those records created before the new Rollup field added to the entity, since they will not contain valid data in the Currency (TransactionCurrencyId) field.
  • To check the understanding, I added the OOB ‘Currency’ field to the form and as expected, it was blank.



  • By Setting ‘Currency’ field manually, fixed the issue.Rollup_3
  • Alternately, If the existing data is trivial, delete them all as the records created after the addition of the Rollup field, should automatically have the currency field set, and the rollup field should thus work correctly.


  • Those who are wondering what is ‘Currency’ field, the first time a new currency field added to an entity, Dynamics creates total of 4 fields, as following:


  • If you notice, in the above list, ‘Currency’ is OOB field that gets added by Dynamics, which is a lookup to ‘Currency’ entity.


Common Data Model (CDM) – Intro

The Common Data Model (CDM) is an open-source definition of standard entities and a metadata system that enable consistency of data across apps and business processes.


Today, the Common Data Model is used within Common Data Service (CDS), which supports Dynamics 365, PowerApps, and the data-preparation capabilities in Power BI dataflows to create schematized files in Azure Data Lake.

With CDS we define an entity which can be leveraged by Dynamics 365, PowerApps and Power BI.

Dynamics 365 Healthcare Accelerator is an example of CDM which built on FHIR-based data model.

Explore the Common Data Model (CDM) using the Visual Entity Navigator

  • Click on ‘Load from Github’ button, which load all available Open Source CDMs.
  • Once definitions loaded, click on an entity to explore its schema


Refer this article to know more about CDM.