Openbravo Issue Tracking System - Retail Modules |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0051447 | Retail Modules | Web POS | public | 2023-01-24 15:52 | 2023-01-27 07:39 |
|
Reporter | marvintm | |
Assigned To | ranjith_qualiantech_com | |
Priority | normal | Severity | major | Reproducibility | have not tried |
Status | closed | Resolution | fixed | |
Platform | | OS | 5 | OS Version | |
Product Version | | |
Target Version | RR22Q4.2 | Fixed in Version | RR22Q4.2 | |
Merge Request Status | approved |
Review Assigned To | |
OBNetwork customer | No |
Support ticket | |
Regression level | Production - Confirmed Stable |
Regression date | 2022-08-29 |
Regression introduced in release | RR22Q4 |
Regression introduced by commit | https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/commit/9b9213cd7d8c8c10553a4a4b2dfffe1256e970f6 [^] |
Triggers an Emergency Pack | No |
|
Summary | 0051447: Cashup update happening in orders and cashups is failing if the "paymentMethods" property is not defined, generating EWIs |
Description | As part of this project:
https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/merge_requests/886 [^]
new data was added to the cashup information, and the corresponding classes that process and save it were changed, and they are now expecting it to be there (and specifically, the "paymentMethods" object inside the cashupReportInformation data).
However, if orders or cashups were generated while being offline, and then the customer is updated, this data will not be in the JSON, and the process will fail, generating records in Errors While Importing.
This is not correct, the code should be smart and first check if the "paymentMethods" property exist, and if it doesn't the corresponding code to save it should not be executed. |
Steps To Reproduce | - Create orders or cashups while being offline in a release before this development
- Update to the newer version with this development, and then synchronize those orders
- Verify that they generate Errors While importing |
Proposed Solution | Handle the case of "paymentMethods" property not being present, by just ignoring this part of the code. |
Additional Information | |
Tags | No tags attached. |
Relationships | blocks | defect | 0051446 | | closed | ranjith_qualiantech_com | Cashup update happening in orders and cashups is failing if the "paymentMethods" property is not defined, generating EWIs |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2023-01-24 15:53 | marvintm | Type | defect => backport |
2023-01-24 15:53 | marvintm | Target Version | => RR22Q4.2 |
2023-01-25 06:05 | ranjith_qualiantech_com | Assigned To | Retail => ranjith_qualiantech_com |
2023-01-27 06:34 | hgbot | Merge Request Status | => open |
2023-01-27 06:34 | hgbot | Note Added: 0145892 | |
2023-01-27 07:39 | hgbot | Merge Request Status | open => approved |
2023-01-27 07:39 | hgbot | Resolution | open => fixed |
2023-01-27 07:39 | hgbot | Status | scheduled => closed |
2023-01-27 07:39 | hgbot | Note Added: 0145894 | |
2023-01-27 07:39 | hgbot | Fixed in Version | => RR22Q4.2 |
2023-01-27 07:39 | hgbot | Note Added: 0145895 | |