web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Copilot Studio - Bot Administration
Unanswered

ImportAsHolding failed with exception :The bot component cannot be deleted

(2) ShareShare
ReportReport
Posted on by 7
I am trying to deploy a solution, it gives the error

Failure details ImportAsHolding failed with exception :The bot(31da726f-2307-4eef-a436-ff1ba9f6096b) component cannot be deleted because it is referenced by 1 other components. For a list of referenced components, use the RetrieveDependenciesForDeleteRequest.
 
The component seems to be the "Copilot in Power Apps" component.
Categories:
I have the same question (1)
  • S-Venkadesh Profile Picture
    743 Moderator on at
    ImportAsHolding failed with exception :The bot component cannot be deleted
     
    It seems you're deploying on top of an existing solution.
    Are you attempting to exclude the bot during deployment?
    Is the target environment a managed solution?
    Check if there are any unmanaged layers in the target solution that might be preventing the component from being deleted.
     
    I hope this information helps! If it does, please consider giving a 👍.
    Best regards,
    S-Venkadesh
  • JW-12061016-0 Profile Picture
    7 on at
    ImportAsHolding failed with exception :The bot component cannot be deleted
    Hi @S-Venkadesh

    Thanks for your response.
     
    We are deploying a new version of the solution using pipelines. Single step upgrade approach. Target is managed solution. No unmanaged layers existing (checked with XrmToolbox).
     
    I noticed in the solution XML that there were quite some appelement tags referring to bots. One of these bots, is the bot in the destination environment, and no longer existing in the source environment. I was unable to remove these appelement using XML modification nor I saw any option in the Model-Driven App Editor to remove the references to these bots (appelemets?).

    Example appelement tag.

    <appelement uniquename="xxx_xxx__schemaname_cr926_bot672100">
    <iscustomizable>1</iscustomizable>
    <name>cr926_bot672100</name>
     
    What we then tried was creating a brand new model-driven app. This is not ideal but we want to get this fix over with. This new model-driven app does not have references any longer to these appelements so we assumed that this would solve the deployment.
     
    However, now we receive a total different error. Being:

    Import failed: {"statuscode":500,"statusdescription":"Internal Server Error","errors":[{"code":10000,"message":"The value passed for ConditionOperator.In is empty. Attribute Name: TeamId, Attribute Id: 5b31a87c-069a-4c96-9567-628e835ae10c"}]}

    We are a bit stuck now.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Chiara Carbone – Community Spotlight

We are honored to recognize Chiara Carbone as our Community Spotlight for November…

Leaderboard > Copilot Studio

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 479 Super User 2025 Season 2

#2
Romain The Low-Code Bearded Bear Profile Picture

Romain The Low-Code... 392 Super User 2025 Season 2

#3
DAnny3211 Profile Picture

DAnny3211 49

Last 30 days Overall leaderboard

Featured topics