Openbravo Issue Tracking System - Retail Modules |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0051478 | Retail Modules | Retail API | public | 2023-01-11 16:00 | 2023-01-27 16:10 |
|
Reporter | nicola_uva | |
Assigned To | ranjith_qualiantech_com | |
Priority | urgent | Severity | major | Reproducibility | have not tried |
Status | closed | Resolution | fixed | |
Platform | | OS | 5 | OS Version | |
Product Version | | |
Target Version | RR23Q1 | 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 | 0051478: BP API -Wehen we create BP If we have two greetings with same name (different org) an error happen |
Description | When we have two greetings with same name (different org) an error happen. Below the error:
"Error while importing an item: query did not return a unique result: 2".
See the full stack trace attached
In addition, when a new civility is sent, it seems to be created in the organization of the user sending the JSON (IntegrationUser) and not on the organization of the business partner inside the JSON |
Steps To Reproduce | Using postman add the request attached |
Proposed Solution | The mapping should be able to define properly how to identify records univocally |
Additional Information | |
Tags | No tags attached. |
Relationships | blocks | defect | 0051333 | pi | closed | ranjith_qualiantech_com | BP API -Wehen we create BP If we have two greetings with same name (different org) an error happen |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2023-01-27 10:40 | marvintm | Type | defect => backport |
2023-01-27 10:40 | marvintm | Target Version | pi => RR23Q2 |
2023-01-27 10:40 | marvintm | Target Version | RR23Q2 => RR23Q1 |
2023-01-27 11:48 | hgbot | Note Added: 0145930 | |
2023-01-27 16:10 | hgbot | Resolution | open => fixed |
2023-01-27 16:10 | hgbot | Status | scheduled => closed |
2023-01-27 16:10 | hgbot | Note Added: 0145945 | |
2023-01-27 16:10 | hgbot | Note Added: 0145946 | |