• Replies 1 reply
  • Subscribers 337 subscribers
  • Views 16 views
  • Users 0 members are here
Related

SSRS Report Not Showing Correct Numbers

Beau Flowers
$organization

Hey everyone,

I recently wrote a stored procedure that would generate a comparative season sales report by year. The paramaters include a present and past season as well price type.

This includes: Number of orders, total sold amount, donations, fees, parking passes, performance date, performance name, and tickets sold to date for "present year".

The report came out outstanding after I built it out in SSRS except for one little hiccup. We have three films that are part of a "Film Package". I cannot figure out how to display the correct numbers for "Tickets Sold To Date". I tried different grouping options in SSRS and that does not seem so solve the issue. Setting filters for package and ID numbers does not correct the error either. 

I am not sure if the failure to load the correct number for "Tickets Sold To Date" lies in SSMS or SSRS. I have been beating my head against a wall trying to figure this one out. Any help would be greatly appreciated.

Below is my SQL code:

SALES SUMMARY

SSRS Screen Shot:

SSRS Report

 

 



[edited by: Beau Flowers at 6:04 PM (GMT -6) on 19 Jul 2017]
Parents
  • $organization

    I think your first order of business should be figuring out whether the problem is in your report or your query (or potentially even in your parameter setup for Tessitura). To that end, I would take the following steps.

    1. Run a SQL trace and run your report with desired parameters from the tessitura client.
    2. From the trace, find the exact SQL statement being used to call your stored procedure with those parameters.
    3. Run this same statement in an SSMS window to get the result set directly.
    4. Compare the result set to your SSRS report, and compare SQL statement with the parameters you chose when running the report.
Reply
  • $organization

    I think your first order of business should be figuring out whether the problem is in your report or your query (or potentially even in your parameter setup for Tessitura). To that end, I would take the following steps.

    1. Run a SQL trace and run your report with desired parameters from the tessitura client.
    2. From the trace, find the exact SQL statement being used to call your stored procedure with those parameters.
    3. Run this same statement in an SSMS window to get the result set directly.
    4. Compare the result set to your SSRS report, and compare SQL statement with the parameters you chose when running the report.
Children
No Data