none
The Value expression used in textrun ‘Textbox.Paragraphs[0].TextRuns[0]’ returned a data type that is not valid.

    Question

  • Hi all,

    While viewing report in SSRS 2008 i am getting an error like this

    Warning 1 [rsInvalidExpressionDataType] The Value expression used in textrun ‘Textbox21.Paragraphs[0].TextRuns[0]’ returned a data type that is not valid. 

     sotred procedure

    ALTER

     Procedure [dbo].[spGetSupervisor]

    (

    @START_DATE

    datetime,
     

    @END_DATE

    datetime,
     

    @CenterID

    varchar(4000),
     

    @TITLE

    varchar(100) = NULL

    )

    as

    Select

     Distinct L1_ID SupID, L1_Name SupName

    from

    REF_DB.info v inner join dbo.fn_MVParam(@CenterID + ',' , ',') P

     

    v

    .CenterID = p.Column1
     

    where

    v.startdate <= @END_DATE and v.enddate >= @START_DATE

    and

     (v.title IN (@TITLE) or @title is

     

    order

     by Name

    Here is the expression in Report textbox

    =Parameters!CenterID.Label

    Please help me

    Thanks in advance

    Jyo

    null)

    ON

    Wednesday, June 22, 2011 2:06 PM

Answers

  • Hi Jyo1105,

    Thanks for your question. Based on my research and experiences, the issue may be caused by you set the @CenterID is a multiple values parameter.

    If in this condition, you couldn’t use the expression of Parameters!CenterID.Value directly, you should use a join() function on the parameter to merge the whole values, or add a sequence number behind the expression to use a specific value, just like this:

    =join(Parameters! CenterID.Value) or

    =Parameters! CenterID.Value(0)

    If your issue still exsits, please feel free to let me know.


    Thanks,
    Sharp Wang


    Best Regards. Sharp Wang
    Friday, June 24, 2011 2:28 AM
    Moderator

All replies

  • Why didn't you use =Parameters!CenterID.Value?
    Remember to mark as an answer if this post has helped you.
    Wednesday, June 22, 2011 4:00 PM
  • @Igor

    I did , still i am getting same error.

    Wednesday, June 22, 2011 6:42 PM
  • You may execute the stored procedure in SQL Server Management Studio to review possible values in the output.

     


    Remember to mark as an answer if this post has helped you.
    Wednesday, June 22, 2011 8:42 PM
  • Hi Jyo1105,

    Thanks for your question. Based on my research and experiences, the issue may be caused by you set the @CenterID is a multiple values parameter.

    If in this condition, you couldn’t use the expression of Parameters!CenterID.Value directly, you should use a join() function on the parameter to merge the whole values, or add a sequence number behind the expression to use a specific value, just like this:

    =join(Parameters! CenterID.Value) or

    =Parameters! CenterID.Value(0)

    If your issue still exsits, please feel free to let me know.


    Thanks,
    Sharp Wang


    Best Regards. Sharp Wang
    Friday, June 24, 2011 2:28 AM
    Moderator
  • I fought with the same error for over an hour. I tried almost everything. Finally when I moved the same report without any changes into a new project, it started to work!

    Here's how I got mine working:

    • Create a new report server project
    • Right click "Reports" and choose Add > Existing Item...
    • Navigate to your broken project/report and add it
    • Reconfigure your data source if you are using a shared one
    • Go to preview and it will work if you had the same issue as I had
    • Proposed as answer by tubelius Thursday, November 08, 2012 1:55 PM
    Thursday, November 08, 2012 1:55 PM
  • Copy and paste your query into a new project, creating a new report project solved the problem! 
    Friday, December 14, 2012 2:15 PM
  • delete the .rdl.data file...
    • Proposed as answer by SQL Padre Tuesday, January 29, 2013 6:33 PM
    Friday, January 11, 2013 6:14 PM
  • Caused by SSRS caching. Had that same isse when I updated the background stored proc for the report. Delete the .data file...
    • Proposed as answer by Brian Buchanan Thursday, January 09, 2014 9:16 PM
    Wednesday, February 27, 2013 2:08 PM
  • George's answer fixed my issue. Closed report delete the .data file and reopened the report and my error was gone.

    Thursday, January 09, 2014 9:18 PM
  • Justo lo que esta necesitaba, muchas gracias.
    Wednesday, April 23, 2014 12:43 AM