Unanswered

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

(0) Share

Report

Posted on by Bhuvita Sisodiya07

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 ?

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (8)

Answers (0)

Sort by

v-xida-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!
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-message-cannot-add-a-root-component-guid-of-type-29-because-it-is-not-in-the-target-system?pifragment-97030=1

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-failure?forum=crmdevelopment

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 :

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

<RootComponents>  </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,

Was this reply helpful? Yes No
Bhuvita Sisodiya07 78 on at

Like
a
(0)

Report
Copy link

Link copied!

@v-xida-msft

No i have not modified my customization.xml file.

I tried commenting out the

<RootComponents>

<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

Was this reply helpful? Yes No
Ben Thompson 1,400 on at

Like
a
(0)

Report
Copy link

Link copied!

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.

Was this reply helpful? Yes No
Ben Thompson 1,400 on at

Like
a
(0)

Report
Copy link

Link copied!

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.

Was this reply helpful? Yes No
v-xida-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!
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,

Was this reply helpful? Yes No
Bhuvita Sisodiya07 78 on at

Like
a
(0)

Report
Copy link

Link copied!

@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

Was this reply helpful? Yes No
Ben Thompson 1,400 on at

Like
a
(0)

Report
Copy link

Link copied!

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.

Was this reply helpful? Yes No
v-xida-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

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,

Was this reply helpful? Yes No