Breaking news from around the world
Get the Bing + MSN extension
Answer forum questions for a chance to win prizesProviding verified answers in the community not only helps your colleagues find solutions, it also earns community members badges and spots on the Top 10 Leaderboards. Starting this month, your verified answers can help you earn a chance to win monthly prizes.
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View 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 | Talent TechTalks | Upcoming TechTalks
I am running into a problem of trying to import a solution that I have exported from one Dynamics 365 (Customer Engagement) instance to another Dynamics 365 (Customer Engagement) instance. The problem is the system is complaining that the destination environment is missing components that are used as dependencies in the solution. To be more specific, those dependencies are related to components introduced by Dynamics 365 for Marketing which is installed in the source instance, but not in the destination instance.
Dynamics 365 instance A:
- Dynamics 365 for Marketing installed in this instance
- Solution exported from this instance
Dynamics 365 instance B:
- No Dynamics 365 for Marketing installed
- Want to import the solution exported from instance A into this instance. Solution import failed.
Does anyone know how I could resolve this? How can I get those missing dependencies into my target instance? The issue here is that I can only install the Dynamics 365 for Marketing app in one instance at a time under the same tenant. So for example, in order to apply Dynamics 365 for Marketing to instance B, I would need to uninstall the app from instance A first. If this is correct, I find this very problematic to manage solution changes and import.
Any help would be appreciated!
Are you using those dependant resources, or have they just been included in your solution as a result of 'including components' or 'including metadata'?
A) If you aren't using the dependant resources, simply remove them from your solution, Save, Publish and Import.
B) If you are using these dependant resources, you will need to get the marketing module into your target environment. That said, this module is generally default with relevant licenses, which it sounds like you have in your source. If for whatever reason this is available but not configured in your target, simply Add and Configure this module following the steps in this Microsoft article:
You'll need to head into D365 Admin Center and configure the module. The image below perfectly outlines this.
Let me know how this goes and if you need any further help!
Thank you for your response and inputs!
So in my current setup, I have Dynamics 365 for Marketing installed and configured for my Dynamics 365 Sandbox instance. It looks like in the admin centre I can only configure this Marketing app for one instance at a time, and therefore, how would I be able to set it up for my destination instance, which is my Production instance?
And if indeed the Marketing app can only be set up for one instance at a time, I find this very problematic because does this mean I would need to set it up in Sandbox for my testing, and then re-set it up in Production later each time?
Hi Again Eric,
Hmm, generally with a license, you will have access to a production instance and a sandbox instance.
Both of these instances are technically the same, so it isn't as though one should have the ability to configure Marketing and the other not.
Please can you confirm which license(s) you have?
If you also want to try in the meantime, creating another sandbox and trying to configure marketing in there, to check this isn't just a glitch with your production instance.
Thanks again for your quick response.
I have the Customer Engagement Plan license, which gives me access to Dynamics 365 for Marketing. The below image is what I see in the admin centre. From this it looks like I can only have the Marketing app point to one instance at a time - it's currently set up for Sandbox. That's the reason why I mentioned if I re-configure it for Production, then I would lose it for Sandbox. Am I understand this incorrectly?
It does look that way.
Did you check the list of dependencies to see if they were needed in your target instance?
Also, you could have a look at changing the organisation Marketing is pointing too, to your Production and just checking this does resolve the issue, before heading down this path too far.
Thanks again for your inputs!
I am able to remove most of the dependent components that I don't need from the solution I am trying to import to the target instance, but I am stuck with the following 2 dependencies, which I don't know how to remove from the solution. Would you know if there is a way I can remove them? These are introduced by the Dynamics 365 for Marketing app as you can see from the managed solution circled below, and I don't want to install these yet in the target environment.
If you find the above two dependencies in your source solution, then highlight each of them (one at a time), then select the 'Include Required Components' button, this should bring across the missing components into your solution.
You could also do this during export of your un-managed solution, seen at the stage below:
Business Applications communities