Answered

Passing Configuration to PCF Components

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

Hi all,

Can anyone help me out here? I'd like to pass some configuration to a PCF component (e.g. drop a control onto a model-driven form, then click properties and provide a string or numeric value).

Where do i start?

Cheers,

Andrew

Categories:

Power Apps Pro Dev & ISV

All responses (8)

Answers (1)

Sort by

Hemant Gaur Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Not sure I understand, if you are wanting to add input property to the component whcib can be configured at the control configuration time , you can add a property node with input type and data type to the manifest. If at the runtime you expect end user to provide some value than it can be HTML input control. Can you elaborate bit more and I can help?
Verified answer

Hemant Gaur Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

https://docs.microsoft.com/en-us/powerapps/developer/component-framework/manifest-schema-reference/property

Reference doc for the additional input properties. Field control can have multiple input properties, please see bullet graph oob control for reference.
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!
"you can add a property node with input type and data type to the manifest"

I think that's the answer i'm looking for Hemant. As you can tell I'm 'really' new to how this all works.

So if i wanted to say add a Theme Color parameter and a Number of Rows paramter it'd be something like:

<?xml version="1.0" encoding="utf-8" ?> <manifest> <control namespace="lyf365" constructor="HelloWorld" version="0.0.1" display-name-key="HelloWorld_Display_Key" description-key="HelloWorld_Desc_Key" control-type="standard">  <property name="sampleProperty" display-name-key="Property_Display_Key" description-key="Property_Desc_Key" of-type="SingleLine.Text" usage="bound" required="true" /> <property name="themecolor" display-name-key="Property_Theme_Color_Display_Key" description-key="Property_Theme_Color_Desc_Key" of-type="SingleLine.Text" usage="bound" required="true" /> <property name="numberRows" display-name-key="Property_NumberRows_Display_Key" description-key="Property_NumberRows_Desc_Key" of-type="SingleLine.Number" usage="bound" required="true" />
Hemant Gaur Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

Usage input if this is just used as read only.

usage - The usage attribute identifies if the property is meant to represent an entity attribute that the component can change (bound) or read-only values (input) bound, input or output.

You are doing great . I assume this is field control. Data set needs it inside data-set node. One more thing, since you are changing control definition the update might not work and you will need to unconfigure and remove old version.
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Ah perfect, thanks for the tips Hemant. That's really helpful.
Hemant Gaur Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

And of-type = Whole.None

Please see https://docs.microsoft.com/en-us/powerapps/developer/component-framework/manifest-schema-reference/property for supported CDS types
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks for the tip Hemant.

Getting there, just uploaded v1 of my control onto Github - in case anyone wants to see some bad typescript 🙂

Number Button Selector.
http://365lyf.com/powerapps-component-framework-pcf-number-button-selector/
Hemant Gaur Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

Congratulations Andrew 🎉. Hardest part is behind us now (getting the first control built :)).

Looking forward to more cool ones from you. As next step, I would recommend looking at data set (we have samples in preview) and also the framework API typing file to understand broader capabilities. You can pick up your favourite lib/service sample and try making it a PowerApp component.