Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0055222 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
defect | [Retail Modules] Retail API | major | have not tried | 2024-04-17 14:30 | 2024-04-18 10:37 | |||
Reporter | azzeddine_meftoh | View Status | public | |||||
Assigned To | Retail | |||||||
Priority | normal | Resolution | no change required | Fixed in Version | ||||
Status | closed | Fix in branch | Fixed in SCM revision | |||||
Projection | none | ETA | none | Target Version | ||||
OS | Any | Database | Any | Java version | ||||
OS Version | Database version | Ant version | ||||||
Product Version | main | SCM revision | ||||||
Review Assigned To | ||||||||
Regression level | ||||||||
Regression date | ||||||||
Regression introduced in release | ||||||||
Regression introduced by commit | ||||||||
Triggers an Emergency Pack | No | |||||||
Summary | 0055222: Price API - importing price for deactivated product | |||||||
Description | When importing a price for a deativated product we get the error : ERROR: duplicate key value violates unique constraint "m_productprice_pricelist_ve_un" | |||||||
Steps To Reproduce | deactivate a product import a price for this product with the API | |||||||
Tags | No tags attached. | |||||||
Attached Files | ||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Notes | |
(0163352) adrianromero (manager) 2024-04-18 10:37 |
This is the expected behaviour when trying to import any Openbravo entity with the same keys as another existing deactivated entity. Deactivated entities are maintanined in the database for reference and reporting purposes but cannot be used in new processes or selected, etc... and as consequence: * Deactivated records cannot be updated by the import API and kept deactivated * Deactivated records cannot be reactivated and updated as a result of an import API request * Openbravo cannot create a new activated record due the database constraints that can end in an inconsistent database with two records with the same keys, one activated and the other deactivated. |
Issue History | |||
Date Modified | Username | Field | Change |
2024-04-17 14:30 | azzeddine_meftoh | New Issue | |
2024-04-17 14:30 | azzeddine_meftoh | Assigned To | => Triage Platform Conn |
2024-04-17 14:30 | azzeddine_meftoh | Triggers an Emergency Pack | => No |
2024-04-17 14:49 | victor_perez | Severity | minor => major |
2024-04-18 10:29 | jorgewederago | Assigned To | Triage Platform Conn => Retail |
2024-04-18 10:29 | jorgewederago | Status | new => acknowledged |
2024-04-18 10:37 | adrianromero | Note Added: 0163352 | |
2024-04-18 10:37 | adrianromero | Status | acknowledged => closed |
2024-04-18 10:37 | adrianromero | Resolution | open => no change required |
Copyright © 2000 - 2009 MantisBT Group |