Unanswered

All controls disappear from Add Control Dialog after importing PCF solution

(1) Share

Report

Posted on by Mikko_K

I have created two PCF controls and a solution for them. After importing the solution, the list of controls on Add control dialog goes empty. Also the built-in controls disappear. Any ideas what is wrong or how to start debugging?

Other info:

I have used "pcf push" to test. This works fine.

I have one solution with two controls. I have increased version numbers for controls and solution.

I built the solution using "msbuild /t:build /restore /p:configuration=Release".

The issue is the same on multiple environments.

I'm using version 1.2 of PCF.

After import, the solution and its contents look OK on CE solutions. There are no import errors.

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (10)

Answers (0)

Sort by

a33ik 3,306 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

I had similar issue. Can you please post ControlManifest.Input.xml here?

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

Like (0)

Report
Copy link

Link copied!

Can we get more details, is it like on import you don't get any errors and upon import the controls bound don't render?

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

Like (0)

Report
Copy link

Link copied!

Hi @Mikko_K ,

How do you built your solution? Using "msbuild /t:build /restore /p:configuration=Release" command?

Have you taken a try with the Solution functionality in PowerApps web portal (https://make.powerapps.com)?

Could you please share a screenshot about this issue within your app?

Please consider take a try with the Solution functionality in PowerApps web portal (https://make.powerapps.com), then check if the issue is solved.

More details about the Solution in PowerApps, please check the following article:

https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/use-solution-explorer

Best regards,

Was this reply helpful? Yes No
Mikko_K 25 on at

Like (0)

Report
Copy link

Link copied!

Hi,

- I built using "msbuild /t:build /restore /p:configuration=Release".
Inside manifest.zip:
- Attached manifest.xml (ControlManifest.Input.xml).
- Attached solution.xml

As for clarification for questions above,
1. Build -> success
2. Import solution -> success
3. Go to solution editor, open a form for edit, add a field -> success
4. Change the control of the field from the default to my control -> can't do that, the list to choose from is empty. Also, the built-in CE components have disappeared from the list.

So the problem is not with the component itself (it works when I update it using "push").

manifest.zip

Was this reply helpful? Yes No
Mikko_K 25 on at

Like (0)

Report
Copy link

Link copied!

Hi,

Here.

manifest.zip

Was this reply helpful? Yes No
dmognaschi 6 on at

Like (0)

Report
Copy link

Link copied!

Hi

I have the same problem: after installing a managed solution containing one custom control of type OptionSet, all the available controls compatible with OptionSet field disappeared from the selection dialog.

In attachment my manifest.

@Mikko_K , have you solved this issue?

Thank you,
Davide

ControlManifest.I...

Was this reply helpful? Yes No
a33ik 3,306 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!
@dmognaschi I checked your manifest and reason why you experience issue is following property:
<property name="icons" display-name-key="Icons" description-key="Icon list in Json format [{'value':number, 'url':'string'}]" of-type="SingleLine.TextArea" usage="input" required="true" default-value="{}" />
and to be more specific - ' characters you used in the description. Remove it or replace with other symbols, pack solution, import to your CDS and issue should disappear.

Was this reply helpful? Yes No
Mikko_K 25 on at

Like (0)

Report
Copy link

Link copied!

In case the suggestion above doesn't help, I'm just letting you to know that I was never able to pinpoint the problem. After running build + install process numerous times, it just got somehow solved.

Was this reply helpful? Yes No
dmognaschi 6 on at

Like (0)

Report
Copy link

Link copied!

Solved,
thank you @a33ik.
I confirm that the cause was special characters in the property's description.

Have a nice day,
Davide

Was this reply helpful? Yes No
Hemant Gaur Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Thanks for the confirmation. We are tracking it as internal bug # 1663317

hemant

Was this reply helpful? Yes No