Answered

Cannot Add PCF Code Component to Canvas App

(1) Share

Report

Posted on by Rick Wilson

160

I am attempting to import one of my code components into a canvas app. I receive a very generic error in the UI but after looking through the network traffic I get the following error. Anyone have any thoughts or seen this before?

Thanks,

Rick

https://instance-eus.create.powerapps.com/v3.20022.21.144312096/api/v2/invoke

Request

Response:

[{"dresult":{"f":[{"error":1,"errorMessage":"Sequence contains no matching element","templateName":"","controlName":"raw_RAW.ColorPicker.ColorPicker"}]}},
{"seq":35}]

Manifest File

https://github.com/rwilson504/PCFControls/blob/master/ColorPicker/ColorPicker/ControlManifest.Input.xml

Import Attempt

Import Code Component

Error Message in UI

Error Message

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (3)

Answers (1)

Sort by

Hemant Gaur Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

I was able to import the solution from the same github and have the working control inside my canvas app.

Can you please share your environment details and session ID for further investigation. (DM or hemantg@microsoft.com)

hemant gaur

Was this reply helpful? Yes No
Verified answer

Diana Birkelbach 3,072 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

HI @RAWilson
I couldn't import your component in the beginning ether.
First I thought it's because of the preview-image="preview.png" in your manifest, because it's documented only for model-driven apps: https://docs.microsoft.com/en-us/powerapps/developer/component-framework/manifest-schema-reference/control
But it still didn't work.
BUT, strangely I could import it in a canvas app, after I deleted the second property "defaultColor" from the manifest.
I don't know what's "special" about this property. Maybe the defaultValue or comment, because of "#" in "#ffffff"? The only thing that I haven't tested before in a CanvasApp is the usage="input", but I think this shouldn't be a problem.
Best regards,
Diana

Was this reply helpful? Yes No
Rick Wilson 160 on at

Like (0)

Report
Copy link

Link copied!

Thank you Diana!!!

You were right on the money with the preview-image attribute causing the issue.

I copied the code from the original ColorPicker and renamed it to CanvasColorPicker and tried all these test below.

-Initial Version. NO
-Remove preview-image attribute. NO
-Removed the ',' character from the description-key of the defaultColor property. NO
-Removed the ':' character from the description-key of the defaultColor property. NO
-Removed the '(' and ')' characters from the description-key of the defaultColor property. NO
-Removed # from the description-key and default-value of the defaultColor property. NO
-Removed the default-value attribute of the defaultColor property. NO
-Change name of defaultColor to something else. NO
-Removed the entire defaultColor property. NO

In between all the tests though I was only updating the control and solution versions and doing a publish all. So I took everything back from the start and this time between each test i actually deleted the control completely from the environment then re-imported. It worked on the first test of removing the preview-image attribute! I can even see my #ffffff default value.

Thanks Again Diana!

@HemantG Any way we could get an item put it to just ignore that attribute on import?

Was this reply helpful? Yes No