Using RunningValue in SSRS - reporting-services

Trying to use the following expression in a matrix in my report:
=RunningValue(Fields!orderCount.Value,SUM,"RedemptionData")
But it gives the error:
The Value expression for the text box '' has a scope parameter that is not valid for RunningValue, RowNumber or Previous. The scoke parameter must be set to a string constant that is equal to the name of a containing group within the Tablix''.
Any ideas what I might be doing wrong?
Cheers

Im such an idiot. Just realised there is no scope on this. Used the following code which works perfectly fine:
=RunningValue(Fields!orderCount.Value,SUM,Nothing)

Related

SSRS - Using RunningValue vertically

I am running a report on SSRS where 2 of the columns are running value.
Before it was like:
SO i was running the report by each code at once.
I changed it to allow multiple codes to be shown in the report (Grouping by Code) and it gave me the below:
As you can see, its doing running value horizontally.
I want it to do it vertically by each code like below:
MAYBE USING THE COLUMN GROUP AS SCOPE WILL WORK? I AM NOT SURE HOW TO USE COLUMN GROUPS IN SCOPE. ANY IDEAS?
You can try this by writing custom code -
Go to Report Properties and write code
public corder as integer
Function GetcOrder(order as integer) as integer
corder =corder + order
Return corder
End Function
Give a Name to Order text box
Next write an expression to calculate cumulative order value by calling function written in first step
preview output
Repeat the same step for rest of cumulative values .. please make sure to define public variable like
public corder as integer
All the Best!
Got it working!
Using the column group as scope works. I was using Nothing before as the scope. THen tried using the group in square brackets until i realised it needs to be passed as a string like "groupName"

The Group expression for the grouping ‘Origin2’ contains an error: Argument 'Length' must be greater or equal to zero. (rsRuntimeErrorInExpression)

I am getting this error every time this report is rendered. I looked at the group expression for this group and it looks like this:
=Trim(Left(Fields!ILS_LS_USER_10.Value,InStr(Fields!ILS_LS_USER_10.Value,"->")-2))
The field ILS_LS_USER_10.Value is: BNST -> USWEOLN
I can't see the error. Can anyone help me diagnose this error, please?
It works if you put the string literal in place of Fields!ILS_LS_USER_10.Value.
The issue is that it isn't getting the value of the field as a string by default. Use the ToString() method after .Value and it should work, or at least it did on my machine.
=Trim(Left(Fields!ILS_LS_USER_10.Value.ToString(),InStr(Fields!ILS_LS_USER_10.Value.ToString(),"->")-2))
I found that the Group expressions, for some reason, do not seem to like the subtraction in the InStr. Leave out the subtraction and it works.
In fact, take the same formula, and place it into a placeholder in the Group and it seems to work just fine. Replaced with Split in the Group expression and it works.
This was on SQL Server 2016, using Report Builder.

LIKE operator in SSRS row visibility expression

I have a text box within an rdl report which I want to suppress based on certain terms in my dataset (i.e. if the query returns a term which ends with the letter "L" then hide the text box).
Within the textbox properties I have set visibility expression for Hidden with the below expression:
=First(Fields!STERMS__.Value, "Job") NOT LIKE '%L'
When I run it I get the error:
"The Visibility.Hidden expression for the text box contains an error:
[BC30201] Expression expected"
It seems like a schoolboy error but I have tried various permutations on this expression with no luck. Any help would be appreciated.
SSRS expressions are funny in some ways. I think what you're looking for is:
=IIf(First(Fields!STERMS__.Value, "Job") Like "*L", True, False)
The gist is that SSRS doesn't use SQL syntax. It's VB
I think you could use the Right() function which returns a specified number of characters from the right hand side of a string.
E.g.
=Right(Fields!STERMS__.Value,1)
I guess in your case for Hidden property on the cell, the expression would look like this
=IIF(Right(First(Fields!STERMS__.Value, "Job"),1)=="L",true,false)

