Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I'm getting solution import errors on missing fields. But it is not an actual field, see below. the field name is dw_cashdiscount. The complaint is dw_cashdiscountname. This is a hidden field. I can't figure out how to trigger the solution to pick them up. I've included metadata.
1. Have you included both lookup field and N-1 relationship in your solution?
2. Extract the solution file and check solution.xml if this lookupname field dependency is stated.
3. Try to deploy solution with all the dependent components added.
Surprisingly, I noticed the button -- not on the Account Entity in the solution tree but -- on the Account member of the solution components that says to add all requirements. Mashing it cleared the problem.
Good to hear that.
Please mark the post as Suggested Answer if it has helped to resolve your problem.
Business Applications communities