Update location tokens for Contact to new apiv4 style #25032
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Update location tokens for Contact to new apiv4 style
Traditionally we have supported a token format that reflects the Query object / apiv3. During our last round of work on tokens we migrated the 'adverstised' token names to apiv4 style, while keeping the old ones working as deprecated tokens.
For the Contact tokens the internal workings use apiv4 now but the advertised tokens are apiv3 style. In addition the apiv4 style tokens that are also supported differed from what has since been added to apiv4
{contact.street_adddress}
{contact.primary_address.street_adddress}
{contact.address_primary.street_adddress}
Before
After
Technical Details
Noting minor changes to the formatting of the legacy tokens
contact.on_hold goes from 0 to 'No'
contact.im_provider goes from a number to a label
contact.signature_html renders html-encoded in plain text mode
I think these are all obscure enough we shouldn't hit any issues (and the advertised ones do work)
Comments