Related ISSUE-52924: Add new references ("Invoice Address" and "Shipping...
This MR fixes the following issues:
- https://issues.openbravo.com/view.php?id=52924 (https://openbravo.atlassian.net/browse/RM-3624)
- https://issues.openbravo.com/view.php?id=53218 (https://openbravo.atlassian.net/browse/RM-6521)
Other Mrs involved in this project
- !955 (merged)
- https://gitlab.com/openbravo/ci/modules/org.openbravo.test.mobile.sampledata/-/merge_requests/98
- https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/merge_requests/1281
- https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2.sampledata/-/merge_requests/55
- https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1940
- https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/merge_requests/566
Following changes are done in this MR:
- Remove a flag in CRM property "Is default address". This flag does not make sense anymore because
- For double endpoint -> A field defined in address mapping indicates which property stores the value about default for shipping and invoicing (ISINVOICE_ADDRESS, ISSHIPPING_ADDRESS, ISDEFAULT_INVOICE_ADDRESS, ISDEFAULT_SHIP_ADD)
- Remove the possibility to define different properties as key property (remove key seq no field)
API change documented here
- Single enpoint only accept (1 address for shipping and 1 address for invoince) or 1 address for both
- Allow to select invoice and shipping address
- Allow to create customers and addresses using openbravo CRM conector
try
- 20/09: https://builds.openbravo.com/job/try-ret-init/9291/artifact/retail.html
- 20/09: https://builds.openbravo.com/job/try-init/2659/console -> API change to manage
- 20/09 - https://builds.openbravo.com/job/try-pos2-init/2947/console
Edited by Guillermo Alvarez de Eulate