Hi, I have observed a weird behavior on PCF bound properties.
I have a PCF control with 2 bound SingleLine.Text properties.
I want to bind my control on the Account Form to fields from Address1 like this
I have put my 2 fields on the form just to be sure that they are available for the control to pick.
Now I will bind my PCF to the ‘address1_country’ field
As expected, the CountryCode gets automatically binded to ‘address1_country’
Problem is that now I want to bind the second parameter to ‘address1_city’, I do not see this field on the available fields that are proposed. ‘address1_city’ is of type SingleLine.Text so it should be available to choose .
Has anyone ever noticed that behavior? Is this normal or is this a bug? Is it because the address fields are part of the composite field (address1) ?
(See attachments for screenshots)
Solved! Go to Solution.
Thanks for the solution @a33ik
Does anyone from the product team knows if this will be addressed anytime soon?
It's a bit odd to have to modify the form XML.
What if I want to sell a PCF that targets addresses.
The main usage of customers would be to target adresses fields of Accounts and Contacts.
I dont want to tell them to mingle with the Form XML.
You could package the solution up with a Account and Contact forms that included your address PCF component within it but as you say you can't expect others to hack formxml to get things to work.
Find your favorite faces from the community presenting at the Power Platform Community Conference!
See the latest Power Apps innovations, updates, and demos from the Microsoft Business Applications Launch Event.
ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.
Features releasing from October 2020 through March 2021