How do I remove a relationship dependency from another solution?

(0) Share

Report

Posted on by rmorris

Hello -

I am running into an issue with a new custom entity and its dependencies. We are currently creating a set of custom entities/workflows/business rules/etc to replace an outdated piece of software our company using. We use dev/test/prod environments and to date everything has been in one main custom solution (not the default solution). We do use the occasional patch for a quick break/fix but when we update test & prod we export the whole solution as managed into our other environments. This has worked fine for us until now.

With the new customization we didn't want them to be public until tested and approved by the users. So this was set up in its own unmanaged solution on our dev environment. The idea being that we could contain the customization separately and still push out the main solution with out having to release them out to the organization too.

Well the first first export from our main solution showed dependencies to the new entities we created in the other solution. I am thinking this is because of the relationships. The new custom entities require a relationship to the Account, Contacts, and a couple of our other custom entities.

Unfortunately I can't find out how to remove the relationship from our main solution to allow it to export/import without issue.

Is what we are trying to do possible?

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

ScottDurow 21 on at

Like (0)

Report

It sounds like you need to remove the account from your main solution and then add it back but only include the bits that you need.

Was this reply helpful? Yes No
ScottDurow 21 on at

Like (1)

Report

It is notoriously tricky to do what you want because workflows will create dependencies on fields even if you don’t use them.

Was this reply helpful? Yes No
rmorris on at

Like (0)

Report

That is what we are finding out now. We removed the lookup fields in the new customization and then we could export/import our main solution since there were no more relationship dependencies. Kind of depressing since I really want to find a way to break up our solutions into smaller, manageable chunks.

Was this reply helpful? Yes No
Jonas Vachal on at

Like (0)

Report

I'm reviving this because I'm experiencing just this behavior.

I have a "core" solution that contains a set of core custom entities as well as modifications to the standard entities.

I have the first of many smaller solutions that create relationships against entities in our core solution and I'm not getting import errors when updating our core managed solution because of missing dependencies created in the solution by these smaller solutions.

Did you find a solution for this or is it just not currently possible?

Was this reply helpful? Yes No