This may be a little tedious depending on how many prompts you have but one way to achieve this is to assign a Parameter to the "required" prompts. Then you can assign a filter to the map and any other object you don't want to load yet using the "IsSet" function. The filter would something like this: IF ( IsSet('Parameter'p)) RETURN (1=1) ELSE (1=2) which basically checks to see if there is a value for the parameter. If yes, then return values. If no, then return no values. Hopefully that makes sense! ... View more

When you export, make sure you select the option "Expand all clipped and non-visible content": This should print the first page of your report as-is on page 1, but then in the Appendix you will find the table in full.    ... View more

It looks you may have accidentally disabled auto refresh. This should be in the options menu here (this screenshot is from VA 8.5.2, so may vary a bit on other versions):   ... View more

Text with a parameter would be the cleaner approach I think, but it's a little tricky. You are right that you cannot set a parameter from a graph, but to work around that you can do the following: 1. Add a drop down list with the same category you are using in your chart. 2. Set the drop down list to Required 3. Create a character parameter and assign it to the drop down list. 4. Create a filter interaction from the chart to the list control 5. Add a text box and add whatever text you want plus the parameter.  As you click through the chart, the drop down list should update, setting the parameter, and then updating the text box. Something like this:   Then you could take it a step further and use a precision container to hide the drop down list from view (put it behind the bar chart for example).   One downside to this approach, when you do not have any selections in the chart, the parameter is still going to be set to either the default value or whatever was previously selected. Here I de-select the 'Ford' bar in my example, but Ford is still set in the drop down list and therefore the parameter:     I haven't found a way around this yet.  If you want to stick with the button bar approach, a separate datasource might work for the button bar. As long as the page filter prompts aren't mapped to it then they won't filter it,  BUT you'd still have to have one mapping from the chart to the button bar which might get you in the same situation anyway.    Alternatively, you would have to abandon using page filters and move all of those prompts to the body of the report, then just not have an action between the prompts and the button bar. I don't believe there is going to be an easier way around that.   ... View more