Archive
[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.
Reason:
- 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.
Fix:
- By Setting ‘Currency’ field manually, fixed the issue.
- 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.
Notes:
- 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.
🙂
D365 Customer Service – Virtual Agent – Get Started
Virtual Agent for Dynamics 365 Customer Service is a new cloud offering built on the Microsoft Bot Framework to create powerful bots using a guided, no-code graphical interface.
In this article, lets see how to get started with ‘Virtual Agent’ using a simple demo.
Prerequisite:
- Subscribe to a Dynamics trail .
Steps to Subscribe ‘Virtual Agent'(Preview):
- Go to ‘Virtual Agent’ Portal and click on ‘Try preview’
- Login with your O365 credentials.
- Continue by clicking on ‘Create’ link.
- You will be redirected to ‘Virtual Agent’ application with a ‘Create a new bot’ popup
- Provide the bot’s name and click ‘Create’
- Initial Bot set up would take 2-4 minutes and you would be notified post completion.
- Once the bot set up completes, you need to configure ‘Topics’ to start the bot conversations.
Create ‘Topics’:
- ‘Topics’ allows to set context of bot conversation. Its a combination of 2
- Trigger Phrases – Prompts the conversation with BOT. Phrases like ‘Hi’, ‘Hello’, ‘Help’, ‘Issue’ are sample phrases.
- Conversation – Represents exchanges between bot and user.
- Lets create a simple ‘Topic’ by name ‘Welcome’ to wish the User by his name.
- Click on ‘Go to Topics’ link or ‘Topics’ tab.
- From the ‘Topics’ tab, click on ‘New Topic’
- Add the ‘Trigger Phases’
- I added ‘Hi’ and ‘Hello’ as my Phrases to initiate the conversation.
- Click ‘Edit’ under ‘Conversation’ section
- Now you will be redirected to ‘Conversation’ flow page.
- Add ‘Bot Says’ control, to communicate to User from BOT.
- Add ‘User Responses’ control, to provide options to User to answer
- For example, I am adding ‘Tampa’ and ‘Orlando’ as ‘User Responses’ to show the city names as options for User to pick.
- You can also create a variable to capture User response.
- I created 2 variables to capture User’s ‘Name’ and ‘City’.
- Save the Conversation
Test the BOT:
- Once you configured ‘Topics’, you can test the BOT by clicking ‘Test your bot’ link on the footer.
- Turn on ‘Tracing’ to check the flow.
Deploy the BOT:
- Click ‘Deploy’ to configure Channel.
- For this demo, I am choosing, ‘Demo Website’ option, which hosts the bot to a sandbox demo website.
- Demo Website:
- Provide the details and click on ‘Publish’. You will be redirected to the demo website.
- Type ‘Hello’ phrase to initiate BOT conversation.
- BOT responds back asking ‘Please help with your Name’
- You can also see City options, which User can select instead of typing.
- Finally, Bot responds back wishing User by capturing Name and City provided by the User.
- Custom Website
- This is the second deployment option.
- Allows you to host the BOT in an IFrame control to your web site.
- Copy the HTML content and paste it in your web site.
🙂
Dynamics Portals – Using ‘Emojis’ in Entity Form and Entity List
In this article, lets see how to use Emoji’s to capture the data in Portal’s Forms.
It’s very simple to achieve. All you need to do is to set the Dynamics ‘Option Set’ field’s ‘Label’ with ‘Emoji’.
Below is the ‘HOW’ part.
Create an ‘Option Set’ field with ‘Emojis’:
- In Dynamics, create a new ‘Option Set’ Field with 2 options
- In the Option’s ‘Label’ paste the Emoji.
- Place this ‘Option Set’ field on the Dynamics Form and View which are being referred in your portal’s ‘Entity Form’ and ‘Entity List’.
Make ‘Options’ to render side by side in Portal:
- By default, ‘Option Set’ renders as ‘Drop down’ control in Portal.
- To show the ‘Options’ as Side by Side, add a new ‘Metadata’ to ‘Entity Form’.
Test the Emojis in Portal:
- Navigate to Portal and open the ‘Employees’ view. Option Set value would renders as ‘Emoji’
- Open the record and you should get ‘Emojis’ rendered side by side.
Note:
- You can ‘Copy’ the Emoji from here . Search the Emoji as per your requirement and click ‘Copy’.
- The rendering of Emojis will be same in ‘Dynamics Web Application’.
🙂
D 365 – How to access Customization’s and Solutions in UCI Only Mode
To know more about ‘Unified Interface Only mode’ refer my previous article
Below are the steps to access environment settings, customization’s and solutions when the ‘Unified Interface Only mode’ turned on.
- Click on ‘Advanced Settings’ from the ribbon
.
- It will open up ‘Settings’ tab in classic web mode.
- You can access your solutions and make customizations how you used to do earlier.
Refer the documentation to know more about ‘Unified Interface’.
🙂
D365 – How to turn On/Off ‘Unified Interface Only mode’
Today, I subscribed to my new D365 30 days trail and noticed the ‘Sales’ web Application opening up in ‘Unified Interface’ mode rather than in Classic web mode by default.
When noticed, the URL of the Dynamics landing page (My Apps) has a parameter forceUCI=1
It seems that Unified Interface ONLY mode has been implied on my new instance.
What is Unified Interface Only mode?
- As per the documentation, Microsoft product team wants us to adopt to UCI (Unified Client Interface), to provide superior performance and usability.
- All the new Dynamics 365 for Customer Engagement environments (instances) and Common Data Service environments, will be provisioned in Unified Interface Only mode.
Enable/Disable Unified Interface Only mode:
- To Enable/Disable Unified Interface Only mode, navigate to ‘Settings’ tab by clicking on ‘Advanced Settings’ from the ribbon
.
- Open Settings -> Administration -> System Settings
- Select the option under ‘Use the new Unified Interface only (recommended)’ section.
Accessing the legacy web client app:
- The legacy web client app, also known as Dynamics 365 – custom, is hidden from end users when a new environment is provisioned.
- It is always visible to those with System Administrator and System Customizer roles, and to other custom roles with similar privileges.
- To enable the Legacy App to non-admin users,
- Go to Settings > Administration > System Settings > General tab. Under Show legacy Dynamics 365 – custom app, select Yes for Show this app to all users, not just administrators.
- In the Power Platform Admin center, go to Environments and select an environment. Go to Settings > Behavior > Interface settings and then turn on Show legacy app to everyone, not just admins.
- Note:
- When ‘Unified Interface Only mode’ is enabled, Dynamics 365 – custom opens in Unified Interface and not in the legacy web client.
- Legacy app opens only If users only have access to the Dynamics 365 – custom app and no other model-driven apps.
🙂
ADX/Dynamics Portals Issue – Missing Entity ‘Tab’ in ‘Web Form Step’
We have ADX portal 7.0 solution installed on our Dynamics 365 8.2 application. We got a requirement to create a Web Form steps on a Custom Entity ‘Employee’.
‘Employee’ entity has an OOB ‘Information’ of ‘Form Type’ Main, with a tab named ‘Personal Details’.
Issue:
- While adding a Web Form step, there was no ‘Personal Details’ tab and could get only ‘general’ tab.
- In the new ‘WEB FORM STEP’, select the ‘Form Name’
- In the ‘Tab Name’ drop down, there is no ‘Personal Details’ tab and all it had was ‘general’ tab.
Reason:
- As there were 2 OOB forms (i.e., Form Type ‘Main’, ‘Mobile – Express’) with the same name ‘Information’, ADX solution always picking ‘Mobile – Express‘ form which had a tab ‘general’
Fix:
- Renamed ‘Information’ Main form to ‘Employee’.
- Publish the solution
- Refresh the ‘Web Form Step’ and you should see ‘Personal Details’ tab once you select the ‘Employee’ form.
🙂
[Step by Step] Postman tool to test Dynamics 365 online Web API
In this article, lets see how to connect and test Dynamics 365 Web API requests using Postman tool, step by step along with troubleshooting steps.
Note: Refer article for steps to connect to Dataverse Web API from Postman tool.
Those who are not familiar with Postman tool, it is a request composer tool, which allows you to authenticate to your Dynamics 365 instance, compose Web API requests, send them, and view response. Link to download
Prerequisites:
- Download Postman tool
- Dynamics 365 online instance. (Subscribe to 30 days trial, if you have not one)
- Azure Active Directory Portal (You need to login with your Office 365 Credentials)
Register App in Azure Active Directory:
As a first step, you need to register an App in Azure Active Directory (i.e., oAuth) by following below steps
- Connect to the Azure Active Directory (AD) Portal with your Office 365 credentials.
- Register a new Dynamics 365 App by following steps mentioned here
- Once you are done with App registration, copy ‘Application ID’ and ‘Home page’ values, which you need to use next steps.
Setup your Postman tool:
Create ‘Environment’
- Create a new Postman ‘Environment’ with below variables. This is one time activity for a single D365 instance.
- url : Your Dynamics 365 URL
- clientid : ‘Application ID’ from Azure AD, generated in above section.
- version : Dynamics version
- webapiurl : Set this to {{url}}/api/data/v{{version}}/
- callback : ‘Home page’ value from Azure AD, generated in above section.
- authurl : Set this to https://login.microsoftonline.com/common/oauth2/authorize?resource={{url}}
- I created a new ‘Environment’ with name ‘DynamicsCRM’ and it looks as below
Generate oAuth Access Token:
Post ‘Environment’ creation, we need to generate oAuth Access Token. This is one time activity for a single D365 instance.
- Make sure you select ‘Environment’ created in previous section. In my case its ‘DynamicsCRM’.
- Under ‘Authorization’ tab, set ‘Type’ to ‘oAuth 2.0’ and click on ‘Get New Access Token’.
- In the ‘GET NEW ACCESS TOKEN SCREEN’ make sure you set values as below.
- Click ‘Request Token’ and system will prompt you for credentials, pass your O365 credentials.
- When you click ‘Next’, you may encounter “response_type ‘token’ is not enabled for the application” exception.
- To fix this, make sure in your Azure AD Application’s manifest “oauth2AllowImplicitFlow” property is set to ‘true’
- You may also encounter “The reply url specified in the request does not match the reply urls configured for the application“.
- To fix this, make sure you set the Postman’s ‘Environment’ -> ‘callback’ variable set correctly.
- Click ‘Continue’ to complete the ‘Access Token’ generation process.
- On successful ‘Access Token’ generation, you would get the screen as below.
- Click ‘Use Token’.
That’s it! we are done with settings and its time to test the Dynamics API’s with Postman
Test by executing ‘WhoAmI’ request:
- Make sure you select the right ‘Environment’ and generated your ‘Access Token’.
- Select ‘GET’ operation and set the URL as {{webapiurl}}WhoAmI
- Click ‘Send’
- You should get “200 OK” response up on success.
- You may get “401 Unauthorized” response.
- To fix this, make sure you set “Add authorization data to” to “Request Headers”.
🙂
Dynamics 365 – Configure Custom ‘Help Page’
‘Help’ feature in Dynamics 365 is a useful and an intuitive way to provide guidance to the end users.
Sometimes we may get a requirement from customer to configure ‘Custom Help’ page.
Its simple to configure the custom help screen from Dynamics 365 ‘Admin Center’ Settings screen.
Steps to configure custom Help URL:
- Connect to your Office 365 Admin Center
- In the ‘Environments’ tab, select the instance and click on ‘Settings’
- In the ‘Settings’ screen, click on ‘Products -> Features’
- Under ‘Help features’, turn ON the “Custom help for customizable entities”.
- In the ‘Global custom help URL’, provide your custom web link.
- I provided my blog URL in this case.
- Select ‘Append parameters to URL’ option, if you want to pass the “typename”, “formid” etc.. parameters to your custom URL.
- Alternatively, you can also configure the same from ‘Administration -> System Settings’
Steps to test the Help URL:
- Connect to your dynamics instance.
- Click on Help(?) icon
- You will be redirected to the configured URL
🙂
Dynamics 365 – Get ‘April 2019’ update
Last weekend, I subscribed to a Dynamics 365 30 days trail and noticed that now we can upgrade to ‘April 2019’ update and start exploring the features.
Below are the steps to update your instance to ‘April 2019’.
- Connect to your Office 365 Admin Center
- In the ‘Environments’ tab, select your environment and navigate to ‘Settings’ page by clicking on Instance name hyperlink.
- In the ‘Settings’ screen, under the ‘Updates’ tab, click on ‘Manage’ link
- In the ‘Updates’ slider window, click on ‘Active now’ to get the ‘April 2019’ update
- Confirm by providing your instance name in the text box, as below.
- That’s all we need and enjoy your ‘April 2019’ update.
Note:
- You cannot revert once you activate the ‘April 2019’ update.
Refer the link for what’s included in ‘April 2019’ update
🙂