cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
365-Assist
Advocate IV
Advocate IV

Using Standard Tables (User) across multiple Managed Solutions

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?

1 ACCEPTED SOLUTION

Accepted Solutions
rampprakash
Community Champion
Community Champion

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

 

https://docs.microsoft.com/en-us/dotnet/api/microsoft.crm.sdk.messages.retrievedependenciesfordelete...

 

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

 

View solution in original post

2 REPLIES 2
rampprakash
Community Champion
Community Champion

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

 

https://docs.microsoft.com/en-us/dotnet/api/microsoft.crm.sdk.messages.retrievedependenciesfordelete...

 

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

 

View solution in original post

365-Assist
Advocate IV
Advocate IV

Thanks your option 1. REMOVE user table in Solution 1. Worked for me.

Helpful resources

Announcements
User Group Leader Meeting January 768x460.png

Calling all User Group Leaders!

Don't miss the User Group Leader meetings on January, 24th & 25th, 2022.

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

Users online (2,058)