locked
Returning no value in a field RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I am having an issue with a field not returning a value ONLY in the report. 

    Basically, the value will return when I run my stored procedure from my DB utility, but when the report runs, the value will not show up.

    There is no grouping, filters or anything set on the row or tablix the field is in.

    The field comes from a variable set inside the stored proc, and returned from a temp table.

    I'm thoroughly confused..I've created hundreds of reports and never run into this issue. HELP!!!

    Sarah Jr.Developer

    Friday, March 22, 2013 4:46 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    What parameters does the stored proc expect to be passed into it? what are you passing in from your dataset? Are you mapping report parameters to the SP input parameters? How is the SP variable being set? Is that source impacted by input parameters? If so take a close look at the input parameters. Be certain they contain the expected values.

    You can do this by adding one textbox for each parameter and setting the text box to display one of the report parameter values:

    =Parameters!ReportParameter1.Value

    Then run the stored proc from your db utility using those exact values. I suspect that you will find that at least one of the parameter values being passed into the SP is causing the null values being returned to the report.

    "You will find a fortune, though it will not be the one you seek." - Blind Seer, O Brother Where Art Thou
    Please Mark posts as answers or helpful so that others may find the fortune they seek.

    • Proposed as answer by Charlie Liao Monday, March 25, 2013 7:47 AM
    • Marked as answer by Charlie Liao Thursday, March 28, 2013 8:18 AM
    Friday, March 22, 2013 7:11 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Does every row in the dataset have a value in the field in question?

    "You will find a fortune, though it will not be the one you seek." - Blind Seer, O Brother Where Art Thou
    Please Mark posts as answers or helpful so that others may find the fortune they seek.

    Friday, March 22, 2013 4:56 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yes, it does. I set the variable in the beginning of the proc and then just return it in the temp table.

    So, I tried putting an isnull around the variable just to see what would happen so:

    isnull(@Total,100.00)

    The report is returning the 100.00.

    There are no nulls in that field at all. 

    I'm so confused....

    edit: it was a date format thing....so obvious, yet so dumb.

    Sarah 


    • Edited by SarahTZT Friday, March 22, 2013 6:40 PM
    Friday, March 22, 2013 5:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    What parameters does the stored proc expect to be passed into it? what are you passing in from your dataset? Are you mapping report parameters to the SP input parameters? How is the SP variable being set? Is that source impacted by input parameters? If so take a close look at the input parameters. Be certain they contain the expected values.

    You can do this by adding one textbox for each parameter and setting the text box to display one of the report parameter values:

    =Parameters!ReportParameter1.Value

    Then run the stored proc from your db utility using those exact values. I suspect that you will find that at least one of the parameter values being passed into the SP is causing the null values being returned to the report.

    "You will find a fortune, though it will not be the one you seek." - Blind Seer, O Brother Where Art Thou
    Please Mark posts as answers or helpful so that others may find the fortune they seek.

    • Proposed as answer by Charlie Liao Monday, March 25, 2013 7:47 AM
    • Marked as answer by Charlie Liao Thursday, March 28, 2013 8:18 AM
    Friday, March 22, 2013 7:11 PM