Tag: Dynamics 365

Fixed – Unified routing was unable to provision error while trying to configure Unified routing


Recently while trying to set up Unified Routing, we got the below error.

“Unified routing was unable to provision. Please try again or contact Microsoft Support”

The user had the system administrator role and we already had the global administrator’s consent, which should be good enough to set up unified routing.

We tried with different system administrator users but that doesn’t resolve that error.

Eventually, we tried the setup with the same user but in a different VDI (Virtual Desktop Infrastructure), and the setup worked properly without any error. One probable reason could be, that the appropriate URLs being accessed during setup were already whitelisted in the other VDI, which wasn’t the case in the first VDI where we were trying.

Hope it helps..

Advertisements

Fixed – We couldn’t load your user roles from the selected Dynamics 365 Organization error while trying to set up Microsoft Dynamics 365 Marketing


Recently while trying to set up Microsoft Dynamics 365 Marketing on an existing Dataverse environment, we got the below error.

“We couldn’t load you user roles from the selected Dynamics 365 Organization. Please try again”

The user had the system administrator role, which is good enough to set up marketing.

We tried replicating the same in other trial environments but were not able to replicate the above error.

Eventually, we tried the setup with the same user but in a different VDI (Virtual Desktop Infrastructure), and the setup worked properly without any error. One probable reason could be, that the appropriate URLs being accessed during setup were already whitelisted in the other VDI, which wasn’t the case in the first VDI where we were trying earlier.

Hope it helps..

Advertisements

How to – Use the new command designer to customize the command bar – Dynamics 365 / Power Apps


Using the modern app designer either open an existing model-driven app or create a new model-driven app in https://make.powerapps.com/

Select Edit >> Edit in preview

Select any entity/table and select the Edit command bar (preview)

The different command bars that can be edited are the Main grid, main form, subgrid view, and the associated view.

  • Main Grid view–

  • Main Form view –

  • Subgrid view–

  • Associated view –

The legacy / classic button is not supported currently.

Check out all the known limitations

https://docs.microsoft.com/en-gb/powerapps/maker/model-driven-apps/command-designer-limitations

limi

Let us try adding a new command/button in the Main Form, and see what options do we get there.

Select + New command or the + New option

It adds a new button with the label NewCommand with options to duplicate, hide, move up and down, etc.

The different properties that can be configured for the new command –

Property

Description

 

Label

To set the label

Icon

To set the icon either using icon or web resource

Tooltip

Set tooltip title and its description.

Order Number

Customize the Order of the command

Action

Either run formula or run javascript

 

Open Formula Bar

 

Library for Run JavaScript

Visibility

  

 

Open Formula Bar for Show on Condition

Let us Save and Publish

Click on Play and open a lead form.

We can see the new command added.

Get all the details here –

https://docs.microsoft.com/en-gb/powerapps/maker/model-driven-apps/command-designer-overview

Hope it helps..

Advertisements

Set Auto Number field value conditionally in Dynamics 365 / Dataverse


Recently we had a requirement to use auto numbers for lead records.

However, based on where the lead records are being created from, we wanted to specify a different prefix to it.

For leads created manually, the format should be prefixed “L” followed by “– “and then 10 digit sequence number.

L-{SEQNUM:10}

And if created through API the prefix should be B.

B-{SEQNUM:10}

To achieve this, we can define an auto-number field with the following format.


Next, we can have a bool field (default – false) in the lead table, to identify if it is being created from the API, which we can set while creating the lead record through API.

And a Pre Create Plugin on Lead to check the value of that field.

If it is set (true), that we can replace the Prefix from L to B in the auto-number field within the context.

In the Pre Create plugin, we get the next sequence in the auto-number field, so simply replacing/setting the value of the auto numbering field did the trick.

Lead created through Web Application –

Lead created through API –

Here uniqueness was more important than the next sequence of the lead record so this solution worked.

Also check –

https://jonasr.app/2020/03/anm-unique-seq/

https://nishantrana.me/2021/11/09/few-key-points-auto-number-field-in-dataverse-dynamics-365-ce-crm/

Hope it helps..

Advertisements

Lookup Behavior – Minimum character to trigger search and delay between trigger – Dynamics 365


Within Power Platform Admin Center – (https://admin.powerplatform.microsoft.com/)  through Environments >> [Name] >> Settings >> Behavior >> Lookup Behavior settings we can control the minimum number of characters entered before triggering the search in the and delay before the search is triggered for the lookups.

  • Minimum number of characters to trigger typeahead search – Default (2)
  • Delay between character inputs that will trigger a search – Default (250ms)

Here we have updated the value to 5 and 5000 respectively for our testing.

The result –

Lookup Behaviour

After 5 characters are entered, it waits for 5 seconds before searching (loading..)

Also check –

https://nishantrana.me/2021/06/22/advanced-lookup-in-model-driven-power-apps-dynamics-365/

https://docs.microsoft.com/en-us/power-platform/admin/settings-behavior

Hope it helps ..

Advertisements

Fixed – You do not have a license to use Microsoft Dynamics 365


Recently we started getting the below error  suddenly in one of our environments for all the users.

“You need a Microsoft Dynamics 365 license to continue. You do not have a license to use Microsoft Dynamics 365. Contact your Office 365 administrator to assign a Microsoft Dynamics 365 license to you.”

The users had the required CRM licenses and this error was only coming for the case entity.

Eventually, we realized that a Plugin / Workflow was running under the context (owner for Workflow) of a user who had recently left the organization and had his account disabled inside CRM.

Updating the context and owner of the workflow to run under the Service Account (with appropriate roles) fixed the issue.

Hope it helps..