cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Import Error with PCF Control "Cannot add a Root Component of type 66 because it is not in the target system."

I  have created few PCF controls, and i have created single solution zip file for all the controls by running below commands.

 

pac solution init --publisher-name DefaultPublisher21cdcsandbox --publisher-prefix cdc

pac solution add-reference --path F:\Controls\Controls\CustomerJourneyBoard

pac solution add-reference --path F:\Controls\Controls\StakeholderEngagement

pac solution add-reference --path F:\Controls\Controls\LeadBoard

msbuild /t:build /restore

 

Solution was build successfully and i have imported into my sandbox environment. Now i have few changes in one of my control CustomerJourneyBoard. So i have used pac pcf push command to do so. But i want to again built my complete solution again.

 

I have used below command to rebuild the solution in single zip file.

msbuild /t:rebuild

 

From the sandbox environment i have removed the reference of CustomerJourneyBoard and try to import the new solution but i am getting below error.

Cannot add a Root Component cdc_CustomerJourneyBoard.CustomerJourneyBoard of type 66 because it is not in the target system.

 

Earlier this used to work from me but not anymore.

 

Any idea anyone for this ?

8 REPLIES 8
v-xida-msft
Community Support
Community Support

Hi @Bhuvita ,

Have you commented out some nodes within your customization.xml file?

 

Based on the issue that you mentioned, I found that the user Stanley Lai has faced similar issue with you, please check the response within the following thread:

https://community.dynamics.com/crm/f/microsoft-dynamics-crm-forum/157591/solution-import-failure-mes...

 

Also please check and see if the following article would help in your scenario:

https://social.microsoft.com/Forums/en-US/fddff17f-1cca-4d33-a666-60c08ad76b0c/crm-2011-import-failu...

 

In order to this issue, please consider open your Component Control Solution file, and then find solution.xml file under the *.zip file. Then edit the solution.xml file, comment out the <RootComponent> node where type = 66 :

1.JPG

please use the following code to comment out the <RootComponent> node:

<RootComponents>
      <!-- <RootComponent type="66" schemaName="dev_SampleNamespace.TSIncrementControl" behavior="0" /> -->
</RootComponents>

then save your solution.xml file. After that, import your solution into your CDS Environment again, check if the issue is solved.

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

@v-xida-msft 

 

No i have not modified my customization.xml file.

 

I tried commenting out the 

 

<RootComponents>
<!--<RootComponent type="66" schemaName="cdc_CustomerJourneyBoard.CustomerJourneyBoard" behavior="0" />-->
<RootComponent type="66" schemaName="cdc_LeadBoard.LeadBoard" behavior="0" />
<RootComponent type="66" schemaName="cdc_StakeholderEngagement.StakeholderEngagement" behavior="0" /

</RootComponents>

 

It gives me other error 

Import Solution Failed: Root component missing for custom control CustomerJourneyBoard.CustomerJourneyBoard.

Root component missing for custom control CustomerJourneyBoard.CustomerJourneyBoard

 

 

I've had this in the past when a project was corrupted for reasons I wasn't able to work out quickly enough and the corruption broke the list of PCF components.

 

The only way I could and did fix it was to delete and recreate the directory the solution was in and then  recreate the solution by adding references to all the projects except the project that broke the solution.

---
If this post has answered your question please consider it for "Accept as Solution" or if it has been helpful give it a "Thumbs Up".
ben-thompson
Memorable Member
Memorable Member

Interestingly I discovered the same type 66 error yesterday when I deleted a control on an environment but left the solution it came from in place.

 

In yesterday's case deleting the solution did fix the problem and nothing else did.

---
If this post has answered your question please consider it for "Accept as Solution" or if it has been helpful give it a "Thumbs Up".
v-xida-msft
Community Support
Community Support

Hi @Bhuvita ,

Do you refer the Solution to three different Component Projects?

 

If you refer the Solution to three different Component Projects, I think this is the issue. If you remove the reference of CustomerJourneyBoard from this Solution file, the CustomerJourneyBoard Component would not be bind to this Solution.

So when you import this new solution into your Environment, the Solution could not recognize the CustomerJourneyBoard Component as one of references.

Before importing this new Solution into your Environment, you need to add the changed CustomerJourneyBoard Component as reference of this Solution again using the following command:

 pac solution add-reference --path <path to your Power Apps component framework project>

 

As an fixed solution, I also agree with @ben-thompson 's thought. Please remove the whole Solution file from your Environment, then re-import this new Solution file into your Environment.

 

More details about updating existing code component, please check the following article:

https://docs.microsoft.com/en-us/powerapps/developer/component-framework/updating-existing-controls

 

Best regards, 

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

@v-xida-msft 

yes i am referring the solution to three different component projects.

 

As a temporary fix indeed deleting the solution from the environment and importing it again works. @ben-thompson Thanks for the suggestion.

 

Earlier it used to work without deleting the solution from my environment. So if i have any changes to any of my component i just used to rebuild my solution with command  msbuild /t:rebuild and  remove the component CustomerJourneyBoard from environment and import the solution again into my environment. May be something has changed for this

Something has definitely changed recently - based on work I was doing this weekend I have a suspicion that pac pcf push even pac pcf push --force is currently broken.

---
If this post has answered your question please consider it for "Accept as Solution" or if it has been helpful give it a "Thumbs Up".

Hi @Bhuvita ,

Yeah, I agree with you. If you would like to get further help in this issue, please consider submit an assisted support ticket through the following link:

https://powerapps.microsoft.com/en-us/support/pro

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Results posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Solution Authors
Users online (4,211)