Override the default open behavior of data rows in an entity-bound grid

Hello there, fellow power platform customizers/developers! Have you tried to override the default open behavior in subgrid and failed?

 

What I’ve found in my research:

Documentation by Microsoft says: “You can now create a command definition for an entity with Mscrm.OpenRecordItem as the value of the Id attribute (<CommandDefinition> (RibbonDiffXml)), and define custom action for the command <Actions> (RibbonDiffXml). Customer Engagement will look for this command Id for an entity when you try to open a record from the entity-bound grid, and if present, will execute the custom action instead of opening the entity record (default behavior).”
IMPORTANT NOTE: This feature is supported only for Unified Interface.

Did this. No luck. What now? Google…

I found only one related article/discussion: https://community.dynamics.com/crm/f/117/t/254488

Where you can get more concrete visualization about how it should look like. But nobody has tried it on the new UUI.

 

So, I had this snippet:

This <RibbonDiffXml> element is in customization.xml for each Entity.

 

Although we followed every step of documentation, this wasn’t working.

I was stuck, because no one had the solution on the internet and that’s why I’m writing this blogpost, so that you don’t find yourself in similar situation.

 

Solution:

What documentation doesn’t say (written on 2018/12/04) is that you need to add another element to your customization.xml. You need to add <CustomActions>. So, the snippet should look like this:

 

Now import your solution and don’t forget to publish all customizations…

 

Happy PowerPlatforming!

Notes: Adding custom fields to entity maps between Quotes, Orders and Invoices (solution aware)

Finally, it’s the weekend and I have some time to focus on an issue which bothered our team for a few months. As always we wanted to do it the right way so it will be fast, reusable, continuous integration compatible and without spawning unnecessary workflows and plugin instances.

Continue reading “Notes: Adding custom fields to entity maps between Quotes, Orders and Invoices (solution aware)”

Assembly Caching Issue in Dynamics 365 V9 – Update Assembly Version of Custom Workflow Steps With PowerShell

As Alex blogged we are currently facing a caching bug of plugin assemblies in Dynamics 365 cloud instances (V9). You can do an in-place upgrade with Plugin Registration Tool without an exception now (see Unable to in-place update plugin in Dynamics 365 (with build or revision number changed)) but for some assemblies it just won’t propagate to your workflow definitions.

In the past we could fix it by clicking a save button in Properties tab of the assembly in Plugin Registration Tool but this does not work anymore in V9.

I have put together another workaround which is usable in release automation scenarios.

Continue reading “Assembly Caching Issue in Dynamics 365 V9 – Update Assembly Version of Custom Workflow Steps With PowerShell”

Unable to in-place update plugin in Dynamics 365 (with build or revision number changed)

UPDATE 19/9/18: It has been fixed in 9.0.2.5 version of Plugin Registration Tool https://www.nuget.org/packages/Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool/9.0.2.5

If you use 9.0 version of Plugin Registration Tool to update your assemblies in Dynamics 365 you may encounter the following exception:

Continue reading “Unable to in-place update plugin in Dynamics 365 (with build or revision number changed)”

Remove missing dependencies from solution XML with PowerShell

The import of the solution XYZ failed. The following components are missing in your system and are not included in the solution. Import the managed solutions that contain these components (Active) and then try importing this solution again.

If you ever run into this exception and there are all the components already present in the environment you just need to get rid of few lines in a solution definition in the ZIP file you are trying to import.

Do this only if you are absolutely sure that you know what you are doing.

Continue reading “Remove missing dependencies from solution XML with PowerShell”

Setting up ADFS with Azure AD as Dynamics 365 Identity Provider

In previous article, we have looked at the possibility to connect Dynamics 365 on-premise directly with Azure AD, which is on one hand really cool, on the other, it doesn’t provide all the features like mobile apps integration. In this article, we are going to explore a production ready solution by leveraging Active Directory Federation Service and Azure AD as a Claims Provider Trust.

Continue reading “Setting up ADFS with Azure AD as Dynamics 365 Identity Provider”

Dynamics 365 Unified User Interface: Direct View Links in SiteMap

You may have used direct links to specific view in the past but you don’t see these sub areas now in your UUI App.

You could have achieved this by using a special URL in the sitemap sub area with the view’s parameters and Dynamics managed to detect your intent when rendering the application navigation.

This is still working but the format has changed for UUI Apps.

Continue reading “Dynamics 365 Unified User Interface: Direct View Links in SiteMap”

Using Azure Active Directory for SSO with Dynamics 365 On-Premise

While Dynamics 365’s documentation is full of articles and tutorials about setting it up with Active Directory Federation Services, there is no mention of using Azure Active Directory for Single Sign On. Many replies in communities say that this is not possible, but today we are going to prove them wrong.

Continue reading “Using Azure Active Directory for SSO with Dynamics 365 On-Premise”

Dynamics 365 Reporting Extensions and SQL Server 2017 incompatibility

I came across a strange issue when trying to upgrade CRM deployment to Microsoft SQL Server 2017.

Important note: It is not listed as a supported version https://technet.microsoft.com/en-us/library/hh699754.aspx

And here is probably why.

Continue reading “Dynamics 365 Reporting Extensions and SQL Server 2017 incompatibility”