Context:
In our application we use fetch criteria that contain fields that are not in the datasource. (these criteria are processed using custom fetches and dmi).
The fetched client side records don’t match all these criteria, since they don’t contain values for some of these criterions).
Problem:
This causes the records to disappear on update (which we don’t want).
Semi workaround:
We’re aware that neverDropRowsOnUpdate exists and works, but that’s a bit too strict: users can also filter on actual datasource fields and then we do want the records to drop after an update if they no longer satisfy the user filter).
We also saw that neverDropRowsOnUpdate does not work for a TreeGrid
(since setDataProperties needs a Tree and there is no such method there)
Question:
Is there a possibility to add an attribute like doNotTakeIntoAccountNonDataSourceCriteriaToMatchRecordsClientSide, or does such a thing exist already?
Environment:
Using SC_SNAPSHOT-2011-08-02/PowerEdition Deployment 2011-08-02
In our application we use fetch criteria that contain fields that are not in the datasource. (these criteria are processed using custom fetches and dmi).
The fetched client side records don’t match all these criteria, since they don’t contain values for some of these criterions).
Problem:
This causes the records to disappear on update (which we don’t want).
Semi workaround:
We’re aware that neverDropRowsOnUpdate exists and works, but that’s a bit too strict: users can also filter on actual datasource fields and then we do want the records to drop after an update if they no longer satisfy the user filter).
We also saw that neverDropRowsOnUpdate does not work for a TreeGrid
(since setDataProperties needs a Tree and there is no such method there)
Question:
Is there a possibility to add an attribute like doNotTakeIntoAccountNonDataSourceCriteriaToMatchRecordsClientSide, or does such a thing exist already?
Environment:
Using SC_SNAPSHOT-2011-08-02/PowerEdition Deployment 2011-08-02
Comment