I think the link you posted is the link to this article?

If we have the following class...

class A

{

B Child {get; set;}

}

class B

{

int Value {get; set;}

}

in code how can I bind an infragistics Field to the Value field of class B, so the binding path would be Child.Value I think.

Cheers

Jonathan

Yea, we are using UnboundField, but the filtering and grouping performance is horrendous with UnboundFields, also when using UnboundField you cannot utilize...

• FilterEvaluationMode="UseCollectionView"
• GroupByEvaluationMode="UseCollectionView"
• SortEvaluationMode="UseCollectionView"

It feels like a bug that UnboundFields perform so poorly. Is there a solution for v14.1 or can we raise a bug please?

Note once we move to regular fields by hacking our domain model so that there are not binding paths and using the above xamdatagrid settings, performance becomes quite good, however the hacks we put in our domain model are no real solution, we just tried it to see what difference removing the UnboundFields would make.

UnboundField seems to reevaluate the binding everytime we group or sort etc, regardless of us setting the binding mode to OneTime. Performance is so bad.

Cheers

Jonathan

Hello Robson,

I am just checking if there is anything else I can do for you.

Yes. We dont utilize the CollectionView attributes with UnboundFields as they don't work. I would be interested in why the UnboundField performance is so shockingly bad though for sorting, grouping and filtering?

Hello,

I am just checking if you require any further assistance on the matter.