Kbase P48690: Dynamics: Filter settings not re-applied properly when resta
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/24/2003 |
|
Status: Unverified
FACT(s) (Environment):
Dynamics 2.0A02
SYMPTOM(s):
Filter (BrowserToolbar/Filter button) not re-applied correctly when restarting container or session
Filtering on 2nd table of SDO with BrowserToolbar/filter
2nd table of SDO is joined with OUTER-JOIN in the design query (baseQuery)
CAUSE:
Some custom code from a container applies a global filter (such as on login company) against the first table of the SDO at the same time as the BrowserToolbar filter is applied. This results in two filters that do not collaborate well.
Indeed, by filtering with the BrowserToolbar/filter against the 2nd table, then the OUTER-JOIN option in the query for this 2nd table has to be removed, otherwise the filter has not wanted effect. This is normally well done by the BrowserToolbar/filter. However, applying another filter from custom code can put the OUTER-JOIN back for the 2nd table (as it is in the baseQuery).
FIX:
Make sure that the SDO is ready with a global filter before the BrowserToolbar/filter is processed, so the unwanted OUTER-JOIN will be removed. You shall implement code to achieve the global filter in the SDO itself (or super procedure), or with a subclassed SDO.
See also Chapter 4.2 'Applying Global Filters To Your Data' in the Progress Dynamics Programming Handbook.