Solutions and dependencies

(0) Share

Report

Posted on by DKasp

229

Hi community,

I've just started preparing the productive D365 instance we're going to use and I'm honestly baffled by the dependency and required components.

A 3rd party has provided us with a managed solution that was installed on our development server, but is currently still in the evaluation / setup phase. We do not want to deploy these components to the productive environment just yet. But when trying to export my unmanaged solution, I am being told by the export wizard that I have to include 4 entire entities from that 3rd party solution since they added fields to the account and contact entities - but we do not want these fields to be on the productive environment yet.

Q: What do I need to do to get my own solution to not require entire entities from that 3rd party solution?

After exporting the solution (with or without these 4 entities) I'm getting a ton of missing dependencies when trying to import the solution to our productive environment.

I can tell that a huge amount of the dependencies are from that 3rd party solution, which hopefully can be resolved by the question above. But I'm having trouble identifying the source of the other dependencies:

MicrosoftDynamics_EventManagement (1.4.1006.0)
ConnectedFieldService (1.0.18170.5)
IoTConnector (1.0.18266.4)
MicrosoftDynamics_Marketing (1.28.1004.0)

I'm guessing these last three belong to the MicrosoftDynamics_Marketing one, but for completeness sake:
MicrosoftDynamics_MktLeadGenLink (1.5.1.0)
MicrosoftDynamics_MktLeadManagement (1.26.1005.0)
MicrosoftDynamics_MktConsentManagement (1.26.1005.0)

I don't have anything matching these names available for installation in the Admin Center, the only major component I haven't yet installed from there is the Project Service Automation one.

Q: Where do I get the missing solutions from?

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (3)

Verified answer

gdas 50,091 Moderator on at

Like (0)

Report

RE: Solutions and dependencies

Hi ,

You are right there is no options for remove the entity.

To remove the fields from the solution you need to follow below steps -

1. Remove the Account Entity from the solution.

2. Add again the Account entity in the solution , by clicking add existing entity .

3. While adding the Account entity you will get the options to choose selected fields and all the component . So select all the component except the fields of third party (Exclude all third party component by going to each tab)

Once added the Account entity you can not see the third party solution fields in your solution.

Was this reply helpful? Yes No
DKasp 229 on at

Like (0)

Report

RE: Solutions and dependencies

I don't fully understand how you can do that, to be honest.

As an example I have customized the account and contact entities by adding fields as well as customizing the views and forms.

When it came to exporting, D365 told me I had to include certain 3rd party solution entities and components, so I let the system resolve these missing dependencies, which resulted in entire entities being added to my solution.

I've now removed the entities from my solution, but there are still fields part of my solution that belong to the 3rd party solution. But, unlike entities, there's no option to simply remove those fields from my solution, there's only the option to delete them - is that what you meant? Won't this affect the 3rd party solution, too?

(note: My solution is unmanaged, the 3rd party solution is managed)

Was this reply helpful? Yes No
Verified answer

gdas 50,091 Moderator on at

Like (0)

Report

RE: Solutions and dependencies

Yes you can remove those entities and also the fields from your solution. Make sure in that case you should remove all the forms , field dependencies , relationships if any to separate your solution component from third party solution.

Was this reply helpful? Yes No
DKasp 229 on at

Like (0)

Report

RE: Solutions and dependencies

Can I remove an entity from my solution but retain the Forms and Fields and Views I modified and/or created for that within my solution?

Was this reply helpful? Yes No
Verified answer

David Jennaway 14,065 on at

Like (0)

Report

RE: Solutions and dependencies

You should be careful to only include the subcomponents (assets) that you need in your solution, as this will minimise the dependencies. The most likely reason for CRM identifying the dependencies is if the new fields are on a form, and you have included that form in your solution.

Re the solutions, MicrosoftDynamics_EventManagement and MicrosoftDynamics_Marketing will be part of the Marketing app, while ConnectedFieldService and the IoTConnector are part of Field Service (or maybe Connected Field Service, if this is a separate app)

Was this reply helpful? Yes No