Openbravo Issue Tracking System - POS2 | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0054790 | POS2 | POS | public | 2024-02-28 15:02 | 2024-03-21 11:41 |
Reporter | ngarcia | ||||
Assigned To | SABARINATH P | ||||
Priority | urgent | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Platform | OS | 5 | OS Version | ||
Product Version | |||||
Target Version | Fixed in Version | 24Q2 | |||
Merge Request Status | |||||
Review Assigned To | |||||
OBNetwork customer | |||||
Support ticket | |||||
Regression level | |||||
Regression date | |||||
Regression introduced in release | |||||
Regression introduced by commit | |||||
Triggers an Emergency Pack | No | ||||
Summary | 0054790: Errors While Importing POS Data due to the address length higher than 60 | ||||
Description | Errors While Importing POS Data due to the address length higher than 60. In the customer instance (24Q1) the Order is the one that gets stuck in EWI: Error in OrderLoader: Location.addressLine1: Value too long. Length ..., maximum allowed 60 In https://livebuilds.openbravo.com/context/retail_pos2_pgsql/security/Login [^] the Business Partner Location is not stuck in Errors While Importing POS Data but the business partner is created without location | ||||
Steps To Reproduce | In https://livebuilds.openbravo.com/context/retail_pos2_pgsql/security/Login [^] Create a New Customer Assign an address with more than 60 characters. Set it as Shipping and Invoicing Address Add a product, pay it and done In the backoffice: The Order gets stuck in Errors While Importing POS Data with the following error: org.postgresql.util.PSQLException: ERROR: insert or update on table "c_order" violates foreign key constraint "c_order_billto" Detail: Key (billto_id)=(...) is not present in table "c_bpartner_location". The business partner is created without location and the log shows: 2024-02-28 09:07:52,646 [Import Entry - 1] ERROR org.openbravo.retail.posterminal.CustomerAddrLoader - Exception while creating BPartner Address org.openbravo.base.validation.ValidationException: Location.addressLine1: Value too long. Length ..., maximum allowed 60 [...] at org.openbravo.base.model.Property.checkIsValidValue(Property.java:835) ~[classes/:?] | ||||
Proposed Solution | Two things should be reviewed here: 1) a record in Errors While Importing POS Data should be created if the import of a location fails 2) it should be controlled if the address is higher than the column size. It can be when creating a new address but also when using an alternate invoicing feature | ||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2024-02-28 15:02 | ngarcia | New Issue | |||
2024-02-28 15:02 | ngarcia | Assigned To | => Retail | ||
2024-02-28 15:02 | ngarcia | Triggers an Emergency Pack | => No | ||
2024-02-28 15:02 | ngarcia | Issue Monitored: networkb | |||
2024-03-04 05:47 | SABARINATH P | Assigned To | Retail => SABARINATH P | ||
2024-03-14 12:48 | SABARINATH P | Status | new => scheduled | ||
2024-03-18 06:15 | hgbot | Note Added: 0162248 | |||
2024-03-20 13:46 | hgbot | Note Added: 0162419 | |||
2024-03-21 11:40 | hgbot | Note Added: 0162463 | |||
2024-03-21 11:40 | hgbot | Note Added: 0162464 | |||
2024-03-21 11:41 | hgbot | Resolution | open => fixed | ||
2024-03-21 11:41 | hgbot | Status | scheduled => closed | ||
2024-03-21 11:41 | hgbot | Fixed in Version | => 24Q2 | ||
2024-03-21 11:41 | hgbot | Note Added: 0162465 | |||
2024-03-21 11:41 | hgbot | Note Added: 0162466 |
Notes | |||||
|
|||||
|
|
||||
|
|||||
|
|
||||
|
|||||
|
|
||||
|
|||||
|
|
||||
|
|||||
|
|
||||
|
|||||
|
|