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)
