Recently while trying to register the plugin, we got the below error Microsoft.Crm.CrmException: Plug-in assembly fullnames must be unique (ignoring the version build and revision number). —> Microsoft.Crm.CrmException: Plug-in assembly fullnames must be unique (ignoring the version build and revision number). It was because we were trying to register the assembly which was already…
Continue Reading Nishant Rana’s Article on their blog
Fixed – Plug-in assembly fullnames must be unique (ignoring the version build and revision number) – Dynamics 365 / Dataverse
Recently while trying to register the plugin, we got the below error Microsoft.Crm.CrmException: Plug-in assembly fullnames must be unique (ignoring the version build and revision number). —> Microsoft.Crm.CrmException: Plug-in assembly fullnames must be unique (ignoring the version build and revision number). It was because we were trying to register the assembly which was already registered…
Blog Syndicated with Nishant Rana’s Permission
More About This Author
Array
Dyn365CE3 September 2024Fixed – “The relative url contains invalid characters. Please use a different name. Valid relative url names cannot ends with the following strings: .aspx, .ashx, .asmx, .svc , cannot begin or end with a dot, cannot contain consecutive dots and cannot contain any of the following characters: ~ ” # % & * : ? / \ { | }. “ error while creating SharePoint Document Location – Dynamics 365 / Dataverse
Dyn365CE2 September 2024Data Migration of Quote and Quote Product – few key points (Dataverse/Dynamics 365/ SSIS)
Dyn365CE28 August 2024Recent and Pinned options are available now for multi-session app’s sitemap (e.g. Customer Service Workspace)
Dyn365CE28 August 2024Select record quickly inside Lookup control – Model-driven app /Dynamics 365
