Setting Filtering Expression Tree without condition function throws error if columns are not yet defined #15527
Labels
🐛 bug
Any issue that describes a bug
filtering
🧨 severity: medium
version: 19.1.x
✅ status: resolved
Applies to issues that have pending PRs resolving them, or PRs that have already merged.
Description
When specifying
filteringExpression
oradvancedFilteringExpressionsTree
, the user should be able to specify onlyconditionName
per spec without the need forcondition
now. But if there are notcolumns
yet defined for the grid it throws error, event if it works after the columns are added.Steps to reproduce
grid-external-filtering
democondition
property is used and leaveconditionName
from filtering expression trees.columns
to empty arraysetTimeout
to delay them. This works if the error is not thrown/removed from code.Result
The following error is thrown:
Expected result
There should be no errors and should be able to use
conditionName
only initially beforecolumns
are set.The text was updated successfully, but these errors were encountered: