Still looking for a crafty solution to this formatting issue.
(Note - report is based on a cube, not a relational database)
Thanks for the offer to help!
Unfortunately, I don't believe I can grab an extract of the data, when referencing a cube, as the data source...
If that's possible, I've not seen how.
So far, I haven't found a way to dynamically change the dimension level in a title block, without putting each dimension in. If I add several generations of "customer name", say 7 generations for example, and separate them with a "-". I end up with a title that looks like this.
- - - - Customer ABC - -
Where a report user has selected "Customer ABC" from a quick filter.
If I leave the customer dimension at the default level i.e. <Customer>, it only works for the highest level of data.
It's quite frustrating... I appreciate any suggestions.
I see where you're headed with this one... however, when using a cube, you don't get the option to limit to relevant values on all dimensions.
It appears that option is only available for a time series. (i.e. the "Year" dimension)
Hi Jason. I'm having exactly the same problem and am also connecting to a cube. User can select date or month from filter but I have no way to show them on the graph what dates they are looking at. Only option seems to be to insert the Dimension of 'Date' in the title and this shows as every date in the cube e.g. "2012-01-01, 2012-01-02 and 452 more" and not even the context of the filter. Very frustrating. Did you ever find a solution?
Here's my attempt at a solution. It's not completely working, but it might spark some ideas. The basic idea is to create a view for the "Title" that simply is a list of all the filter values as a non-cartesian plot type. A variation of that attempts to filter to the First value of the filter. However, it is very brittle and the table calculation breaks when the hierarchy shifts within the view. There are some other issues that I haven't yet had a chance to track down... but maybe this will help get the ball rolling a little.
By the way, if the data connection fails at first, you may have to edit it and point it to the local cube file that I've attached.
Blimey! That was quick, Joshua! That's a great idea. I hadn't thought of doing that outside of the title function. That has certainly sparked some ideas. I will have a play with it. Thanks for your help
You're welcome! Please let me know what you come up with!