It sounds like the PCF is not the right fit for a scenario like this.
Lets try one more time. Can you explain what is the end user expereince expected, possibly with some mock screens if that helps. We can then see whats the best fit.
@HemantGhopfully the below screenshot will provide some extra clearity. We want to put a PCF on the "Business Phone", so that it can be formated. However, based on the country. We want the format to change.
Curently there is a restriction that the composite fields cannot be configured to the custom control so address-country is not available.
What you can do is create a placeholder address field for country and add a PBL to set the value of this fields base on the country in the address. Hide the field on the form so that the user does not sees two addresses.
use the placeholder address - country field on the form and and add a sync workflow to write this value into actual address-country on form save.
Add additional input property to the Business phone field which is of type text and configure it to the placeholder address feild.
The additional property is now available in the business phone and control can access it to know what country is in the form.
I appreciate the options and It looks like there are ways to kind of do it. However at the moment, it is forcing a fit. Maybe down the road it will open up more.
Read the announcement for more information!
Congrats to the finalists of our ‘Better Together’-themed T-shirt design contest! Click for the top entries.
Features releasing from October 2019 through March 2020
Innovate, Collaborate, Grow - The top training and networking event across the globe for Microsoft Business Applications