Hi Aleksandar, 

I will proceed with setting the status of this item to Declined. Of course, if you have any concerns or any other assistance is needed, feel free to open a new support thread.

All the best,
Stefan

Hello Aleksandar,

I might be missing something. In case you add a SortDescription in the ICollectionView for the StadiumCapacity property, you are sorting the "StadiumCapacity" column. This is irrelevant to whether some of the other columns has its SortMemberPath set to point to the StadiumCapacity property. On the other hand, when you sort another column that has its SortMemberPath set, you are basically telling this exact column to be sorted by another property. This is the expected behavior. From what I understand from your posts, you expect the inverted behavior, i.e. all columns that have their SortMemberPath pointing to the StadiumCapacity to reflect in the UI when a "StadiumCapacity SortDescription" is added. Note, that such behavior would not be possible to achieve.

Regards,
Stefan

Hi Aleksandar,

Thank you for this clarification. 

This would actually be the expected behavior. The SortMemberPath is intended to alter the default sorting only when the actual column is sorted. In other words said, it works only when the grid is sorted over the column on which the SortMemberPath is applied to. In this case this would be the first column. 

Hopefully, this clarifies your concerns.
Stefan

Hello Aleksandar,

Firstly, thank you for your patience. We were on a tight schedule due to the upcoming release, so please excuse us for the delayed reply. 

I tested the behavior of the control and was not able to replicate such malfunction. Attached to my post you can find the sample application I used for testing. Can you please clarify how exactly is the problem reproduced? Am I missing something?

Thanks in advance for your cooperation.
Stefan