Nishant Rana's Weblog

Dynamics 365 QUEUE setup with shared mailbox

This post is a part of a series of posts for Customer Service. The complete GUIDE can be found here
I assume you have a Dynamics Environment at this point.

Exchange

Open https://admin.microsoft.com – login with the credentials you got from the trial, or make sure you are a Global Admin to complete the following tasks.

You now have a shared mailbox in Exchange. We will be using this email address to configure a queue in Dynamics Customer Service.

Dynamics 365 – Queue

If you don’t remember the address to your dynamics environment, you can always find your environments at https://admin.powerplatform.microsoft.com <- click … and then open.

Locate the queue setup from Dynamics Customer Service Hub. This is where we create a new queue for Support@. For the owner we choose Customer Service Team.

Click Save, and the system will automatically give you a new mailbox.

To configure the mailbox…

View original post 110 more words

Collaborate using Comments (preview) in Modern App Designer – Power Apps / Dynamics 365

A new comments (preview) feature has been added recently in the Modern App Designer

Modern App Designer – https://nishantrana.me/2021/06/09/modern-model-app-designer-preview-dataverse-dynamics-365/

To see it in action, open an existing app or create a new app using the Modern App Designer.

We can see the Comments (preview) options in the toolbar.

Comments allow us to add notes, discuss with colleagues using mention etc.

We can add multiple comments and it shows the count.

The comments can be edited, deleted, and resolved.

This is how the resolved comment look like – disabled

We can add comments to the page of type – view, form, dashboard, and custom page.

We can add comment also within the Navigation bar.

Currently, mention is not listing any suggestions –

Check here for more such features added – https://powerapps.microsoft.com/en-au/blog/round-up-of-the-ignite-announcements-for-power-apps/

Hope it helps..

Advertisements

{Power 2021} Clear and Update Custom queue field on Case based on Queue items related to the case

MSDYNAMICSBLOG BY DEEPESH

Pre-requisites:

Should have “Customer Service Hub” app installed in your tenant
Add out of box “Case” entity in your solution
Create a custom lookup field (Lookup to Queue) titled as “Queue” under Case entity and place it on “Case for interactive experience” form

Requirement:

The Queue to which Case is assigned should get displayed under Queue lookup field
If we are closing the Case as “Resolved” or “Cancel” – Queue lookup field should be set to null

Implementation:

Now, we are creating an “Automated Cloud flow” to implement above 2 requirements mentioned above:

Open Solution >> Select Cloud flow from left navigation (Make sure you have selected the correct environment)

Click on drop-down arrow next to “New” button >> Select “Automation” >> then select “CloudFlow” >> then select “Automated Cloud flow”

Now, give name to your Cloud flow and select the…

View original post 481 more words

Fixed – The API version ” is not valid for provider ‘Microsoft.BusinessAppPlatform’ – Action ‘Force_Sync_user’ failed error – Power Automate

Recently while testing a flow we got the below error message

The API version ” is not valid for provider ‘Microsoft.BusinessAppPlatform’ The supported list of API versions are: ‘2016-02-01, 2016-11-01, 2018-01-01, 2018-10-01, 2019-05-01, 2019-10-01, 2020-04-01, 2020-05-01, 2020-06-01, 2020-08-01, 2020-09-01, 2020-10-01, 2021-03-01, 2021-04-01, 2021-07-01’.

API Version is as the name suggests is the version of the API, as there could be discrepancies in the different versions of API with regards to the input and the output parameters or some other changes.

We were using the below template

Force Sync Azure Active Directory Group members to specified CDS instance

The existing Force Sync user action in the template was having the API version as blank.

The way we fixed it was by adding a new Force Sync user action and deleting the existing one.

The new version of Force Sync User action was listing down the Environment in the drop-down and also had the version number mentioned in it.

After making the changes, this time it ran successfully.

Also, check

https://nishantrana.me/2021/12/14/the-trick-to-force-trigger-user-sync-power-platform-dynamics-365/

https://nishantrana.me/2021/12/13/using-force-sync-user-to-sync-powerapp-crm-users-power-platform-dynamics-365/

Hope it helps..

Advertisements

The trick to force / trigger user sync – Power Platform / Dynamics 365

Sometimes it takes a long time for the users to appear in Dynamics 365, even though users have the appropriate licenses.

E.g. here we have added user6 in Microsoft 365 Admin Center.

Back in CRM, we do not see user 6 added.

One way to add the user is through Force Sync User action of Power Platform Management connector.

https://nishantrana.me/2021/12/13/using-force-sync-user-to-sync-powerapp-crm-users-power-platform-dynamics-365/

or the other option is to ask the user to log in to the Power Apps.

As soon as the user logs in we can see his account added/synced to the enabled users in CRM.

Thanks to Emre Gulcan for this trick

Hope it helps..

Advertisements

Using Force Sync User to sync PowerApp / CRM users – Power Platform / Dynamics 365

Recently in one of our trial environments, some of the users were not showing up in the Enabled Users view in Dynamics 365, although the users were having appropriate licenses assigned to them. (was more than 24 hours)

In such a scenario we can use Force Sync user action of Power Platform Management Connector.

https://docs.microsoft.com/en-us/connectors/powerplatformforadmins/

For Force Sync users, we will be passing the object id of the user and selecting the appropriate environment.

Run the flow manually.

It asks for the Object Id of user.

Inside Azure Portal >> Azure Active Directory >> Users, get the Object Id of the user

Currently, we have below 3 users in CRM

Let us run the flow.

Wait for the flow to complete.

After successful execution of the flow, back in CRM, we can see user 5 added to the list of enabled users.

In case we are using a security group for the environment we can make use of the below Power Automate Template, it takes the security group’s object id as input and loops through each of the members and applies Force Sync user action.

We can also make use of PowerShell cmdlets to achieve the same

https://nishantrana.me/2021/01/20/force-sync-users-from-azure-ad-to-dynamics-crm/

Force Sync Azure Active Directory Group members to specified CDS instance

Hope it helps..

Advertisements