locked
rsRuntimeErrorInExpression The Value expression for the textrun ‘Textbox14.Paragraphs[0].TextRuns[0]’ contains an error: RRS feed

  • Question

  • hi;

    whats wrong with my code here.[*urgent]

    =String.Format("{0:0.0}%",(count(Fields!y.Value)/sum(Fields!x.Value)+ sum(Fields!z.Value)) * 100)

    thanks in advance

    Tuesday, September 25, 2012 9:02 PM

Answers

  • Hi vadz007,

    If I understand correctly, the warning message was caused by the incorrect previous expression, however, the warning message persists although the values displays correctly in the report after you modified the expression. Besides, the warning message came out even though you create a new report and use the right expression.

    This is a knonw issue in Report Designer. When there is a warning message generated in the "Error List" pane of the Report Designer, the warning message still pops up after we correct the previous error. Actually, it always pops up whenever we preview any report in the same project. To avoid the issue, we only need to close the project and reopen the project. That way, the previous error lists will be cleared and the warning message won't pop out unless there is still an error in the report design.

    Hope this helps.

    Regards,
    Mike Yin


    Mike Yin

    TechNet Community Support

    • Marked as answer by Mike Yin Sunday, October 7, 2012 2:26 PM
    Tuesday, October 2, 2012 8:02 AM

All replies

  • I just tried your formula in one of my reports using 3 numerical fields in my dataset and I get no errors. Renders as expected. What is the rest of the error, the details?
    Tuesday, September 25, 2012 10:31 PM
  • thanks Tim Pacl for reply

    Message comes as

    [rsRuntimeErrorInExpression] The Value expression for the textrun ‘Textbox14.Paragraphs[0].TextRuns[0]’ contains an error:Input String was not in a correct Format

    it was running before but when i edit on that same text[same code as above] box i got the error message...its a Warning not an error but i don't want to display when i run my ssrs 2008. what it really frustrates is that i points to that same report. i create another report same code as the one before but i points on that same report error..

    What about the String format?..should i have something like this String.Format("{0:0:0:0}% i put colon between 2 0's or a dot after 1st 0?. eg : 0:0.0.0 or 0:0:0:0?

    thanks in advance



    A.Vadz



    • Edited by uttar007 Tuesday, September 25, 2012 11:30 PM
    Tuesday, September 25, 2012 11:16 PM
  • Do you know that x and z are non-zero values? What was the edit you made that triggered the warning? If you haven't closed the report since the edit, undo the edit and make sure it works. Then compare the broken to the working.

    Tuesday, September 25, 2012 11:48 PM
  • Hi vadz007,

    If I understand correctly, the warning message was caused by the incorrect previous expression, however, the warning message persists although the values displays correctly in the report after you modified the expression. Besides, the warning message came out even though you create a new report and use the right expression.

    This is a knonw issue in Report Designer. When there is a warning message generated in the "Error List" pane of the Report Designer, the warning message still pops up after we correct the previous error. Actually, it always pops up whenever we preview any report in the same project. To avoid the issue, we only need to close the project and reopen the project. That way, the previous error lists will be cleared and the warning message won't pop out unless there is still an error in the report design.

    Hope this helps.

    Regards,
    Mike Yin


    Mike Yin

    TechNet Community Support

    • Marked as answer by Mike Yin Sunday, October 7, 2012 2:26 PM
    Tuesday, October 2, 2012 8:02 AM
  • Thanks MIke. Useful info. vadz007, does that answer your question? Does the error go away when you close and reopen the project?
    Tuesday, October 2, 2012 2:24 PM
  •  thanks for your reply..greatly appreciated..:)...ablel to solve it

    A.Vadz

    Thursday, October 18, 2012 5:44 AM