I have two issues with SSRS.
I have cascading parameter. User selects first parameter (#place) and on that
basis last two parameters (#group and #cost) should grey out. Currently Only
the last parameter (#cost) greys out, not the second last (#group) getting
"select a value". If I swap the order then the #group greys out and #cost
does not
When I run the report in my local system, the cascading parameters only works for first time. When I change the #place parameter value then the rest parameters do not update..
Update: Mock Example below:
This is the issue in pic above. When C is selected I want both parameters to be greyed out. In first picture, I have mentioned Null for both when C is selected
I have created a dummy project with other fields in order to solve this scenario. My fields are LAST_DATE_EDITED, ID and FEE_AMOUNT in which ID and FEE_AMOUNT are dependent of LAST_DATE_EDITED field.
In order to do this, I created 3 datasets for each parameter. For LAST_DATE_EDITED I put only a SELECT LAST_DATE_EDITED from test table. For ID and FEE_AMOUNT I did as below:
In this way, I achieved the following output:
I hope that I understood correctly and this will help you.
Related
I need some assistance trying to hide a tablix.
The Scenario:
I have 2 tables on one report which has a multiselect parameter. I need to hide one table based on the selection. i need to show a specific table based on only one value now i have used the instr()and Join() functions which definitely work, but when i select all of the values i still get the table pertaining to the one specific value.
Example of code to show specific table;
=IIF(Instr(Join(Parameters!Name.Value),"Name1")>0,False,True)
This shows the table when 'Name1' is selected.... I want to show that table when ONLY 'Name1' is selected. Any help would be much appreciated
You should also check parameter count on your expression like below
=IIF(Instr(Join(Parameters!Name.Value),"Name1")>0 AND Parameters!Name.Count=1 ,False,True)
I have come to the desired answer by just using the join() function and excluding the instr(). The code looks like the ffg:
=iif(join(Parameters!Name.Value(),",") = "Name1",true, false)
This works well.
Thanks for the help
I am attempting to maintain and fix a horribly out-of-date CRM designed by an ex-employee ~4-5 years ago in Access 2007. I have brought it into Access 2013 and fixed a ton of stuff up, but I am still running into many problems.
I spent a good 4 hours today attempting to figure out why certain values didn't line up. These values were being pulled from a SELECT statement on a Combo Box over a stored Query which simply returns a table with a few extra rows. Great.
However this value (a number) doesn't appear to correlate with what we expect. I enter in one value, save the ticket, and a completely different value gets stored into the table. Opening up the ticket, I see the value that I expect. Digging deeper, I found the following difference:
Set value_1 = Me.RegistrationID // What's being stored in the table
Set value_2 = Me.RegistrationID.Column(0) // What we expect
Surprise surprise! This is a Combo Box and some value is being stored in the table. The Control Source is "RegistrationID" and the Row Source is the query in question.
However I do not know what it is! This specific value correlating to the Combo Box appears to pull the correct data when we later open the tickets. However I have a strong feeling that this could be why many tickets from before one of the rows was deleted all appear to have invalid RegistrationID's.
How badly can this break?
How easily can we correct tens of thousands of tickets?
How can I fix this to store the correct value?
This is what I expect is happening.
Your combo box row source is based on a Select query which returns and displays multiple rows. For example:
Select RegistrationID, CustomerID, CustomerName From MyTable;
The Control Source for the combo box is bound to RegistrationID which is part of the Forms Record Source.
The issue is the bound column. If we set the bound column in our example to 1, then we get the behavior your are describing with:
Set value_1 = Me.RegistrationID - Set's value to CustomerID (may appear correct)
Set value_2 = Me.RegistrationID.Column(0) - position 0 from our query (RegistrationID)
Further building on our query example, you can say:
Me.TextBox1 = Me.RegistrationID.Column(0) - RegistrationID
Me.TextBox2 = Me.RegistrationID.Column(1) - CustomerID
Me.TextBox3 = Me.RegistrationID.Column(2) - CustomerName
The RegistrationID is what normally should be stored in the table.
As long as your form shows any values that directly relate to this RegistrationID you're fine.
I would start by checking to see under the format setting to see if column widths are set properly and I would also check under the data section to see if the bound column is correct. I might also throw in an after update macro/vba sub routine that saves the record. Hope this helps.
I have an SSRS Report parameter set up with 3 different values ("Paid", "Denied" and "Open"). I want to set a tablix filter up so when the user selects one of the parameters, and a condition in the data is met, that row is returned. I want to give the user the option to select all there parameter values.
When I use the following Expression into the Tablix filter(Paid), it works correctly:
=IIf(Parameters!ClaimStatus.Value(0) = "Paid"
and Fields!TotalPaid.Value > "0"
, "Include"
, "Exclude")
If I try adding an additional filter(Denied) with the following Expression, neither filters work:
=IIf(Parameters!ClaimStatus.Value(0) = "Denied"
and Fields!Denied.Value > "0"
, "Include"
, "Exclude")
Is it possible to pass multiple parameters into a Tablix Filter? I've searched all day with no luck. Any help would be greatly appreciated. Thanks.
You should set up the filter to check the values in teh DataSet are 'IN' the multi-select parameter
In this example my DataSet has a field called Status which could be Open, Paid or Denied.
I also have a multi-select parameter as you describe above called ClaimStatus.
Using the IN operator makes the filter look for instances where Status is in the list of ClaimStatuses selected. Note the default when you add the ClaimStatus parmater as an expression is to add a (0) on the end. Remove this
When this runs and I select Paid and Open, only the Paid an open records are returned in the table that has the results filtered.
Hopefully this will work for you. Let me know if I can assist further.
I have a report where users can select items from various location. And I have 3 datasets performing calculations where the third dataset takes the sum where item number is 4942200 and then calculates the values (as shown below):
=SUM(IIf(Fields!masterno.Value= "4942200",Fields!Owned.Value,0))+SUM(IIf(Fields!masterno.Value= "4942200",Fields!Subbed.Value,0))
This is returning error for some reason. The subbed column is toggled based on parameter (visibility). But before I add the toggle functionality, I want to make sure this is working. Can anyone help. I have also tried:
=SUM(IIf(Fields!masterno.Value= "4942200",Fields!Owned.Value+Fields!Subbed.Value,0))
This seems to fail as well. Help would be greatly appreciated.
I would wrap a CDec around Owned, 0 and Subbed, e.g.
=SUM(IIf(Fields!masterno.Value= "4942200",CDec ( Fields!Owned.Value) ,CDec (0 ) ))+SUM(IIf(Fields!masterno.Value= "4942200",CDec (Fields!Subbed.Value ) ,CDec ( 0 )))
If Owned and Subbed are already Decimals, those CDec's may be redundant. On the other hand SSRS doesnt expose this info and they can change at the whim of the data source.
I have an SSRS report
where the date should be grouped by project category
the project code in the category is repeating in side the group how do I suppress the value
Please help me to get an idea.
Thanks,brijit
You can also hide fields by putting an expression in the Hidden property like this:
=Fields!ProductCode.Value = Previous(Fields!ProductCode.Value)
So if the value in the previous record is the same as this one, it will hide the field. You must sort the dataset correctly for this to work. In your case I think the sorting would be Date, ProductCategory, ProductCode.
In the past I used this often together with expressions for field borders to group the output visually.
I think there is one option hide duplicates in properties in ssrs. so you will check in that option under the project category group.so that you can hide the duplicate values and get unique records. first u create one group based on project category in fields properties and then check in that hide duplicate option under that group.whenever you check in that option it will high light one drop down list showing containing group or dataset there you select your created group.
This is a bit late for you brijt, but what I do is edit the textbox properties for that field, in the font tab enter an expression for Color as follows:
=IIf(Fields!ProductCode.Value = Previous(Fields!ProductCode.Value), "White", "Black")
...assuming your background is white this will effectively do what you want.
I think it may be an issue concerning the way you are grouping the dates. Do you have the grouped with time on them as well but suppressing the hours in your output?
For example:
12-5-2010 12:00:00
12-5-2010 13:00:00
if you strip the times off in how you see them but not how you group them, they would show up duped.