We’d get this error if we are trying to import a solution whose upgrade solution is already there in the target system.
So, either we need to Clone the Solution to remove the upgraded solution or we need to delete the Upgrade Solution. Deleting the Upgrade solution will only delete the solution it will not delete the components as it will already be there in the main solution whose upgrade has been imported.
Hope it helps..
Dynamics 365 as a platform has so much to offer for your organization. Be it, best in class Talent management, Sales & Marketing, Customer Service management, Field Service, Project Service automation(PSA), Retail, Finance & Operations management, Microsoft Dynamics 365 offers purpose built apps for each of these areas for organizations of any size, ranging from 5 – 10 employees to large enterprise organizations with 10,000 + users.
Any Tier 1 cloud ERP in the market today will probably provide you pretty much the major functionalities, that you would expect for your organization. However, what sets Microsoft Dynamics 365 apart from the crowd, is the platform itself. Along with purpose built, best-of-breed apps and functionality for all areas of your businesses, you also get the tools, services, technology and the best of Microsoft cloud. A few to name are,
View original post 1,220 more words
We got this error while trying to import managed solution to our TEST environment.
The detail of the error message clearly tells the reason for the error.
The error was because that we had a similar a role with same name in our TEST environment, and in DEV we had renamed that existing role and had created a new role with similar name.
So, while trying to import the solution, CRM was getting confused as it was able to find the role with same name but different id.
To fix this either rename the Role in DEV and export and import it back or rename the role in TEST to and them import the same solution.
Hope it helps..
Awesome post on usage of Virtual Entities
Virtual entities is a powerful feature that can be used not only to bring data from external sources, but also from inside Dynamics CRM/Dynamics 365 Customer Engagement.
Jason Lattimer already has a post (https://jlattimer.blogspot.com.au/2017/12/creating-custom-virtual-entity-data.html) that goes through how to setup the custom datasource/data provider. So, go and read that first as it has all the screenshots and I would be duplicating the content, if I go through the steps again.
Gotcha 1:
There is a exception when you create the datasource.
You can simply ignore this and refresh the Plugin Registration tool.
Gotcha 2: If you don’t want the user the open up an individual record, you don’t have to implement Retrieve message. It is optional. Since, I just want a collated entity, I did not register any plugin for the Retrieve.
Gotcha 3: You have to open up the newly created Data Provider entity, and…
View original post 187 more words
While trying to install a managed solution we were getting the below error
As the error message suggests, at the same time we had the solution upgrade (Apply Solution Upgrade) going on in the same environment.
Installing the solution worked after the solution upgrade successfully completed.
At times we might face SQL Timeout issue while trying to upgrade solution if it contains large number of components in it.
Hope it helps..
To update or upsert a record inside CRM using Alternate Key in Dynamics 365 for Sales Connector we need to define Alternate Key Property of Microsoft Dynamics CRM advanced target properties.
Suppose we have the following alternate key defined in CRM
Here we need to use the Name attribute of the key as shown below
Hope it helps..
