Hi,
1) We would like to be able to sort on tennors (eg. 5 years, 3 months, 10 days). The data comes in as (2Y, 1Y,6M, 3M, 1M, 10d, 5d, 1d etc) Is it possible to apply a custom sort. I have attached an example screenshot with year tennors as they appear. In the example below we would like it to be (60Y, 50Y, 40Y, 30Y .....etc).
2) Additionaly we would like to enable to user to reposition the Currency columns or product rows similar to the Field Chooser drag drop indexing in the XamDataGrid. How would we go about providing such functionality.
3) Finally we would like to display "N/A" for measures that are aggregated. In our case we don't want to show data if it is aggregated. Therefore we only want to show data when the user has drilled down to a result count of 1. I can see that we can specify an aggregation calculation to be Count and can see which cells are made up of more than one value, however how can we display the value only when it is not an aggregate, otherwise "N / A". Many Thanks
Hi Valerie,
Thanks for the update. Looking forward to trying it out once it gets released.
Regards,Nick
Hello Nick,
There have been requests for this functionality, therefore we will be adding this back in the next service release for 11.1 and 11.2 with some changes.
The DataSourceBase.PreserveMembersOrder property will be changed to public with a default of true. Therefore you will need to set this property to false to use the OrderByKeyExpression.
Here are more details on the changes from engineering:
1. DataSourceBase.PreserveMembersOrder property is changed to be public with default value of true, that provides the same behavior we have with the current implementation.
2. This behavior can be overridden for specific levels as adding a LevelSortDirection instance to DataSourceBase.LevelDefaultSortDirections collection; that will change the initial appearance of these levels
<olap:FlatDataSource.LevelDefaultSortDirections> <olap:LevelSortDirection LevelUniqueName="[Date].[Date].[Years]" SortDirection="Descending"/> <olap:LevelSortDirection LevelUniqueName="[City].[City].[City]" SortDirection="Ascending"/> </olap:FlatDataSource.LevelDefaultSortDirections>
3. When DataSourceBase.PreserveMembersOrder is set to false, the initial direction depends on DataSourceBase.LevelFirstSortDirection value, unless the sort direction is specified using DataSourceBase.LevelDefaultSortDirections collection
This feature will be available for both flat data and XMLA.
Please let me know if you have any questions.
Sincerely,ValerieDeveloper Support Engineer Infragisticswww.infragistics.com/support
Our datasource sort is getting more and more complicated as we want to sort more than one field at a time. The custom sort functionality in 11.1 used to work perfect for us and i am surprised that it was taken out. Is this a bug that will be resolved in future updates as we found the custom sort per field very useful.
You should sort the datasource before assigning it to the grid.
Hi Plamen,
We were using 11.1.20111.1002. How can we acheive the same behaviour using 11.2, i.e. apply the custom sort.
Thanks,
Nick