[Mondrian] DRILLTHROUGH behavior change in lagunitas

Julian Hyde jhyde at pentaho.com
Thu Mar 7 12:52:37 EST 2013

On Mar 5, 2013, at 11:52 PM, Ati Rosselet <ati.rosselet at gmail.com<mailto:ati.rosselet at gmail.com>> wrote:

One note on the new behaviour.   With the old system, I had implemented an "additionalColumns setting to the base fact table definition that allowed me to specify additional columns (with i18n column name aliases) to be added to the drillthrough request.  This was in order to display those column values that contain pertinent business data (comments, booking codes etc) that although important, were not relevant to the actual cube data displayed (e.g. only of use when needing to understand the source of a specific data row), and are often really not aggregation friendly (i.e. almost unique strings etc).   Is there a similar function provided, or could there be one for this new method?  We find that customers use this feature quite frequently (especially controllers like to see the "row" that the data comes from).

Does http://jira.pentaho.com/browse/MONDRIAN-1463 cover what you're asking for?

Could you maybe add the other columns as a non-visible dimension (they could still be referenced in the RETURN clause).


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pentaho.org/pipermail/mondrian/attachments/20130307/65186aaf/attachment.html 

More information about the Mondrian mailing list