Description
Since version 21.0.0 and this enhancement, the following issue is observed and reported by a customer in a remote data + remote ESF + uniqueColumnValuesStrategy setup.
Because of this portion in the applyFilter():
this.esf.grid.data.forEach(item => {
const fieldPaths = columnFieldPath(this.esf.column.field)
const itemValue = resolveNestedPath(item, fieldPaths);
if (typeof itemValue === "string" && selectedValues.has(itemValue.toLowerCase())) {
searchVal.add(itemValue);
}
});
, where the search values are mapped to the current available data in the grid, in the case where uniqueColumnValuesStrategy is used to fill the ESF values, search values not currently present in the data would be discarded.
In prior versions, this is working. See attachments - esf-lod-sample-20.zip - version 20.x.
Reproduction sample - esf-lod-sample-21.zip. The samples are identical and differ by the versions.
Framework
Angular
Angular Version
21.x
Ignite UI for Angular Version
21.2.x
Component / Area
Grid
Browser
Chrome
Operating System
No response
Command Not Working
Steps to Reproduce
- Open the project within the esf-lod-sample-21 archive,
npm i, ng s.
- Select some values in the ESF list for "ProductName" and apply the filter
- Only a value that is within the visible portion of the grid data gets filtered.
Actual Result
Expected Result
Perform same steps in esf-lod-sample-20.zip.
Filter is applied correctly. (Please note that due to the test OData endpoint limitation, the sample works for up to 20/30 selected values. So for testing, deselect all values, and select several in the ESF dialog).
Reproduction URL
No response
Attachments
esf-lod-sample-21.zip
esf-lod-sample-20.zip
Description
Since version
21.0.0and this enhancement, the following issue is observed and reported by a customer in a remote data + remote ESF + uniqueColumnValuesStrategy setup.Because of this portion in the
applyFilter():, where the search values are mapped to the current available data in the grid, in the case where
uniqueColumnValuesStrategyis used to fill the ESF values, search values not currently present in the data would be discarded.In prior versions, this is working. See attachments -
esf-lod-sample-20.zip- version 20.x.Reproduction sample -
esf-lod-sample-21.zip. The samples are identical and differ by the versions.Framework
Angular
Angular Version
21.x
Ignite UI for Angular Version
21.2.x
Component / Area
Grid
Browser
Chrome
Operating System
No response
Command Not Working
Steps to Reproduce
npm i,ng s.Actual Result
Expected Result
Perform same steps in esf-lod-sample-20.zip.
Filter is applied correctly. (Please note that due to the test OData endpoint limitation, the sample works for up to 20/30 selected values. So for testing, deselect all values, and select several in the ESF dialog).
Reproduction URL
No response
Attachments
esf-lod-sample-21.zip
esf-lod-sample-20.zip