Have you ever noticed a report data definition where all the fields are Excluded, yet the report style still works just fine?

The Open DMR Status Report (DMRStatusReport) has all fields and field labels marked as excluded, yet it works fine. Has 2 subreports even.
Worse yet, fields that are on the report or subreports, are not even in the RDD, yet the report runs just fine. I checked Menu Maintenance just to make sure I was looking at the right thing.
What’s going on here?

If I add 1 field from the PartTran table to the dataset expression in the TransactionHistory subreport, and add the field to the dataset, the subreport gives the Error subreport cannot be shown message. Which should be easy enough to fix, but I was unable to resolve how all the fields were excluded yet the untouched report was working fine.

This is on 10.2.600.11, cloud pilot system.

In our 10.2.200, there are no fields listed on the exclusions sheet. It’s blank for every table.

I though this was by design.

Weird isn’t it? How does this work do you reckon?

I’ve even pulled up a BAQ, pulled up the PartTran table, and made sure all the column names are consistent with the ones that I wanted to add into the DataSet. No dice.

I haven’t looked into it very much. Just seemed like every RDD had completely blank exclusion sheet.

Maybe it was just my customized RDDs, and the update from 10.1.400 to 10.2.300 FUBAR’d them.

It’s just irritating that I feel like every time I start working on a report, I have to customize the RDD just to make it usable. I don’t really like just creating mods unless is it necessary. And, I shouldn’t get myself aggravated today, it is Friday after all! :slight_smile: