I have a pcf control that requires more than 100 characters of input on the config property but onfiguration properties of usage type input only accepts 100 characters. Already set the property-type to SingleLine.TextArea, also tried Multiple but still no luck. My temporary workaround is inspecting the input element then modifying the maxlenght to 1000. Aside from this, is there anything I can do?
That would be another work around, but the scenario I'm trying to achieve is when you don't have access to the data model and not allowed to add a field where it can be bound to. But anyways, thanks for your input @vigneshR.
You are correct that this limitation is unnecessarily low. We have filed an internal bug (1485549) to investigate what the actual limit set on values here should be, so this process should be fixed in a future iteration to allow for a more reasonable limit.
In the meantime, your workaround is probably the best option short of manually updating the form definitions; please be wary that there may be limits to the size allowed my form configuration metadata that may also be hit with this solution if the value you are setting is very large.
I am having the same issue. My PCF control needs more than 100 characters of input in the config property, which currently I am not being able to.
@jolake any update on the internal bug, or when can we expect this to get resolved.
Hi @Kipetcoff ,
It is possible to extend the length as explained in several answers and the question itself, but the workarrounds are hard to explain to a customer who wants to use the PCFs.
A customer friendly workarround would be to use environment variables for longer strings.
Hopefuly this will be fixed soon.
Join us for the next call on August 17, 2022 at 8am PDT.
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.