Enable binding to OOB Address Fields

[OliverFlint]

While experimenting with PCF development I have noticed that it is not currently possible to bind properties to the OOB address fields (e.g. address1_line1, address2_line1, etc).

Could this be enabled? As currently, the only workarounds are to duplicate the address fields on the entity and then how JavaScript and/or workflow to synchronise the data between the fields, or to use the webapi to retrieve and update values.

[sheldoncopper73]

Hi @OliverFlint  @HemantG 

1)You can pass the logical names of the field through input parameter(hardcoded)

<property name="addressLatitude" display-name-key="Enter Latitude Field Logical Name" description-key="Latitude Field Logical Name" of-type="SingleLine.Text" usage="input"/>

2)Then get the passed value through 

let getLatitude = context.parameters.addressLatitude.raw

3)And then retrieve values through 

context.webAPI.retrieveRecord();

4)You will get entity name and record id through 

context.page.entityTypeName;

context.page.entityId;

[HemantG]

Ack the issue, its being tracked via interna bug ID 1501610. 

[kenakamu]

I couldnt find page object in context.

[sheldoncopper73]

@kenakamu It is not in there in definition file which is provided but you will get in crm try checking in debugger add a breakpoint in init and check the context

[mudassarhassan]

facing the same problem and waiting for a quick fix to this one

---

@OliverFlint wrote:

While experimenting with PCF development I have noticed that it is not currently possible to bind properties to the OOB address fields (e.g. address1_line1, address2_line1, etc).

Could this be enabled? As currently, the only workarounds are to duplicate the address fields on the entity and then how JavaScript and/or workflow to synchronise the data between the fields, or to use the webapi to retrieve and update values.

---

[crmkeeper]

What is the holdup? There is no logical reasoning why some single line text fields are there and some are not. We have tried several workarounds, but it's not sexy. I am currently using a BusinessRule to copy the custom fields to the OOTB fields. It's not great..