Unanswered

Export and Import Solution with PCF out of the CRM

(1) Share

Report

Posted on by OrbisService

After we imported a solution from our developer to a Dev-System, where the PCF worked perfectly we wanted to exprot a Solution with the PCF and import it into a Quality-System.

Where the Error-Message:
"Cannot add a Root Component PCF.Scan of type 66 because it is not in the target system." has occured.

To fix this Problem we imported the original solution of our developer and not imported the exported one form the CRM. It seems that the CRM-Solution-Export is not exporting all of the needed components. Maybe this is bug here.

The error also occurs, when the PCF is alread in the target system and you want to add the form, where the PCF is implemented.

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (5)

Answers (0)

Community Power Pla... on at

Like (1)

Report

i think it is the same as (or at least) related to https://powerusers.microsoft.com/t5/PowerApps-component-framework/Bug-dependecy-to-solution-containing-control-is-reported/m-p/355073

Was this reply helpful? Yes No
davallen Microsoft Employee on at

Like (0)

Report

Do we have anyone who can speak to this issue? I am experiencing it also. I am just trying to upload a new version of my PCF control and receiving this issue.

Do I have to remove all depedencies of this control in order for the solution to upload? This seems like a major issue.

Was this reply helpful? Yes No
ScottDurow 1,039 on at

Like (0)

Report
The documentation seems to imply that the preferred ALM for a PCF component is to build a managed solution from your code rather than export after deploying as unmanaged:

msbuild /t:build /restore /p:configuration=Release
This will build a managed solution that you can import into your target envrionments, it will also ensure that your code is build using production mode so that it is optimised.

Was this reply helpful? Yes No
Diana Birkelbach 3,072 Most Valuable Professional on at

Like (1)

Report

I wonder if using unmanaged solutions for PCF components is really a bad practice.
Just consider delivering solutions to Market Place without dependencies on another solutions: there would have been an option to import PCF components unmanaged and then build a managed solution with the PCF component inside.

Was this reply helpful? Yes No
Hemant Gaur on at

Like (0)

Report

@davallen wrote:

Do we have anyone who can speak to this issue? I am experiencing it also. I am just trying to upload a new version of my PCF control and receiving this issue.

Do I have to remove all depedencies of this control in order for the solution to upload? This seems like a major issue.

Hi @davallen ,

Have you tried to replay the flow? Is the error consistent.

Can you please share the details with me at hemantg@microsoft.com ? If you have concrete repro steps it would be really helpful.

I will loop-in right folks who cna help .

Thanks,

Hemant

Was this reply helpful? Yes No