You’re offline. This is a read only version of the page.
I have created a couple of Solutions in a Development environment. Both solutions have separate Model Driven apps that require the use of the Standard Dataverse Table - User.
I am ready to migrate one solution to a new Production environment but do not want to migrate the other Solution. When importing the Solution for the first time into the new Production Environment I am getting dependency errors on the User Table. This is because the User Table has dependencies based on relationships in both Solutions Apps.
However I want to bring across one of the Solutions without including all dependencies needed for the other Solution.
Is there a way to achieve this or have I designed the Solution\App wrong because I am sharing the same standard User table?
Thanks your option 1. REMOVE user table in Solution 1. Worked for me.
Hello @365-Assist,
As per the OOB Behaviour, with dependencies you cannot import solution from one environment to another, you can try either one for the Suggesstion below
1. REMOVE user table in Solution 1, if there is no Customization
2. If any Customization avaialble remove the User table and Add it back, which adding, only add the Customization needed like Fields, Forms,Business Rules or Relationship
3. If Both Not working, while importing solution it will Ask for Dependencies, just remove the Add or Remove the respective item reference to made it work
You can use Dependencies Class to retrieve too, please find the below link for your reference
As per OOB Behaviour there is no other way..
Please mark as Answer if it is helpful and provide Kudos
Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA
Blog : https://microsoftcrmtechie.blogspot.com
#1
WarrenBelz
791
Most Valuable Professional
#2
MS.Ragavendar
410
#3
mmbr1606
275
Super User 2025 Season 1
Share
Report
All responses (
Answers (
