| T O P I C R E V I E W |
| fdranguet |
Posted - 08/01/2019 : 09:12:25
Hello,
I just noticed that when using the Bottom Count function on OLAP reports, the function "NonEmptyCrossJoin" will be used even if it is unticked from the report options. This does not happen with Top Count, where the MDX is correct. For instance, when using Top Count, this kind of MDX is generated:
TopCount(DISTINCT({AddCalculatedMembers({[Customer].[Customer Group].[Customer Group].AllMembers})}),5,([Invoice Date].[Invoice Year].&[2019], [Measures].[Std Marg var to Previous Year - Mnth]))
With Bottom Count, on the same report (where "NonEmptyCrossJoin" is unticked on the options), we are getting:
BottomCount(NonEmptyCrossjoin(DISTINCT({AddCalculatedMembers({[Customer].[Customer Group].[Customer Group].AllMembers})})),5,([Invoice Date].[Invoice Year].&[2019], [Measures].[Std Marg var to Previous Year - Mnth])))
This issue is urgent enough for us; could you please check it and send us an hotfix if hopefully it can be fixed easily? Thanks.
Regards,
François Dranguet
Information Manager
Scott Bader Group |
| 1 L A T E S T R E P L I E S (Newest First) |
| admin |
Posted - 08/01/2019 : 20:41:08
This is a feature, not a bug. The idea is to show bottom-n members that have data. For example, you have sales for first 6 months out of 12. Without NonEmptyCrossjoin you will see last two months without sales data. This is not an issue for top-n.
From Main.js, Line 408
function NonEmptyCrossjoin2(sDim){
if (sTopOnlyFormula.substr(0,6)=="Bottom"){
return "NonEmptyCrossjoin(" + sDim + ")";
}else{
return sDim;
}
}
|
|
|
Report Portal
