Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0055205 | Openbravo ERP | A. Platform | public | 2024-04-15 19:18 | 2024-05-13 09:40 |
|
Reporter | ivazquez | |
Assigned To | Triage Platform Base | |
Priority | high | Severity | major | Reproducibility | sometimes |
Status | closed | Resolution | no change required | |
Platform | | OS | 5 | OS Version | |
Product Version | | |
Target Version | PR22Q1 | Fixed in Version | | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0055205: Product identifier problem |
Description | A customer tells us about a problem they encountered when exporting price data from a custom process they have created, but which makes use of Core's basic functions. The problem arises when not selecting a specific product and trying to export, so no result was obtained.
However, the expected file is generated when using the product ID as a filter and exporting.
The customer identified the problem as a query in which Core includes an incorrect identifier for the product name, which is marked as translatable. This causes multiple results to be returned, which causes an error and does not generate the file.
The customer also mentions that disabling the check for translated products allows the function to work, but is unsure of the implications for other functions that might also have product translations. |
Steps To Reproduce | Video of the customer reproducing the problem:
https://www.youtube.com/watch?v=p-RywBUmWOA [^]
-Go to the “Price List” window and then to the “Products” tab.
-Filter looking for a product by its name
-Without entering the register, staying in “grid” mode, clicking on the product, and clicking on the “Export price orders” button, you will see that it does nothing.
-On the other hand, if we filter by the product name (right-click on the product in the column “Product” and click on “Use as filter”) and we do the same procedure by clicking on the button “Export tariff orders” we see that the file is exported correctly.
We will provide the information to connect to the customer's environment through google chat. |
Proposed Solution | |
Additional Information | |
Tags | No tags attached. |
Relationships | |
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2024-04-15 19:18 | ivazquez | New Issue | |
2024-04-15 19:18 | ivazquez | Assigned To | => Triage Platform Base |
2024-04-15 19:18 | ivazquez | Modules | => Core |
2024-04-15 19:18 | ivazquez | Triggers an Emergency Pack | => No |
2024-04-15 19:23 | ivazquez | Description Updated | bug_revision_view_page.php?rev_id=27824#r27824 |
2024-04-15 19:43 | Practics | Issue Monitored: Practics | |
2024-04-22 16:10 | ivazquez | Note Added: 0163540 | |
2024-05-02 15:30 | AugustoMauch | Note Added: 0164015 | |
2024-05-02 15:30 | AugustoMauch | Status | new => feedback |
2024-05-02 15:35 | Practics | Note Added: 0164016 | |
2024-05-03 15:35 | ivazquez | Steps to Reproduce Updated | bug_revision_view_page.php?rev_id=27939#r27939 |
2024-05-03 15:36 | ivazquez | Status | feedback => new |
2024-05-07 08:41 | AugustoMauch | Note Added: 0164126 | |
2024-05-07 08:41 | AugustoMauch | Status | new => feedback |
2024-05-13 09:40 | AugustoMauch | Note Added: 0164474 | |
2024-05-13 09:40 | AugustoMauch | Status | feedback => closed |
2024-05-13 09:40 | AugustoMauch | Resolution | open => no change required |
Notes |
|
|
Dear Team,
Any news?
Regards,
Ignacio Vazquez |
|
|
|
Hello Ignacio,
I am sorry but with no steps to reproduce this issue is not actionable. |
|
|
|
Hello Augusto
You have the steps in the video |
|
|
|
Hello,
I am able to reproduce the problem in the customer environment, but until I have steps to reproduce to execute it locally I am not going to be able to debug why the query is being malformed, and whether the problem is in Openbravo's or in the client's side.
Please keep this issue in feedback without an SLA until the issue is actionable the way I mentioned |
|
|
|
Problem confirmed to be on the custom code. |
|