Unanswered

Increasing the number of characters that can be passed as input to a PCF Component

(0) Share

Report

Posted on by navneet_singh

I have a PCF Component that takes input. I am unable to give more than 160 characters as input. I want the following as the input to my field name:

Will this website use personal data collection forms and limit collection fields to no more than the following: first name, last name, job title, phone, email, company name, company size, job title, and country?

But I'm only able to give the input till this:

Will this website use personal data collection forms and limit collection fields to no more than the following: first name, last name, job title, phone, email,

Can anyone help me to increase this?

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (8)

Answers (0)

v-yutliu-msft on at

Like (2)

Report

Hi @navneet_singh ,

Do you mean that you cannot enter into your pcf control more than 160 characters ?

I'm afraid it's a known issue that is seen as a bug in the form designer and for reference it is tracked via internal ID 1485549 .

Control Configuration properties of input usage only limited to 100 characters

Here are two similar issues for your reference:

https://powerusers.microsoft.com/t5/Power-Apps-Component-Framework/Control-Configuration-properties-of-input-usage-only-limited-to/td-p/351525

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

If there's any improvement about this, I will reply here.

Best regards,

Was this reply helpful? Yes No
navneet_singh 13 on at

Like (0)

Report

Thankyou, @v-yutliu-msft !

Was this reply helpful? Yes No
Danish N. 186 on at

Like (0)

Report

@v-yutliu-msft any updates on this?

Was this reply helpful? Yes No
PowerRobin 26 on at

Like (0)

Report

Need an update as well. Want to put SVG-code in there with a length of 100.000 characters and more. Would really be a shame if there was a need to hardcode this, because of this bug...

Was this reply helpful? Yes No
Diana Birkelbach 3,072 Most Valuable Professional on at

Like (1)

Report

Hi @PowerRobin ,

For an SVG, how about creating a Webresource? The PCF property could then be the name of the webresource.

Was this reply helpful? Yes No
PowerRobin 26 on at

Like (0)

Report

Can you point me into the right direction how to do this?
Do I have to implement this in the TypeScript code or can I select a webresource as a value for the field?

Was this reply helpful? Yes No
Diana Birkelbach 3,072 Most Valuable Professional on at

Like (1)

Report

Hi @PowerRobin ,

I would like to say first, that you can include SVG Files in your PCF, and you have methods to access them.

But in case you want to let the maker choose another SVG, and you go wth the webResource idea, you would define a parameter of type string for the PCF, where the maker would input the name of the webresource. Then you can retrive the webResource.

For instance Andrew Butenko ( @a33ik ) did something like this in his Dependent Optionset PCF: https://github.com/AndrewButenko/DependentOptionset_PCF/blob/master/DependentOptionset/index.ts#:~:text=%7D-,private%20loadDependentOptionsetConfiguration(context%3A%20ComponentFramework.Context%3CIInputs%3E)%20%7B,%7D,-private%20onChange()%3A%20void

Hope is helps!

Was this reply helpful? Yes No
PowerRobin 26 on at

Like (0)

Report

Thank you @DianaBirkelbach !

This answers my question perfectly!
In my case I would definitely try to do it the webcomponent way and not "hardcode" the SVG into the PCF for maximum flexibility / reusability.

Was this reply helpful? Yes No