Unanswered

Using Standard Tables (User) across multiple Managed Solutions

(0) Share

Report

Posted on by 365-Assist

2,324 Moderator

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?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Verified answer

Ram Prakash Duraisamy 5,593 Super User 2025 Season 2 on at

Like (2)

Report

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.retrievedependenciesfordeleterequest?view=dynamics-general-ce-9

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

Was this reply helpful? Yes No
365-Assist 2,324 Moderator on at

Like (0)

Report

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

Was this reply helpful? Yes No
CU27120916-0 2 on at

Like (0)

Report

Hello, i have the same situation but with a cutom table not with a standart table. So, first option is not applicable for me and the second option causes self dependency. For example, i add the Order table to the solution without selecting some relationships but when i try to import this solution to the another environment it gives dependency error: Order table required by Order table.

How can i resolve this?

Was this reply helpful? Yes No