Notes |
|
|
I have attached a partial fix for this issue that fixes the problem when using the selector is defined using a custom HQL query. This fix relies on the fix attached to issue 16623. |
|
|
|
->rc7 as rc6 freezing today and full fix will not be ready today. |
|
|
|
Marking as related with all the other known bugs about datasource/filtering/performance |
|
|
|
After investigating further there is one additional change needed to make a custom selector able to filter by the current value.
To add any field to the where clause it needs to have "Clause Left Part" defined so that the custom query selector can generate the HQL. This means the field used as the selector value needs to have the left clause part, even if it is not in the grid view
Additional changes in updated patch
- Change display logic of Clause Left Part field to be displayed for all fields when using custom logic (instead of just fields that are in grid)
- Add clause left part for business partner selector identifier field |
|
|
|
I have attached another patch that fixes the issue for selectors using standard json data source. This patch addresses the two scenarios described in the steps to reproduce above |
|
|
(0036896)
|
hgbot
|
2011-05-12 14:58
|
|
Repository: erp/devel/pi
Changeset: 1b57600d569190c29fb3e726f1aa86b7c06a0d94
Author: Martin Taal <martin.taal <at> openbravo.com>
Date: Thu May 12 14:57:37 2011 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/1b57600d569190c29fb3e726f1aa86b7c06a0d94 [^]
Fixes issue 16611: Initial request done by UI selector element in form view does not use any filters or paging
---
M modules/org.openbravo.client.application/web/org.openbravo.client.application/js/ob-view-form.js
M modules/org.openbravo.client.application/web/org.openbravo.client.application/js/ob-view-grid.js
M modules/org.openbravo.userinterface.selector/web/org.openbravo.userinterface.selector/js/ob-selector-item.js
---
|
|
|
(0036900)
|
hgbot
|
2011-05-12 15:47
|
|
Repository: erp/devel/pi
Changeset: 184bd464aefe4b0e0c3f658fc9d4fad4e74c319b
Author: Martin Taal <martin.taal <at> openbravo.com>
Date: Thu May 12 15:46:50 2011 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/184bd464aefe4b0e0c3f658fc9d4fad4e74c319b [^]
Related to issue 16611: Initial request done by UI selector element in form view does not use any filters or paging
---
M modules/org.openbravo.client.application/web/org.openbravo.client.application/js/ob-view-grid.js
M modules/org.openbravo.userinterface.selector/web/org.openbravo.userinterface.selector/js/ob-selector-item.js
---
|
|
|
|
|
|
|
|
|
|
Re-opened, as same requests with limit are still (or again) happening as described in the bug-report. |
|
|
|
Note: when waiting for the slow coombo-query to finish, then opening the selector grid...
Then some data is displayed directly
but the two applied filter are not rendered in the filter area
in background 2* the same request without limit is fired
after waiting for those to also finish the filter is rendered and used |
|
|
(0037051)
|
hgbot
|
2011-05-17 09:50
|
|
Repository: erp/devel/pi
Changeset: 0bb5ac454ee19bac63d045ab4e047f4dd2bc7532
Author: Martin Taal <martin.taal <at> openbravo.com>
Date: Tue May 17 09:48:59 2011 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/0bb5ac454ee19bac63d045ab4e047f4dd2bc7532 [^]
Fixes issue 16611: Initial request done by UI selector element in form view does not use any filters or paging
---
M modules/org.openbravo.client.application/web/org.openbravo.client.application/js/ob-grid.js
M modules/org.openbravo.client.application/web/org.openbravo.client.application/js/ob-view-form.js
M modules/org.openbravo.userinterface.selector/web/org.openbravo.userinterface.selector/js/ob-selector-item.js
---
|
|
|
|
Tested in pi/pgsql (rev: a364fc44064e). Working fine now. When showing either new or edit in grid or edit mode a combobox for a i.e. product selector is no longer doing one request for all record in its table without any filter or limit.
Instead only a data request is fired when really using either the dropodwn of the combo or the popup of the selector. that requests is doing its normal filtering/paging as expected. |
|
|
|
|