Openbravo Issue Tracking System - Openbravo ERP | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0037931 | Openbravo ERP | 00. Application dictionary | public | 2018-02-15 12:32 | 2022-02-01 08:05 |
| Reporter | eduardo_Argal | ||||
| Assigned To | Triage Platform Base | ||||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | acknowledged | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | |||||
| Target Version | 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 | 0037931: Parameter replacement not working for hqlwhereclause in a tab when tab is based on a HQLQuery table | ||||
| Description | when creating a window based on a HQLQuery table, if you try to define a whereclause based on the selected row or just add any parameter to that expression (@xxxx@) those parameters are not being replaced with the proper value. This behavior works fine when the table used to build the tab is a standard table (when it maps to a DB table) while it fails when using HQL based tables. This problem can be workarounded by defining a transformer java class to modify the hql and replace those values. | ||||
| Steps To Reproduce | 1) Create an hql table. For example based on a simple hql query to ProductCategory (select cat.id, cat.name from ProductCategory cat) 2)Add some columns: id, name 3) Create a tab below Product window / Product tab: Prueba. this tab is based on previous table. add a hqlwhereclasuse ("not exists (from Product p where p.productCategory.id = cat.id and p.id = @Product.id@)") 4) Create fields when query is launched you will see an error related to having "@" in final query although it should have been replaced. | ||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2018-02-15 12:32 | eduardo_Argal | New Issue | |||
| 2018-02-15 12:32 | eduardo_Argal | Assigned To | => platform | ||
| 2018-02-15 12:32 | eduardo_Argal | Modules | => Core | ||
| 2018-02-15 12:32 | eduardo_Argal | Triggers an Emergency Pack | => No | ||
| 2018-06-15 11:28 | alostale | Status | new => acknowledged | ||
| 2022-02-01 08:05 | alostale | Assigned To | platform => Triage Platform Base | ||
| There are no notes attached to this issue. |