Today while exploring the CRM, I found “status reason transitions” option of status reason field. This option is introduced many years back but I haven’t noticed. Status reason transitions are an optional additional level of filtering to define what the status reason value can be changed to for each status reason. That means it will restrict the users to select the status reason which is not valid based on current status reason. Follow the below steps to configure this in your environment.
Open the Default solution.
Navigate to the entity (Case for example).
Go to Fields and open “statuscode” field.
Click on the “Edit status reason transition” button on the top.
A window will open to configure the status reason transition . The Current Status Reasons are available on the left and for each of the Current Status Reason you can specify the available New Status Reasons.
Select “Enable Status Reason Transitions” check box and add the new status reasons based on your business need.
Save and publish the changes.
In the above example, one of the business scenario is, I will not allow the users to select “Problem Solved” status reason from “On Hold”. User has to change it to “In Progress” in order to move to any other status reason.
Like this you can configure all your scenarios based on your business needs. This can be configured on both System and Custom entities.
In one of my previous post, I explained about the navigation property naming issue when working with Lookup fields using the WebAPI endpoint in “CDS/CRM Connection Manager”. Recently, I got a mail from Kingsway Soft support team with a Hotfix to resolve this issue. I installed this Hotfix in my machine and ran a simple package successfully to update custom lookup (account) on Contact entity.
This Hotfix is part of the most recent official release (188.8.131.524). You can download this from the below link.
Today while updating one of my plugin assembly in plugin registration tool, I got the below error.
Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=184.108.40.206, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: PluginType not found in PluginAssembly which has a total of  plugin/workflow activity types.
Detail: <OrganizationServiceFault xmlns="http://schemas.microsoft.com/xrm/2011/Contracts" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<a:value i:type="b:string" xmlns:b="http://www.w3.org/2001/XMLSchema">Plugin/Microsoft.Crm.ObjectModel.PluginAssemblyService</a:value>
<a:value i:type="b:string" xmlns:b="http://www.w3.org/2001/XMLSchema">Microsoft.Crm.CrmException: PluginType not found in PluginAssembly which has a total of  plugin/workflow activity types. ---> Microsoft.Crm.CrmException: PluginType not found in PluginAssembly which has a total of  plugin/workflow activity types.
After a bit of research, I found that I forgot to change the “Copy Local” property to false of “Microsoft.Xrm.Sdk” and “Microsoft.Crm.Sdk.Proxy” dlls. In our case, we are using ILMerge to merge different dlls but these Microsoft dlls should not be part of the Merged dll. After setting the “Copy Local” property to “false”, Plugin assembly updated sucessfully.
Recently Microsoft have released quite a few updates to it’s client API and one such is the update to API for getting the currency name of the logged in user.
All this time, Microsoft had an API to get the transaction currency id of the logged in user using the API – . You needed to run a separate query to fetch the currency name based on currency id. However it is being deprecated now and now the replacement API is
This wonderful api returns the name of the currency as well as the id and entityType.
Nested Grids – as the name suggests is a grid-within-a-grid (or rather, Grid-ception!). Nested Grids will let you expand a sub-grid entry to look at another grid of the expanded record. This depends on how you configure it.
Be aware, Nested Grids work with Editable Grids and only for Tablet, Phones and Unified Interface. This is not available for the classic Web UI.
Configuring Nested Editable Grid
Here’s my entity structure – I have Account, having multiple Contacts and each Contact, having Opportunities under them. Like in the below diagram –
Now, I have a Contact grid on my Account form (just like we usually do).
I now will have to choose the grid to be a Editable Grid Control as follows. Also, click on the Nested grid view control as pointed
On clicking the Nested grid view pencil, the next dialog box will let you select what entity…
Power studio app (previously flow studio) is a great app for Flow makers and administrators. It is offering wide range of options to manage Flows as an administrator. You can use the following functionalities with this app.
Migrate and Deploy
Full Text Search
Export your data
How to use it?
Open this link and sign in with your CDS credentials.
You can see list of Flows with multiple operations like Export Excel, Flow Diagram, Sort, Filter and etc.,
Click on (…) next to any flow for more operations. You can see all operations that you can perform on each Flow in the below screen shot.
They are offering one month trail version, so I suggest everyone to subscribe for trail version and explore all the options. I like the Flow Diagram and Snapshots options the most.
While exploring the new features with 2020 Release wave 1, I found the advanced filtering option from Home Grid View. You can find this filter button before the search box on Home Grid View.
Advanced filter looks like below. I applied two more extra filters to the existing “My Active Accounts” view. You can add conditions from the related entity also. Click on “Apply” button to filter the records.
Here is the result after these conditions applied. You can remove the filters by clicking on the below highlighted button.
You can also create a personal view with these conditions from the ribbon button.