Missing Dependencies during Solution Import - referencing to the New Table to Be Imported

(0) Share

Report

Posted on by Omardith20

Hello,

Anyone experiencing issue with importing a solution where there is a new Table created.

Issue:
Created a New Table in Environment 1 and then included it in the solution, tried to import it to Environment 2, but dependency error comes out referring to the new Table.

I already added all required objects in it.

I am trying to import the solution as unmanaged to another DEV environment.

The Email Notification Template is actually included in that solution as I want to import this to another DEV environment but it seems it is looking by the import process.

Thank you.

Categories:

General Questions

All responses (8)

Answers (0)

Suggested answer

Euria 8 on at

Like (0)

Report

Missing Dependencies during Solution Import - referencing to the New Table to Be Imported

I have same problem with the solution have custom tables in dev_environment. And thank to the finding of Sermakel with the "Customized" value as "No" for the issue table. He brought me some ideas, so I came back the Dataverse table try to modified it (update the form and view or change the properties of table) my purpose is to change that value to "Yes" as normal table and then try again to deploy the solution.

And, it worked for my case.

Hope it can help other, too ^^
Suggested answer

sermajkel 5 on at

Like (2)

Report

Missing Dependencies during Solution Import - referencing to the New Table to Be Imported

I found quite interesting dependency:
on screen below, tables in red square causing deploy issue - missing dependencies. If table from green square added to solution, it is deploying without any issue... the only diffirence is that tables in red square are not customized instead of table from green square which is. Any clue?
sermajkel 5 on at

Like (0)

Report

Missing Dependencies during Solution Import - referencing to the New Table to Be Imported

I have the same issue. Table exist in source solution, but when exporting to prod (eithin pipeline) it throws missing reference error during soluton validation. It's very frustrating. When table removed from solution deploy process run without any issue. Ewenv if I create completly new table (since scratch) I have the same issue.
Suggested answer

ankit_singhal 329 on at

Like (0)

Report

Missing Dependencies during Solution Import - referencing to the New Table to Be Imported

Can you try to apply same steps in other environment once and check if you are facing same issue or not. If not then there is some issue with environment. I think MS Is best for this issue

Note: Please mark verified, if it is helpful for you
Omardith20 43 on at

Like (0)

Report

Missing Dependencies during Solution Import - referencing to the New Table to Be Imported

Yes, Ill be raising a ticket, but I just noticed that this dependency error is also occurring when I created another new dataverse table and tried to import the solution to another environment.
Suggested answer

ankit_singhal 329 on at

Like (0)

Report

Missing Dependencies during Solution Import - referencing to the New Table to Be Imported

Yes it works but not feasible. if those are MS component then you can raise ticket with MS. Sometimes they deployed these type of things in patch

Note: Please Mark verified, if it is useful for you
Suggested answer

Omardith20 43 on at

Like (0)

Report

Missing Dependencies during Solution Import - referencing to the New Table to Be Imported

Thanks @ankit_singhal! I actually tried. The missing components that the import process is looking is the columns itself, those columns are actually included in the solution.

As a work around - what I have done is to modify the solution.xml file and remove the dependency tagging inside and re-zipped it back. It works.
ankit_singhal 329 on at

Like (0)

Report

Missing Dependencies during Solution Import - referencing to the New Table to Be Imported

As per the error few components are missing related to email template in your solution. You need to add those or you can check the dependency on your table and if those are not needed then remove manually.

Note: Please mark verified, if it is useful for you