Hi,
it seems filtering isn't working when the column has a uniquename that is different from the field name. No filtering happens regardless of type of filter, isreadonly etc. The issue can easily be reproduced with your hard-coded demo data.
Can you confirm this or am I doing something wrong? Is there a workaround?
Thx & regards
Frank
it seems filtering isn't working when the column has a uniquename that is different from the field name. No filtering happens regardless of type of filter, isreadonly etc. The issue can easily be reproduced with your hard-coded demo data.
Can you confirm this or am I doing something wrong? Is there a workaround?
Thx & regards
Frank
3 Answers, 1 is accepted
0
Hi frankd,
Just tested and it seems that filter expressions are applied and working. I tested with a column for which the FieldName is "ContactName" and UniqueName is "column2" and it has a filter expression that is set in design time.
However, you should check if you have values serialized for the FieldAlias property, because if its value is different from the FieldName property, the filter expressions may not work.
If that is not the case it will be most helpful if you can send us a sample project that demonstrates the issue or at least give us more detail about your case. You can do so in a support ticket.
Greetings,
Jordan
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Just tested and it seems that filter expressions are applied and working. I tested with a column for which the FieldName is "ContactName" and UniqueName is "column2" and it has a filter expression that is set in design time.
However, you should check if you have values serialized for the FieldAlias property, because if its value is different from the FieldName property, the filter expressions may not work.
If that is not the case it will be most helpful if you can send us a sample project that demonstrates the issue or at least give us more detail about your case. You can do so in a support ticket.
Greetings,
Jordan
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Frank
Top achievements
Rank 1
Rank 1
answered on 09 Dec 2008, 02:50 PM
Jordan,
thanks for looking into this.
I have a column with FieldAlias = FieldName = UniqueName = 'PRO_CODE'. At run-time I can set filter criteria OK, everything is fine.
Once I change UniqueName to, say, 'PRO_CODE_Column', run-time filtering on this column stops working (remains working for all other columns). If I revert to PRO_CODE, erverything is fine again.
The difference between my scenario and the one you tested seems to be 'design time' vs. 'run time' - I haven't checked design time filtering yet.
For the moment I have re-named my columns, but I believe the issue is still there.
Thx & regards
FrankD
thanks for looking into this.
I have a column with FieldAlias = FieldName = UniqueName = 'PRO_CODE'. At run-time I can set filter criteria OK, everything is fine.
Once I change UniqueName to, say, 'PRO_CODE_Column', run-time filtering on this column stops working (remains working for all other columns). If I revert to PRO_CODE, erverything is fine again.
The difference between my scenario and the one you tested seems to be 'design time' vs. 'run time' - I haven't checked design time filtering yet.
For the moment I have re-named my columns, but I believe the issue is still there.
Thx & regards
FrankD
0
Accepted
Hi frankd,
This issue is due to the complex dependencies between properties like FieldName, UniqueName and FieldAlias.
We are aware of this issue and it will be fixed in the next release.
Greetings,
Jordan
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
This issue is due to the complex dependencies between properties like FieldName, UniqueName and FieldAlias.
We are aware of this issue and it will be fixed in the next release.
Greetings,
Jordan
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.