We have a letter with an optional directions-page. When the directions aren't available we don't want the directions-page. If they are available, we do want a seperate directions-page.
The problem
We put the objects we want to show in a list. In the properties for this list we set 'Page break before start' to true.
When we run the report with let's say two records, we get 4 pages. For each record a page with the letter and a second page with the directions.
However, if the 'directions'-field wasn't filled, I don't want the directions-page either. So in the properties for the list we set 'Initial visibility' to 'Expression: =IsNothing(Fields!Location.Value)'
When running the report we get two pages. On one page the letter is show allright, on the other page the letter ánd the direction-objects are rendered.
After some searching I discovered RS does not support this combination. Microsoft tells us it will be resolved in some future release.
The workaround:
We create a second list around the first 'directions'-list. Both use the same grouping and sorting. The trick is we will split the visibility and new-page functionality. The first list has no new-page set, but only the visibility. This list contains one object: the second list.
This second list has set 'Page break before start' to true.
Now it works fine.
