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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Build solution wiith C...
Power Apps
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.

I have the same question (0)
  • Verified answer
    Arjan_M Profile Picture
    11 on at

    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

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 305 Most Valuable Professional

#2
11manish Profile Picture

11manish 212

#3
Valantis Profile Picture

Valantis 167

Last 30 days Overall leaderboard