November 21, 2014 at 7:40 am
Using SQL Server 2012 running SSRS
Reports is designed in Report Builder 3.0
Dataset based on StoredProcedure is fairly simple.
Each record contains a Customer, Employee, APValue, ARValue, NumberOfDays. Profit
The report contains a tablix with 3 rows and 5 columns
1 - Customer (Merged cells across 5 columns)
2 - (Detail) Employee, NumberOfDays, APValue, ARValue, Profit
3 - Totals for each customer. Sum(NumberOfDays), Sum(APValue), Sum(ArValue), Sum(Profit)
There is a Customer Group with KeepTogether = True
There is a Employee ChildGroup with KeepTogether = True with Details
If a customer group is too big to fit on the rest of the page, it should start at the first line of the next page regardless of weather it completely fits on the next page or not.
This should be a no-brainer but the pagination action doesn't work. Each customer starts at the end of the previous customer regardless of size. It doesn't matter if the customer is small enough to completely fit on the next single full page or not. It behaves as if all KeepTogether = False.
I noticed there are many places where KeepTogether and KeepWithGroup can be set around this tablix.
The Border box has a KeepTogether, I set it to False
The Tablix has a KeepTogether, I set it to False
Each Row in the Tablix has a KeepTogether, I set them all to false
Each Cell in each row has a KeepTogether, I set them all to false
Both Groups have a KeepTogether, the Customer is set to True and the Employee is set to false.
From AdvancedMode every static group element row and column has KeepTogether set to false and KeepWithGroup set to None.
I've also tried setting all the KeepTogether settings to true with all KeepWithGroup set to none.
Then I tried a large number of combinations with the same result.
What kinds of settings could keep something as simple as this from working?
There must be a standard approach to this that makes it easy to manage.
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply