Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
While importing the solution in my production environment I am getting the following error.
A managed solution cannot overwrite the AttributeMap component with Id=7db12511-860e-e411-a4c2-d89d67658224 which has an unmanaged base instance. The most likely scenario for this error is that an unmanaged solution has installed a new unmanaged AttributeMap component on the target system, and now a managed solution from the same publisher is trying to install that same AttributeMap component as managed. This will cause an invalid layering of solutions on the target system and is not allowed.
As per the error description I understand that the problem with unmanaged solution import. But in production environment I didn't installed any unmanaged solution. What could be the reason?
As far as I could understand the problem was with the managed solution you are trying to install.
You already have the required field on your Solution but as unmanaged and now you are trying to re-install it as managed.
You will need to find what component is causing this error, and try to re-import the solution without It.
Good Luck :)
This mean that you have a directly custom for AttributeMap on your production environment.. And your managed solution also have that custom as well, so it will break your importing solution..
because your customization on your production environment considered as unmanaged custom / unmanaged AttributeMap..
Could you please download the import log and see where what entity/attribute that make import process failed? After you got it, you should delete your unmanaged AttributeMap on production environment and try to import again.. Don't forget to backup your database first..
Hope its help..
I didn't change anything in the Production environment. Before also I imported managed solution only. So how this AttributeMap became unmanaged.
Could you please download the import log first and check what entity/attribute that occur the error? After you got it, you can start to analyze all the AttributeMaps inside that entity and make sure is there any customization on it or not..
Because i just got that problem also last week and solve it with this way..
PS: AttributeMap is different with Attribute..
I investigated on this. The particular attributemap is belongs to OpportunityProduct - QuoteProduct. As we don't have direct approach to map fields between those 2 entities I used the following link for mapping.
If we create mapping by using the above link will it became unmanaged even I exported the solution as Managed?
No.. I mean if you are doing customization on your production environment, that customization will considered as unmanaged customization.. but if you export it as managed, that customization will become managed for sure..
the problem is, if you have the same customization also on your development environment and export solution as managed and then try to import that solution into your production environment, it will failed.. because the system will try to overwrite unmanaged customization on your production environment with managed solution from your development environment..
About your case, i am not sure what the link did, because it refer to old CRM version..
if you change in the production environment, you should undo/remove this changes.. but since you said that you didn't change anything in the Production environment, its a different case.. i think you should ask for Microsoft support..
I hope you will get the answer soon..
Business Applications communities