You’re offline. This is a read only version of the page.
We have a list of things to do to create a new test environment in Dynamics 365 - we activate "Create a database for this environment" and install "Customer Service" + "Sales Enterprise" by default. Then we install our managed solutions. Normally we don't have issues with importing our solutions, but now a dependency is missing: the relation "contact_SharePointDocuments". Where did this relation come from? We currently have not configured anything with SharePoint on our Dynamics servers, so I think it's very strange that it is present in the dev-environment, but not in a new test environment. I've double checked that all solutions that are in the dev-environment are also present in the test environment.
Does anyone know where this relation does come from and how I can convince my new test environment to also generate it?
Hello krbromark,
I removed the references to these relations from the forms and then excluded them from the solution. I also switched on "document management" in the entity of the target system and switched it off again. Now, the relation is there in the dev and test environment, but not used. Also, it's not in the managed/unmanaged solution.
I'm not sure whether it would be a problem including the relation (and the corresponding entity) into my solution, but I don't want to have things in my solution I don't need. I also don't want a status of the test/prod environment where a missing dependency drives the next one working with this project crazy. So, I crated the relations by switching it on and off again.
IMHO, all tables/relations/fields should either be present after installing or be deployed via a managed solution - I don't understand why Microsoft generates such places for trouble by dynamically creating fields/relations "on the fly" when just clicking a checkbox without installing a corresponding solution.
All the best.
PS.: Don't be puzzled if my posts appear under two different accounts "Sven007" and "Sven Erik Matzen" - it's another thing I don't understand: why on earth do I need an account that is "member" and not "guest" to work with a clients PowerPlatform? I already have a guest account with my "real" AAD identity, but cannot use that to work as a PowerPlatform-Admin, so we needed to create 2nd in the tenant of my client ... but that's another story ;-).
I think I found out how the problem did come up: There is an option at the entity-level to "Enable SharePoint document management". Enable it and it will create two relations (and make the contact depend on that fields); disable it and ... nothing - the relations remain as unmanaged components on the entity contact ... and cause issues.
Thanks for the hints - I was sure that document management was not enabled, because we didn't even configure the SharePoint online so far. But someone of the development team must have switch it on at the entity level, has seen that it didn't work and then switched it off again, assuming that this will revert what he did by activating it.
It's funny how many surprises I get per week even after years of experience with Dynamics.
It gets even more strange: the production environment has this relation while it still shows the "Enable Sever-based SharePoint Integration" link under "Settings > Document Management". I think Microsoft really messed up that product. There are so many things that drive you crazy when working with it on the development side.
Yes, you are right, it looks like it has been activated but not configured.
Is there a way to disable it after it has been enabled? I think it's a really bad decision to simple generate unmanaged relations in an environment when activating something. Changes on the structure should always be done via solutions, so they are isolated from the intentional changes. I think I cannot include the relation to the solution, because it will have a different ID in every environment, and I cannot exclude it, because my solution does build on the contact entity, which now has a dependency on an unmanaged component.
Is it safe to simply delete that unwanted modification in the development environment or will that cause even more issues?
that kind of relationship usually appears after the sharepoint integration has been enabled, are you sure that the dev environment does not have it? did you checked the solution xml if contains that relationship?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (