Openbravo Issue Tracking System - Retail Modules | ||||||||||||
| View Issue Details | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | |||||||
| 0049846 | Retail Modules | Contact Info for Product | public | 2022-07-19 15:34 | 2022-08-03 08:03 | |||||||
| Reporter | jose_duque | |||||||||||
| Assigned To | radhakrishnan | |||||||||||
| Priority | normal | Severity | major | Reproducibility | always | |||||||
| Status | closed | Resolution | duplicate | |||||||||
| Platform | OS | 30 | OS Version | Openbravo Appliance 14.04 | ||||||||
| Product Version | ||||||||||||
| Target Version | Fixed in Version | |||||||||||
| 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 | 0049846: API issue - When updating the price through an API, the audit fields are not updated | |||||||||||
| Description | When we do a change to a pricelist, updating the existing prices of a price list version, the audit fields of those prices are not changed accordingly so we don't know when was the last update of the price, and the incremental refresh in the POS doesn't pick the new prices up. | |||||||||||
| Steps To Reproduce | 1. Change a price through the /PriceList endpoint. 2. Check the updated by and updated date audit fields of that particular price in the backoffice They won't change according to the new update done through the API. When the update is done through the backoffice the audit fields are correctly updated. | |||||||||||
| Proposed Solution | ||||||||||||
| Additional Information | ||||||||||||
| Tags | No tags attached. | |||||||||||
| Relationships |
| |||||||||||
| Attached Files | ||||||||||||
| Issue History | ||||||||||||
| Date Modified | Username | Field | Change | |||||||||
| 2022-07-19 15:34 | jose_duque | New Issue | ||||||||||
| 2022-07-19 15:34 | jose_duque | Assigned To | => Retail | |||||||||
| 2022-07-19 15:34 | jose_duque | Triggers an Emergency Pack | => No | |||||||||
| 2022-07-19 15:34 | jose_duque | Issue generated from | 0049844 | |||||||||
| 2022-07-19 17:48 | jose_duque | Issue cloned | 0049849 | |||||||||
| 2022-07-29 12:12 | marvintm | Type | design defect => defect | |||||||||
| 2022-08-01 06:45 | marvintm | Status | new => scheduled | |||||||||
| 2022-08-01 06:45 | marvintm | Assigned To | Retail => radhakrishnan | |||||||||
| 2022-08-03 07:00 | marvintm | Description Updated | bug_revision_view_page.php?rev_id=24574#r24574 | |||||||||
| 2022-08-03 07:00 | marvintm | Steps to Reproduce Updated | bug_revision_view_page.php?rev_id=24576#r24576 | |||||||||
| 2022-08-03 07:58 | alostale | Status | scheduled => closed | |||||||||
| 2022-08-03 08:03 | alostale | Relationship added | duplicate of 0049791 | |||||||||
| 2022-08-03 08:03 | alostale | Resolution | open => duplicate | |||||||||
| There are no notes attached to this issue. |