Microsoft Dynamics 365 | Integration, Dataverse...

Removing dependencies

(0) Share

Report

Posted on by Muhammad Anas Naeemi

386

Hello everyone,

I exported a solution from one tenant and was importing it into another. During the import, dependencies issue occurred. I resolved many of the dependencies but stuck in the ones mentioned below with Type Column and View. Kindly guide how can I remove these?

All responses (3)

Answers (0)

Suggested answer

Eiken on at

Like (0)

Report

RE: Removing dependencies

Hi,

Did my answer help you ?

If yes, please don't forget to click Yes under "Did this answer your question?" to close this thread.
Suggested answer

DAnny3211 9,278 Moderator on at

Like (0)

Report

RE: Removing dependencies

hi

when importing a solution into a different Dynamics 365 tenant, it's not uncommon to encounter dependencies issues. In your case, you mentioned that you are stuck on dependencies related to Type Column and View. Here are some steps you can take to resolve these issues:

Check the solution components: The first step is to identify which solution components are causing the dependencies issues. You can do this by reviewing the error message you received during the import process. Look for the components that are listed as missing dependencies or unresolved dependencies.

Export the dependent components: Once you have identified the missing dependencies, you will need to export the dependent components from the source tenant. In this case, you need to export the Type Column and View components.

Import the dependent components: After you have exported the dependent components from the source tenant, you can import them into the target tenant. This will resolve the dependencies issues related to Type Column and View.

Re-import the solution: Once you have resolved the dependencies issues, you can re-import the solution into the target tenant. This time, the import process should complete successfully without any errors related to Type Column or View.

If you continue to encounter dependencies issues after following these steps, you may need to repeat the process for other missing dependencies until all dependencies are resolved. It's also a good idea to test the imported solution thoroughly to ensure that it works as expected in the new tenant.

DAniele
Suggested answer

Eiken on at

Like (0)

Report

RE: Removing dependencies

Hi,
This is caused by the presence of subgrid of views from other tables in the form.

For example, I try to reproduce your situation and create test_table and test_parent_table.

There is a subgrid showing the view of test_parent_table in the form of test_table.

Then I export and import the solution, the same error occurs.

Then I remove the segment in the form of test_table.

I recommend you to remove it in classic interface.

Now the missing dependence error disappeared.