Project:
| View Revisions: Issue #33478 | [ Back to Issue ] | ||
| Summary | 0033478: implicit filters not applied in updated instances with grid configuration | ||
| Revision | 2016-07-14 12:54 by alostale | ||
| Steps To Reproduce | 1. Install a fresh Openbravo in PR16Q2 2. Activate this instance 3. Open Sales Order window 4. Change grid layout: ie. sort by Document Number 5. Check in Preferences window there is a "Grid Configuration" preference for this window. 6. Update to PR16Q3 7. Open sales order window * Transactional implicit filter message appears as applied in UI -> OK * The request to populate the datasource has the isImplicitFilterApplied set to false, which causes the grid not to be filtered -> ERROR == Alternativelly == 1. In a pi professional instance, emulate steps 1 to 6 by: 1.1 Create a new preference - Property: Grid Configuration - Visibility: Current session settings - Value: http://pastebin.com/raw/RqA6e3Dc [^] 1.2 Relogin 2. Issue explained in step 7 can be reproduced |
||
| Revision | 2016-07-14 12:52 by alostale | ||
| Steps To Reproduce | 1. Install a fresh Openbravo in PR16Q2 2. Activate this instance 3. Open Sales Order window 4. Change grid layout: ie. sort by Document Number 5. Check in Preferences window there is a "Grid Configuration" preference for this window. 6. Update to PR16Q3 7. Open sales order window * Transactional implicit filter message appears as applied in UI -> OK * The request to populate the datasource has the isImplicitFilterApplied set to false, which causes the grid not to be filtered -> ERROR == Alternativelly == 1. In a pi professional instance, emulate steps 1 to 6 by: 1.1 Create a new preference - Property: Grid Configuration - Visibility: Current session settings - Value: http://pastebin.com/RqA6e3Dc [^] 1.2 Relogin 2. Issue explained in step 7 can be reproduced |
||
| Revision | 2016-07-14 12:52 by alostale | ||
| Description | Instances updated from a previous release that had "Grid Configuration" preferences with transactional filters applied, do not apply transactional filters when fetching data though in the UI the message informing the transactional filter is applied is seen. The problem is caused because old grid configuration saved in their state whereClause as string and now the code expects it to be a boolean filterClause:\" ( e.updated > @transactionalRange@ or e.processed = 'N' ) \" |
||
| Revision | 2016-07-14 12:40 by alostale | ||
| Steps To Reproduce | 1. Install a fresh Openbravo in PR16Q2 2. Activate this instance 3. Open Sales Order window 4. Change grid layout: ie. sort by Document Number 5. Check in Preferences window there is a "Grid Configuration" preference for this window. 6. Update to PR16Q3 7. Open sales order window * Transactional implicit filter message appears as applied in UI -> OK * The request to populate the datasource has the isImplicitFilterApplied set to false, which causes the grid not to be filtered -> ERROR |
||
| Revision | 2016-07-14 12:40 by alostale | ||
| Description | Instances updated from a previous release that had "Grid Configuration" preferences with transactional filters applied, do not apply transactional filters when fetching data though in the UI the message informing the transactional filter is applied is seen. | ||
| Revision | 2016-07-14 12:34 by alostale | ||
| Steps To Reproduce | 1. clone https://code.openbravo.com/erp/pmods/org.openbravo.externaldata.integration/ [^] in rev 2913f243 2. Open EDL Request window 3. Check that: * Transactional implicit filter message appears as applied in UI -> OK * The request to populate the datasource has the isImplicitFilterApplied set to false, which causes the grid not to be filtered -> ERROR |
||
| Revision | 2016-07-14 12:34 by alostale | ||
| Description | Under certain (still undefined) circumstances, transactional implicit filters are displayed as applied in UI, though they are not actually applied in backend filtering. This behavior has been observed in external module development, but not in OB3 distribution. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |