Personalized Community is here!
Quickly find the content you seek
Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
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 TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
'EntityKey' metadata entity doesn't contain metadata attribute with Name = 'issynchronous'.
Getting this error while importing solution. Can anyone point out some possible reason for this
Could you please share more details, log file, screenshot, version nuber of source and target environment.?
This error is from log file only Item type was solution and this was error for solution. Target version was 188.8.131.52 and Source 184.108.40.206
Me too, today I export solution and get the error: 'EntityKey' metadata entity doesn't contain metadata attribute with Name = 'issynchronous'
Download import log & see the components in the list for extra clue. Definitely something messed in workflow or something, could be an upgrade issue.
Is this happening for every single solution or something in particular? Can you remove components one by one & figure out the troublemaker?
If nothing works, MS support ticket is the only choice.
If it is happening for multiple instances then must be a bug which should be fixed in the future updates (If MS is aware about it). You could break the solution into smaller components to identify the for which entity/ component its failing. Once found you can remove that fromyour solution if feasible. Otherwise, its best to contact Microsoft.
Hope this helps.
I try to create a solution with only one entity that I know the error. But the process export throw the same exception.
It is worth to contact Microsoft on this issue. As mentioned above, this seems like a bug.
1. Create a Key attribute (e.g. new_mykey) for any entity in the target system >> this will fix the 'EntityKey' metatdata
2. Import solution (should work without any error)
3. Delete the Key attribute created in step 1
Delete the alternate key worked now.
Business Applications communities