HINT: Advanced Printing RDD

When making an Advanced Print Break/Routing rule on a Report style, make sure to make a copy of the Report Data Definition, and use that for the Style’s RDD.

Because you can’t change the RDD used by the Break/Routing. Even if you change the RDD used by the Report Style, the Break/Routing will use the RDD specified when the Break/Rout was created.

So even if you just need to un-exclude a field of the base RDD so it can be used in the Break/Routing, you must delete the Break/Routing and create it from scratch.

The good news is, that changes to an existing RDD do show up in the Break/Routing designer.

So just always make a copy of the base RDD, and use that one for the Report Style

One last thing: Deleting a Break/Routing isn’t straight forward. There’s no “delete” button on the Break/Routing tab, and no “row” to select on the form. And the Delete icon in the toolbar is diabled.

Just click the Style Number on the Break/Routing tab - yes it’s Read Only, but the cursor will make that field in focus - enabling the delete button on the toolbar.


Great guidance. I’ll throw in another that I ran into recently.

The Breaking rule is dependant on how the RDD was configured at the time that the rule was created. Which is to say, assume

  1. you have an RDD that includes all columns on all tables (not so great).
  2. you create your life changing amazingly awesome Breaking and Routing rule that will save so much time you only have to work three days a week instead of eight.
  3. you realize you don’t need extended UD fields in this particular RDD, so you exclude them from the RDD to improve performance.
  4. you try to print the report that has this routing rule and very good chance you :’(

The order of operations when it comes to report development:

  1. create a new style for your next report.
  2. get your RDD exactly as you want it (only the columns that you need, nothing more, nothing less).
  3. when you are happy with the report, actually wait to make sure your users are really happy with it.
  4. when everyone is happy happy, create your Routing Rule lest you wish to potentially create it a second time.

One thing to add with respect to RDD’s…

If you add a Table to an RDD the fields used for the table relationship must not be excluded. This includes the parent table.