| Author |
 Topic  |
|
|
fdranguet
France
81 Posts |
 Posted - 01/24/2020 : 02:40:04
|
Hello,
would it be possible to configure ReportPortal so that when you use sorting feature (by clicking on the header of the column), and if you are sorting on a dimension attribute, it would rely on the key of that attribute to do the sort and not the name - or even better, it would check the "OrderBy" property of the attribute to decide whether to sort by name or by key?
That would fix for instance some of the issues our users are having when sorting on a date column (which is displaying with format DD/MM/YYYY on name but has YYYYMMDD format on key to enable proper ordering).
Thanks.
Regards,
François Dranguet
Information Manager
Scott Bader Group |
|
|
admin
1637 Posts |
Posted - 01/24/2020 : 14:37:36
|
| Currently, dimension sorting happens on Member name (Dim1.CurrentMember.Name). Would you like a report-level option that would let you sort dimension on ID (Dim1..CurrentMember.Properties("MEMBER_KEY"))? |
 |
|
|
fdranguet
France
81 Posts |
Posted - 02/03/2020 : 09:57:01
|
Hello,
sorry for the delay - yes, adding a report level option to enable sorting with "MEMBER_KEY" would be one way to cover my requirement. But I am not sure this would be ideal; I think the best way, which could work in every situation and without changing any report settings at each report level, would be to rely on the "OrderBy" property of the attribute itself: suppose on the OLAP cube you are connected to, you have a "Customer" dimension with two attributes, "Customer Creation Date" and "Customer Name". The first one has "OrderBy" property set to "Key", while the second one has "OrderBy" property set to "Name": ideally ReportPortal should use the member key when sorting on the first attribute, and member name when sorting on the second one.
Is this doable? Many thanks!
Regards,
François Dranguet
Information Manager
Scott Bader Group |
|
|
|
admin
1637 Posts |
Posted - 02/05/2020 : 10:26:46
|
CurrentMember.Properties("OrderBy") is not an Intrinsic Member Property. Also the value of OrderBy cannot be discovered from SSAS. On the plus side, You usually do not need to know the value of this property because the dimension members are automatically sorted by it.
In any case, please try this patch. It will let give you OLAP report option to sort by MEMBER_KEY.
1. Download and unzip: http://reportportal.us/upload73/upload/rp_203_olap_Options.zip
2. Backup old file and copy the unzipped file to:
ReportPortal\olap\Options.aspx
ReportPortal\olap\Options.js
ReportPortal\olap\script\main.js
3. Clear browser cache |
|
|
|
fdranguet
France
81 Posts |
Posted - 02/14/2020 : 03:25:03
|
Hello,
sorry for the delay again. Thanks for the detailled answer and the patch; I tested this and can confirm it will be all good - except for a very slight bit which is that the sort does not take into account the type of the key (integer, string, ...), thus when sorting integers for instance, it does sort in order "1, 10, 11, 2, 3, ..." instead of "1, 2, 3, 10, 11, ...".
The fix seems simple enough: you use ".CurrentMember.Properties("MEMBER_KEY")" to get the key, if you actually change this for ".CurrentMember.Properties("KEY",TYPED)" it does work perfectly (it seems ".CurrentMember.Properties("MEMBER_KEY",TYPED)" does not work thus we would need to use "KEY" instead of "MEMBER_KEY").
Could you please do that simple change and post the new version for this patch? Many thanks!
Regards,
François Dranguet
Information Manager
Scott Bader Group |
|
|
|
admin
1637 Posts |
|
|
fdranguet
France
81 Posts |
Posted - 02/21/2020 : 05:28:18
|
Hello,
I confirm this second hotfix is working perfectly for us. Many thanks for your help with that and your quick reaction time!
Regards,
François Dranguet
Information Manager
Scott Bader Group |
|
|
| |
Topic |
|
|
|
Report Portal
OLAP reports sorting feature
