Importing Solution error

[bettc]

Hey All,

I have 2 solutions in 1 environment. both have lookup fields to the system User table.

I cannot import either solution to another environment as they both state there are missing dependencies.

Is this basically saying dont use solutions at all?  how can a lookup field to the User table from another solution be a dependency?  This would mean that you can only 1 solution per environment?

I have tried exporting both managed and unmanaged, i have published, checked dependencies (none)

any help would be appreciated

[ChrisPiasecki]

Hi @bettc,

You have to take care to not create circular dependencies (Sol A has dependency on a component introduced in Sol B and Sol B has a dependency on component introduced in Sol A).

Is there a specific reason you have 2 separate solutions that are customizing the same components? Solution segmentation introduces additional complexity into application lifecycle management, so you should be sure that you have a specific reason or benefit for doing so to make the trade off worth it.

If you are going to segment solutions, each unmanaged solution should have its own separate environment for development, and other dependant solutions needed should be imported into the environment as managed. That way you can detect these types of circular dependencies sooner and adjust.

More information is available here. 

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

[bettc]

I'm not sure why you think I'm creating a component customization?

> Solution A has a lookup to the User table

> Solution B has a lookup to the User table

The User table is the system generated User table, I have not altered it in any way shape or form i am merely Looking it up on another table.

Is this incorrect? i would have thought system tables could be referenced in many solutions?

[ChrisPiasecki]

Hi @bettc,

It's likely not the User table that is the issue, every environment will have that table so it wouldn't be missing anything from it that would prevent the solution import. What else do you have in the solution that the other solution may be depending on? You mention you added a Lookup to the User table. Is this a custom table you created the user Lookup for? Is this same table also in the other solution?

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

[BhartenduP]

Hello @bettc  , The error messages regarding dependencies are commonly observed when using the solutions infrastructure. I would request you to please share the error message you are receiving. Once you locate the error message you can check which components is the dependency being reported - https://docs.microsoft.com/en-us/powerapps/maker/data-platform/view-component-dependencies Then you can check if these components are included in your solution . If not you will need to add these components . https://support.microsoft.com/en-us/topic/solution-install-fails-due-to-dependencies-that-do-not-exi...

Please mark my answer as verified if you found it helpful.

Please let me know if you have any other questions around the above.

Bhartendu Pandey

Support Engineer - Customer Engagement- Dynamics CRM/PowerApps/Power Automate

Microsoft

[bettc]

Here is the detailed error message when importing one of the solutions.  Each one of those listed dependencies is a Table column I created in another solution that has a "Lookup" to the User table.  

Any thoughts?  Am I reading this wrong?

For example the first one listed "Case" is a table that has a Lookup field to the User table from another Solution.  I am not using any of the tables, columns etc from that other solution.  Case has nothing to do with the Solution that i am trying to import nor does it reference any of the tables, components or otherwise to do with Case.

<MissingDependencies>

    <MissingDependency>

        <Required type=\"1\" schemaName=\"ip_case\" displayName=\"Case\" solution=\"Active\" />

        <Dependent type=\"1\" schemaName=\"systemuser\" displayName=\"User\" />

    </MissingDependency>

    <MissingDependency>

        <Required type=\"1\" schemaName=\"ip_casemetadata\" displayName=\"CaseMetadata\" solution=\"Active\" />

        <Dependent type=\"1\" schemaName=\"systemuser\" displayName=\"User\" />

    </MissingDependency>

    <MissingDependency>

        <Required type=\"1\" schemaName=\"ip_chat\" displayName=\"Chat\" solution=\"Active\" />

        <Dependent type=\"1\" schemaName=\"systemuser\" displayName=\"User\" />

    </MissingDependency>

    <MissingDependency>

        <Required type=\"1\" schemaName=\"ip_division\" displayName=\"Division\" solution=\"Active\" />

        <Dependent type=\"1\" schemaName=\"systemuser\" displayName=\"User\" />

    </MissingDependency>

    <MissingDependency>

        <Required type=\"1\" schemaName=\"ip_userlogin\" displayName=\"UserLogin\" solution=\"Active\" />

        <Dependent type=\"1\" schemaName=\"systemuser\" displayName=\"User\" />

    </MissingDependency>

    <MissingDependency>

        <Required type=\"1\" schemaName=\"ip_userrole\" displayName=\"UserRole\" solution=\"Active\" />

        <Dependent type=\"1\" schemaName=\"systemuser\" displayName=\"User\" />

    </MissingDependency>

    <MissingDependency>

        <Required type=\"1\" schemaName=\"ip_workflowstep\" displayName=\"WorkflowStep\" solution=\"Active\" />

        <Dependent type=\"1\" schemaName=\"systemuser\" displayName=\"User\" />

    </MissingDependency>

</MissingDependencies>

[bettc]

Solution 1 - Timesheets (prefix ts) this is the one I'm trying to import

Has tables related to timesheets and a few of those have lookups to the User table.

Solution 2 - Investment Portal (prefix ip)

has the Case table, which has a lookup to the User table.

Im seeing references to all the ip tables that have a lookup to the User table in the error message listed above. I'm not sure why that is

> Timesheets dont use the Case tables period. 

> The components I use in my solutions dont references data sources, only collections - so it cant be there

> The tables from one solution do not appear in the other solution, except for the System table "User" (un touched)

> the timesheet solution i am trying to import doesnt have any Flows, only 2 power apps with no references to those tables from ip

[bettc]

@ChrisPiasecki  I have 2 separate custom Tables that I created, 1 in each solution that have a Lookup field to the User table called ip_UserLogin and ts_UserLogin.  The solutions are not sharing any Tables that I have created.

[bettc]

I've just been informed by Microsoft support that this is how Dataverse and Solutions work.  Basically you have to included all tables in all of your solutions that reference the User table.

Meaning you pretty much cant use Solutions or reference similar tables in the same Environment.  We are bout to build 10 Power Apps which each need a Solution. This would be an absolute nightmare to have so many tables in each solution that are not being used.

I guess I  have to build a copy of the User table in each solution.  Is nobody else having these issues?

This seems totally against the whole shared data principles and ALM that Solutions preach?  Am I missing something?

It is totally insane to not be able to build a table with a Lookup to the inbuilt User table because it would have to appear in every solution in that environment, how would you know which solution owns or administers the table? 

I now will have to copy the users details in each solution meaning they can get out of date/sync.

[dpoggemann]

Hi @bettc

I think the issue here might be you are building both solutions from the starting same Sandbox environment.  You have modified the User entity in your Investment Portal solution to add a number of fields including (ip_case, ip_casemetadata, ip_chat, etc.) so your Investment Portal has the User entity as a component of the solution with these fields in the Sandbox Environment.

If you had a separate sandbox environment (as if you were a vendor that was starting with the Core entities in the dataverse) then you could create your Timesheet solution there an there would not be any Investment Portal fields, forms, views, etc. that have updated the User entity like you are having an issue with here.  

Is it possible to start with another Sandbox and build your Timesheet solution from there?  

Also if your Timesheet solution has not modified the User entity at all and only has a lookup to that entity I would not expect the dependency issue, especially if you do not include related entities in your solution.  If you have the User entity in your Timesheet solution you will have the errors if the Investment Portal solution is not installed first because there are ip fields on the User entity.  Same as the reverse if you have ts fields on the User entity, you will hit this issue if you are starting from the same Sandbox environment...

Hope this helps in some way.  Please accept if answers your question or Like if helps in some way.

Thanks,

Drew