Unanswered

Remove object in managed solution - Error during deployment

(0) Share

Report

Posted on by ryjan

Hi all,

I am trying to remove a Bot that I no longer need. I have removed it from the unmanaged solution on my DEV environment and prepared a new managed version. However, there is an error about dependencies during import into the UAT environment.

Details: This is the managed solution, consisting of 1 Chatbot with components, 1 Table, 3 Flows and 1 Connection reference.

None of this is needed at all.

First, I tried to delete the solution from the environment. The environment is managed. This is not possible due to dependencies.

Second, I have removed all the components, which are mutually dependent, and created a new version of the solution. The solution is now empty.

I have tried to import this new version using Upgrade option and expected all the components to be deleted.

But the import ended with error: Solution "XXX" failed to import: Solution Upgrade action failed after import as holding. InnerException is: Solution dependencies exist, cannot uninstall. DependencyCount : 325

And each component was listed as dependent....... But there is no dependency on any object which is outside the solution. I just need to remove it all at once.

Any advice on how to proceed?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (7)

Answers (1)

Parvez Ghumra 1,579 Moderator on at

Like (0)

Report

@ryjan Go into the default solution in the target environment, find the component you wish to delete (in your case, the Chatbot, click on it's associated elipses and click 'View Dependencies' in the context menu. This will give you a list of all components that depend upon the Chatbot. You will need to resolve all these dependencies before the Chatbot can be deleted. This may include managed components or unmanaged customisations. If you can share the details of these dependencies, I can try to advise further.

Was this reply helpful? Yes No
ryjan 45 on at

Like (0)

Report

Hi @parvezghumra
There are two unmanaged solutions in the target environment:
I found my chatbot in the Standardlösung / Defaultsolution.
BUT: all of the dependencies listed there are the Chatbot components of the Chatbot in the same solution.
How exactly they shall be resolved?

Was this reply helpful? Yes No
Parvez Ghumra 1,579 Moderator on at

Like (0)

Report

@ryjan Did you totally delete the chatbot from the source (dev) environment or just remove it from the solution?

Was this reply helpful? Yes No
ryjan 45 on at

Like (0)

Report

@parvezghumra I am afraid I have deleted it from the environment ☹️
Anyway, I have investigated a little bit in the classic view and I have found that some of the processes are required by some objects which are in solution layers of another solution:
This is the first target environment (UAT)
If I go into one detail, I see in the dependency detail (this was not visible in Power Platform View)
Unfortunately, I cannot access the details of the requiring components.
Do you have any idea how to identify the requiring component by their GUID?

Was this reply helpful? Yes No
ryjan 45 on at

Like (0)

Report

Hi @parvezghumra
In total, there are two objects in my solution, each of which has 6 dependent objects in another solution.
I just have IDs of these objects of type botcomponent_workflow
I have reviewed everything in this another solution but was not able to find any of these objects.
Any idea how to identify these 12 object in Dataverse so that I am able to resolve the dependency?

Was this reply helpful? Yes No
Verified answer

Parvez Ghumra 1,579 Moderator on at

Like (0)

Report

@ryjan As far as I can tell botcomponent_workflow is a system table and it's name suggests it's related to Power Virtual Agents. When I look at the default solution in my environment in the classic experience, I can see this N:N relationship called "botcomponent_workflow" under the "Chatbot subcomponent" table.

Also visible in the maker portal

Unfortunately, I don't know enough about Power Virtual Agents/Copilot Studio/Chatbots to be able to help much further. You might get more help in the Power Virtual Agents/Copilot Studio/Chatbot community forums? Failing that, you might need to raise a support request with Microsoft.

Was this reply helpful? Yes No
ryjan 45 on at

Like (0)

Report

Hi @parvezghumra many thanks, now I see that botcomponent_workflow is not an entity, but a relationship.
I can see the exact dependencies when reviewing the records and I can fix them. 👍

Was this reply helpful? Yes No