data is in sql query and query designer in report builder but doesn't show up in field in report.

Question

I have tried converting the data, using case statements, everything I can think of to modify the data but it will not show up in the report when you run it. The data always shows up in sql query and in the query designer in report builder 3.0 but will not show up when you run the report. I've checked everywhere for visibility issues on the tablix, the detail row, the cell for the data. I've uploaded it to the report server and run it, same thing, blank cells where there should be data. I've checked the xml file of the report, fields that work before and after the blank cells are no different thank the blank cells. I have fields of alpha and numeric data before and after the blank cells. I'm at 'wits end' as they say to resolve this. Please give me a clue why this is happening. Thank you.

Answer 1

Hi @Hochstatter, Raymond

Sometimes SSRS can be a bit "off" at times, and there can be any number of reasons. You can try the following:

1. Delete the .data file associated with the report.
2. Copy/backup the report and try adding the dataset to a fresh base tablix to see if the data actually shows up.
3. Check font color and size.
4. Check ExecutionLog3 and other logging stuff, etc. For more details, you can check out the discussion in this link for reference: https://stackoverflow.com/questions/11359194/ssrs-report-not-displaying-data.

If the answer is helpful, please click Accept Answer and Up-Vote for the same. If you have any questions, please feel free to let me know.

Best regards,

Aniya

Answer 2

The answer is what I stated in the last comment. The data source did not have rights to some of the data. Because I was running the sql query and query designer under my account and thinking the query designer was using the data source, I wasn't seeing the limitation. When the runtime runs the report it uses the data source which I thought was a full access one but apparently was not. Thank you for the assistance. This is the first time I've run into a security issue like this.