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=18.104.22.168, 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.
If you have ever worked in Dynamics 365 implementation then it is almost certain that you must have played around with ribbons. And more often than not you must have faced scenario where you have multiple enable and display rules on the form and not sure why the ribbon button is showing up on the form when it is supposed not to show up or vice versa.
And what we do to resolve it. Well, we play around with the ribbon customizations which takes much more time than other customizations in Dynamics 365. And if it is some custom rule, we would attach debuggers to our custom code and debug and find what is going wrong.
What if I tell you that Microsoft just released something which shall help you identify which of your ribbon rule is evaluating to what in a matter of few mins so that you can…
In this post I am going to explain how did I solved the performance issue while migrating activities using SSIS packages. My approach to migrate the data is, export the CRM data to Staging DB by using “Data Export” services and then to CRM by using SSIS packages. We all know that we have to migrate the party list (from,to,cc,bcc etc.,) data as part of activities migration and we need to write either SQL functions / script component to migrate party list data. I opted for SQL functions and I used those functions in SQL view. For ex, in email view I have to call 4 functions for each record to transform the data in party list fields (from, to, cc, bcc). So it leads to huge performance issue while fetching the data from staging table.
After a bit of research, I realised that I don’t have index for my intermediate tables. So I immediately created the following indexes.
Index for “activityid” and “participationtype” fields on “activityparty” table
Index for “activityid” on “email” table
and here is my SQL Function
CREATE function [dbo].[GetPartyListForEmail] (@activityid uniqueidentifier, @partyType int)
DECLARE @partyList nvarchar(max);
DECLARE @partyid as uniqueidentifier;
DECLARE @logicalname as nvarchar(100);
DECLARE @getPartyList nvarchar(max);
DECLARE db_cursor CURSOR FOR SELECT ap.PartyId,ap.partyid_entitytype
FROM email em
LEFT JOIN activityparty ap ON ap.ActivityId = em.ActivityId
WHERE ap.ParticipationTypeMask = @partyType AND em.ActivityId = @activityid;
FETCH NEXT FROM db_cursor INTO @partyid, @logicalname
WHILE @@FETCH_STATUS = 0
IF @logicalname = 'systemuser'
SET @partyid = (SELECT TargetUserId FROM mapping_systemuser WHERE SourceUserId = @partyid)
IF @partyid IS NOT NULL
SET @partyList = Concat(@partyList, @logicalname);
SET @partyList = Concat(@partyList, ':');
SET @partyList = Concat(@partyList, @partyid);
SET @partyList = Concat(@partyList, ';');
FETCH NEXT FROM db_cursor INTO @partyid, @logicalname
IF (LEN(@partyList)) > 0
SET @partyList= left (@partyList, len(@partyList)-1)
After adding the indexes, I experienced huge improvement and processed 230k records in 2 hours.
I used “ReviseQuoteRequest” SDK method in one of the plugin to revise the quote. When you revise a quote from UI, first it will close the existing quote and then create a revised version of this quote. So I expected that “ReviseQuoteRequest” also do the same, but I got the “The quote cannot be revised because it is not in closed state” error when I am using the SDK method. After a bit of research, I understood that we have to Close the quote before revise it. So I closed the quote by using “CloseQuoteRequest” and then “ReviseQuoteRequest” which solved my issue. But my suggestion that SDK method should handle the close quote request also internally. Please let me know your thoughts on it.