UPDATE:  We shipped granular address properties this past Friday. Refer to the Changelog for details.  

UPDATE...These address fields should be available in the next week or two.

Hi Dan

Thanks for the update

Looking forward to seeing it live and playing with it.

UPDATE: We're in final steps of tech research and hope to deliver in coming weeks. Thanks for your input. 

Address properties to be added (barring any last minute adjustments to approach):

address_lines

suburb (relevant for New Zealand)

city

state

postal_code

county

country 

I have seen address lines done both ways i.e. have an address block (like in RE 7) or have address line 1-5 (or any number in between).  I don't really have a preference as either way you are able to break them up or put them together depending on the scenario.

Other than in RE7 which really over complicates the state and county fields depending on the how the country models to one of four or five set address countries, I normally see one field representing state, province or county.

I realise that in the US there are counties within states but I am not so sure how relevant this is when recording a postal address (although I would probably defer to a resident of the US rather). In the UK county is not officially required in postal addresses but some people like to retain it as part of their address.

I would say simpler is better in this respect. Have one field of region that could cover state, province or county. Whether or not this is a dropdown entry is another discussion though...

UPDATE...We're looking to make this enhancement in the coming month(s). Current thinking is to provide:

• country
• address lines (as single property)
• city
• state
• postal code
• county

We could use some developer input into the address design.

QUESTION #1:  Single 'address lines' property or each address line as its own property? What're developers thoughts, based on experience with other APIs and prior Blackbaud address integrations?

QUESTION #2:  If you have experience working with addresses across multiple countries, what can the API do to manage that complexity? Does the above suffice, where for example 'city' is really 'suburb' in Australia, and 'state' is really 'province' in Canada? Or, have you seen other APIs handle international addresses better?

We're currently evaluating technical options for making this improvement, as we've heard this request from multiple sources and agree with the value. I'll update to Planned once I have a better idea of when it may be delivered.