Unanswered

Cannot choose Custom control when editing a PowerApp Model form in the PowerApp (modern) form editor

(0) Share

Report

Posted on by Ben Thompson

1,400

I have a number of Single text field PCF controls that are administrative that I would like to package up separately and make generally available. All of them follow the same pattern - 1 bound singleline.text field that contains the output and another bound singleline.text field that pulls in the entity name from the previous field to provide the context for the control.

Now when I use the classic former editor all the controls are visible but when I use the PowerApps editor they don't appear - see screenshots below.

So I have 2 questions:-

1) Am I missing something in my controlmanifest file

<?xml version="1.0" encoding="utf-8" ?>
<manifest>
 <control namespace="abc" constructor="AttributeList" version="0.0.1" display-name-key="AttributeList" description-key="AttributeList description" control-type="standard">
 <!-- property node identifies a specific, configurable piece of data that the control expects from CDS -->
 <property name="Attribute" display-name-key="Attribute" description-key="Attribute (single)" of-type="SingleLine.Text" usage="bound" required="true" />
 <property name="Entity" display-name-key="Entity" description-key="Entity" of-type="SingleLine.Text" usage="bound" required="true" /> 
 <resources>
 <code path="index.ts" order="1"/>
 <css path="css/AttributeList.css" order="1" />
 <img path="img/DownArrowTransparent.png" />
 </resources>
 </control>
</manifest>

2) If not when is this issue likely to be fixed so I can work out how to document using the control.

Classic Interface (works)Modern Interface (cannot be found)

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (3)

Answers (1)

v-yutliu-msft on at

Like (0)

Report

Hi @ben-thompson ,

Do you mean that your pcf control will become invisible in form editor?

Here's a doc about how to add pdf control to a field or entity, please refer this to see whether you made any mistake:
https://docs.microsoft.com/en-us/powerapps/developer/component-framework/add-custom-controls-to-a-field-or-entity

Also, please notice the pcf control's limit to see whether your problem is caused by this:

Control Configuration properties of input usage only limited to 100 characters.

Here's a issue for your reference:

https://powerusers.microsoft.com/t5/Power-Apps-Component-Framework/Problem-with-maximum-length-of-Input-parameters-which-are-of/td-p/288295

Best regards,

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

Like (0)

Report

No I mean that the controls are all invisible and inaccessible from within the new PowerApps form editor for reasons that I don't know but, I suspect, is due to the controls asking for multiple inputs rather than a single input.

If you look at my screenshot in the first post you can see the component that I created and added via the classic interface is shown as unknown and I cannot add the other components when I search for them.

The document you refer to references the old classic / web refresh form editor where all my controls appear as options and work fine as I demonstrated with the screenshots in my original post but that classic interface is deprecated.

I've attached an unmanaged solution with all 5 PCF components so that you can see the issue at first hand. All of them have 2 bound inputs as they take the entity value of a previous field as the basis of the query to generate the options that appear in the "select"/ optionset dropdown.

MetaDataSelectPCF...

Was this reply helpful? Yes No
Verified answer

namohant Microsoft Employee on at

Like (1)

Report

Hi @ben-thompson ,

We are currently working on having the option enabled for controls built using powerapps component framework. We will be ensuring to have it addressed soon and have it documented. I do apologize for the inconvenience and thanks for raising this. If you have any more questions please let us know.

Regards
Nandi

Was this reply helpful? Yes No