cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
ben-thompson
Solution Sage
Solution Sage

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

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)Classic Interface (works)Modern Interface (cannot be found)Modern Interface (cannot be found)

---
If this post has answered your question please consider it for "Accept as Solution" or if it has been helpful give it a "Thumbs Up".
1 ACCEPTED SOLUTION

Accepted Solutions

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

View solution in original post

3 REPLIES 3
v-yutliu-msft
Community Support
Community Support

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-fi...

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-In...

 

 

Best regards,

Community Support Team _ Phoebe Liu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

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.

---
If this post has answered your question please consider it for "Accept as Solution" or if it has been helpful give it a "Thumbs Up".

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

View solution in original post

Helpful resources

Announcements
PA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

MBAS Attendee Badge

Claim Your Badge & Digital Swag!

Check out how to claim yours today!

secondImage

Are Your Ready?

Test your skills now with the Cloud Skill Challenge.

secondImage

Demo Extravaganza is Back!

We are excited to announce that Demo Extravaganza for 2021 has started!

MBAS on Demand

Microsoft Business Applications Summit sessions

On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks

Users online (54,073)