Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0043974 | Openbravo ERP | 02. Master data management | public | 2020-05-06 19:45 | 2020-05-26 12:52 |
|
Reporter | sdossantos | |
Assigned To | cberner | |
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | |
Platform | | OS | 5 | OS Version | |
Product Version | | |
Target Version | | Fixed in Version | PR20Q3 | |
Merge Request Status | |
Review Assigned To | alostale |
OBNetwork customer | Gold |
Web browser | |
Modules | Core |
Support ticket | 15940 |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0043974: In sales order when navigating the Delivery Location record is modified with another address whit the same address name |
Description | When two busines partner share the same name for two different addresses, and creating two consecutive sales orders one with each of these business partner. When editing the first sales order, if the delivery address is navigated, then this record is changed with the record of the address of the other business partner (of the second sales order created), this create problems with shipments (these orders are sent to addresses of other business partner). If this record is saved without knowing that this change was made (closing the form view or changing the focus to the order lines) or if any modification is made in another field and it is saved, it generates the problem of Shipping.
|
Steps To Reproduce | 1) Create two business partners (or update existing) adding on each one a new business partner address, same name for these addresses.
2) Create a new sales order, in form mode, with first business partner using the adress created in Delivery Location field. Add a product and book this order.
3) Create a new sales order, in form mode, with second business partner using the adress created in Delivery Location field. Save this record.
4) Close form mode and open first sales order created and navigate Delivery Location field.
At this point, the first sales order created was modified seting Delivery Location of second sales order created. If you make a change in other field and save this order you has modified the Delivery Location field permantly or if you accidentaly save this order. |
Proposed Solution | |
Additional Information | |
Tags | No tags attached. |
Relationships | |
Attached Files | Video.tar.xz (4,495,916) 2020-05-06 19:50 https://issues.openbravo.com/file_download.php?file_id=14437&type=bug |
|
Issue History |
Date Modified | Username | Field | Change |
2020-05-06 19:45 | sdossantos | New Issue | |
2020-05-06 19:45 | sdossantos | Assigned To | => Triage Finance |
2020-05-06 19:45 | sdossantos | Modules | => Core |
2020-05-06 19:45 | sdossantos | Triggers an Emergency Pack | => No |
2020-05-06 19:50 | sdossantos | File Added: Video.tar.xz | |
2020-05-06 20:25 | matias-bernal | OBNetwork customer | => Gold |
2020-05-06 20:25 | matias-bernal | Support ticket | => 15940 |
2020-05-07 08:33 | dmiguelez | Resolution time | => 1590530400 |
2020-05-07 08:34 | dmiguelez | Assigned To | Triage Finance => platform |
2020-05-07 09:25 | jfrances | Issue Monitored: jfrances | |
2020-05-14 20:02 | matias-bernal | Issue Monitored: matias-bernal | |
2020-05-21 13:25 | cberner | Assigned To | platform => cberner |
2020-05-21 13:25 | cberner | Status | new => scheduled |
2020-05-21 13:25 | cberner | Review Assigned To | => alostale |
2020-05-22 10:44 | alostale | Note Added: 0120165 | |
2020-05-26 12:42 | hgbot | Checkin | |
2020-05-26 12:42 | hgbot | Note Added: 0120286 | |
2020-05-26 12:42 | hgbot | Status | scheduled => resolved |
2020-05-26 12:42 | hgbot | Resolution | open => fixed |
2020-05-26 12:42 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/devel/pi/rev/1766912da85a42f6b3a96d51fafe45f6b45a1b0f [^] |
2020-05-26 12:52 | alostale | Note Added: 0120287 | |
2020-05-26 12:52 | alostale | Status | resolved => closed |
2020-05-26 12:52 | alostale | Fixed in Version | => 3.0PR20Q3 |