Check null and split value in textbox in SSRS report

I am facing very simple issue but not getting solution over it.
I have textbox in my ssrs report, I am passing value "1;prashant" or null to it. Now, if I pass value "1;prashant" to textbox then textbox should show only "prashant" and If I am passing nothing then it should be blank.
I have tried following IIF condition:
=IIF(IsNothing(FieldS!WIAPPORVER.Value),"",Split(Fields!WIAPPORVER.Value,"#")(1).ToString())
But, I above code is giving an error ["#error" shows in textbox] if I am passing blank value.
Please let me know, where I am wrong in this.
Thanks
There are probably better ways of doing this, but this is what my head came up with at the time:
=IIF(
IsNothing(Fields!WIAPPROVER.Value)
,""
,Right(Fields!WIAPPROVER.Value,Len(Fields!WIAPPROVER.Value) -InStr(Fields!WIAPPROVER.Value,";"))
)
I believe SSRS is trying to compute everything in the report at runtime, so in your case it is still trying to fetch index 1 from an array even though there is nothing in it and it crashes.
Edit: Changed parameters to Fields. I created a parameter to remake the issue at my side.
Just get the split out of the iif. Then in your iif, if field is nothing create a string that when split will return ""
=Split(IIF(IsNothing(FieldS!WIAPPORVER.Value),"#", Fields!WIAPPORVER.Value),"#")(1)
You are relying on the IIf expression short circuiting, but SSRS IIf expressions do not short circuit - the expression will try and work out Split(Fields!WIAPPORVER.Value,"#")(1).ToString() for all rows and fail when this value doesn't exist.
You can get this going by using text expressions, which don't get this error.
With test data:
And a simple table:
I have added columns with both your existing expression and a new expression:
=Right(Fields!WIAPPORVER.Value, Len(Fields!WIAPPORVER.Value) - InStr(Fields!WIAPPORVER.Value, "#"))
This new expression works for NULL values, empty strings and strings with no delimiter present:

Type Problems with Filter Expression in SSRS

SQL Server 2008 R2, using BIDS to design the report.
I have a table and I am trying to only show a certain row. Maybe there are better ways to do this, but I am coming across an error with the filter expression and regardless of how I achieve my initial task, I'd like to understand the filtering.
I started with the filter expression (set to type "Integer"):
RowNumber(Nothing) = 1
This gave the error:
Cannot compare data of types System.String and System.Int32.
I found the solution to this is to change the 1 to "=1" as 1 is evaluated as a string.
So I then had:
RowNumber(Nothing) = =1
That changed nothing, I got the same error.
Then I tried to do that to the first part of the expression:
=RowNumber(Nothing) = =1
This changed the error to a deployment problem (still builds, which is frustrating):
Error pvInvalidDefinition : The definition of the report '/ReportName' is invalid.
I then tried using CInt on RowNumber:
CInt(RowNumber(Nothing) = =1
Then I can deploy it, but the error just changes back to the first one:
Cannot compare data of types System.String and System.Int32.
It seems no matter what I try here I either can't deploy the report or I get an error that I'm comparing a string to an int.
RowNumber returns an integer, so it seems like this should work. I've tried using the name of the dataset in place of "Nothing" but that doesn't change what I'm seeing.
I realize there are many ways to solve my initial problem, but I am curious as to why the filter expression is invalid.
Its better to hide a row with visibilty property. Just click on any text box and go to visibily tab . You can now click on show or hode and go to expression.
That default to Hide . So write an expression there to hide the row.
=IIf(NOT(RowNumber = 1),TRUE,FALSE)
Let me know if you get any error
RowNumber is not available to use in a Tablix Filter.
Using RowNumber(Nothing) <> 1 as a Row visibility property fixed the issue.
Using BIDS you are not given any error that indicates what the problem is, but importing the report to Report Builder and deploying it from there will give a more descriptive error that, in the end, helped me to solve my problem.