[
https://issues.apache.org/jira/browse/OFBIZ-6882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416089#comment-16416089 ]
Jacques Le Roux commented on OFBIZ-6882:
----------------------------------------
Thanks Scott, Paul, Nicolas (long ago),
I agree I should have gone with streetNumber, I think I focused on the functionallity but not the name despite your several comments.
It's not a big deal, we can add streetNumber and streetNumberExt in trunk keeping oldHouseNumber and oldHouseNumberExt with column-names STREET_NUMBER and STREET_NUMBER_EXT plus provide a service to move the data from the old fields to the new ones. Also we should mark those fields to be removed in next release branch (I don't remember how we decided to mark that).
Agreed? We could even dot that in R17 (no risks at all) since it has not been released, what do you think?
> Extend the PostalAddress entity with additional elements
> --------------------------------------------------------
>
> Key: OFBIZ-6882
> URL:
https://issues.apache.org/jira/browse/OFBIZ-6882> Project: OFBiz
> Issue Type: Improvement
> Components: party
> Affects Versions: Trunk
> Reporter: Pierre Smits
> Assignee: Pierre Smits
> Priority: Major
> Labels: 3rdParty, Shipment, integration
> Fix For: 16.11.01
>
> Attachments: OFBIZ-6882-party-PostalAddress.patch
>
>
> Various modern day 3rd party delivery solutions (e.g. PostNL in The Netherlands) require that elements are delivered separately, so that addresses can be checked more easily.
> Current definition of the PostalAddress doesn't have separation of:
> * street name
> * house number
> * house number addition or extension
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Locked
