Answered

Binding to address fields on contact/account

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

I'm just playing with the PCF and noticed that I cannot bind properties of my component to the address fields (e.g. address1_line1).

I am able to configure address fields on the form to display the control in the UI and that binds the first property. But any other properties after that cannot be bound to address fields on contact/account. I can bind them to other SingleLine.Text fields (e.g. firstname).

Is this a limitation or a bug?

Cheers

Ollie

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (15)

Answers (2)

Sort by

Verified answer

Hemant Gaur Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

This is a known issue which has come up few times in the past too. It is being evaluated and tracked.

As a workaround you can create duplicate text fields for the address components and use the PBL/ClientAPI script to read values from these into the OOB ones. Workflows can also be used fro data copy.

Was this reply helpful? Yes No
Sheldon Copper 200 on at

Like (2)

Report
Copy link

Link copied!

I have also tried that, address fields on order like ship to and bill to address could be bind but for account, I am passing the logical name of the fields and retrieving their values through context.webapi.retrieve method

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Thanks for the replies guys!

I'll look forward to this being fixed 😉

Was this reply helpful? Yes No
Hemant Gaur Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

@sheldoncopper73 wrote:

I have also tried that, address fields on order like ship to and bill to address could be bind but for account, I am passing the logical name of the fields and retrieving their values through context.webapi.retrieve method

That is interesting solution. Do you mind sharing the code for community reference as this avoids field duplication.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

FYI, I have created an Idea/Feature request for this... https://powerusers.microsoft.com/t5/PowerApps-Ideas/Enable-binding-to-OOB-Address-Fields/idi-p/302387#M26641

Was this reply helpful? Yes No
Sheldon Copper 200 on at

Like (2)

Report
Copy link

Link copied!

Hey @HemantG Just wanted to know when will we be the address bug will be fixed.

Was this reply helpful? Yes No
heitorsalatiel 2 on at

Like (0)

Report
Copy link

Link copied!

There's already a final solution for this issue ? For the solution I've been implementing, I can't use any of the workarounds presented here.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Can you please share the solution? I am unable to access the address fields from my control?

Was this reply helpful? Yes No
Sheldon Copper 200 on at

Like (0)

Report
Copy link

Link copied!

Try this way I am able to get address field value
You have pass field logical name as input parameter then use context.webApi.retrieve to get passed parameter value to set value use context.webApi.update
For current entity and recordID
store context in a variable : let _context:any = context(since page is not declared in index declaration file you will get error)
_context.page.entityTypeName;
_context.page.entityId;

https://powerusers.microsoft.com/t5/PowerApps-Ideas/Enable-binding-to-OOB-Address-Fields/idi-p/302387#comments

Was this reply helpful? Yes No
MJain 2,450 on at

Like (1)

Report
Copy link

Link copied!

May be I am late here but what we ended up is using the solution from this link :

https://www.magnetismsolutions.com/blog/jaredjohnson/2019/07/04/binding-to-address-fields-in-a-pcf-control

Bind your address fields on the form as single line text and then open XRM toolbox and update them using the link mentioned above.

Thanks

Was this reply helpful? Yes No