Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Power Apps - Power Apps Pro Dev & ISV
Answered

Build solution wiith Custom Connector (pac solution pack or msbuild)

(0) ShareShare
ReportReport
Posted on by 11

I have a solution with a custom connector in my DEV environment. When I take the solution and put it in source control (git), I can't build/pack and deploy the solution anymore. 

Always give the following on build (or pack):

Following root components are not defined in customizations:
Type='Connector', Id (or schema name)='{c280222c-4add-4292-b590-df8f0d1b789e}'.

 

This is independent of the combination of export/extract/build/import. Used

* pac solution clone

* pac solution sync

* msbuild /t:rebuild /restore

* pac solution export + pac solution unpack

* pac solution pack

 

Nothing seems to work. Inspecting the solution and the source everything seems fine.

Solution.xml contains RootComponent for the connector. And there is a Connectors folder with all the files for the connector.

I thought I had everything working one day last week bij not hacking the name of the connector and leaving in the (stupid) '5F' in front of the name. But appearantly this wasn't the (only) problem, as today everything is broken again.

 

Any help please?

 

P.S. Is the pac cli open source on GitHub somewhere? Would be nice to see how things work. The docs aren't great. Or to figure out/fix when something isn't working.

We have our entire dev and build proces automated and this is all based on pac (and DevOps Build Tools). The tools aren't as stable as one would want, so currently the automation seems to take more time and trouble shooting, than the manual export/import of solutions.

  • Verified answer
    Arjan_M Profile Picture
    11 on at
    Re: Build solution wiith Custom Connector (pac solution pack or msbuild)

    After some tedious trail and error ... turns out that sometimes the OAS/Swagger content for the connector gets "corrupted". I can't see anything visibly wrong, but after creating a new definition file, and copy-pasting section by section (including build and deploy of the solution) the problem seems to have fixed itself.

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

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Congratulations to all our community participants!

Warren Belz – Community Spotlight

We are honored to recognize Warren Belz as our May 2025 Community…

Leaderboard > Power Apps - Power Apps Pro Dev & ISV

#1
WarrenBelz Profile Picture

WarrenBelz 109 Most Valuable Professional

#2
Michael E. Gernaey Profile Picture

Michael E. Gernaey 82 Super User 2025 Season 1

#3
mmbr1606 Profile Picture

mmbr1606 71 Super User 2025 Season 1

Overall leaderboard