I have a report that for some odd reason wants to ignore the existence of a value. All of the other values are present, it is just the 69 value that happens to be missing within SSRS.
In SSMS the value is there.
I am feeding the parameter (Allow Blank/ allow Multiple Values) from a Dataset query, the query is:
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
SELECT DISTINCT hrcl.rvalue
FROM dbo.herpaderpcl hrcl
UNION ALL
SELECT 'ANY'
When this is run against SSMS I am given 137 rows as the return. In SSRS I am only returned 136.
Everything else on the report works great. I also rewrote it slowly removing all other parameters to see if there was a conflict. There is not. It is purely this one Dataset/ Parameter that is acting up
Here is a partial screen shot of what the parameter drop down looks like, and where 69 should be showing up, but isn't.
The problem is I am dynamically creating the table listing, and the starting point for this choice does not have this value in it.
I am attempting to create a new dataset, by dynamically populating this set, based off of the original choice.
Related
First time posting here so please be kind.
I've come from using PowerBI to achieve pretty much everything I need to with a couple of clicks to using SSRS 2008... and I'm having a hard time. Here's what I'm trying to do:
I have a main report that summarizes some data on how long it takes to close down help desk tickets. On that report I have a table with summary figures (ie 220 tickets were picked up after 5 working days, 18 tickets were reopened etc). I want to click the text-box that contains 220 and be taken to a drillthrough report that contain the same table with column headers and just different row sets in each case. There will be 8 drill through actions in total and I currently have 8 drill through reports. Only 2 of those are parameter based, the others just filter the dataset based on some conditions.
What I'm trying to work out is this: can my 8 drill-through reports be rolled into one, if they're just different views of the same dataset? I've created some calculated columns with values (Yes/No because boolean doesn't allow multiple values) which are easier to pass to parameters. I also have 8 parameters on my detail data set. I've set up actions (where parameter1 = yes for instance) to take me to my detail report and use the corresponding parameter each time. It should work... but it doesn't and I can't work out why. Currently its' complaining that I can't compare a boolean to an int16 - neither the value in my calculated column nor the default parameter value is boolean or int. So, am I trying to do something that just isn't possible? Has anyone else achieved this?
Edit: here's the parameter
The error I'm getting is
The calculated column that should be checked against the parameter is
=IIF(IsNothing(Fields!DatePickedUpByAgent.Value), "Yes", "No").
Here's how I defined the action to take me to the drill through report in this case
Here are the filters on the subreport dataset based on the parameters passed through from the main report. "NotYetPickedUpByAgent" is the example we've been discussing here. enter image description here
Could you please go through each of your parameters one by one.
I would suggest deleting all the filters and trying to run the report and subreport.
Then keep adding filter one by one.
I think issue can be any of the filter and not the one you think.
I have an Access report with details (see image below). I have incremental numbering for the report details. I achieved this by creating a TextBox and setting it's Control Source: '=1' and Running Sum: 'Over Group'. This works well, but if I have no records the number shows up as 1 (I want this number to show up as 0). If I try to check if detail is NULL in VBA, it returns false if I have at least one Detail record in the entire report.
(Try 3)
OK, so the red section does show up on a left join, because the query is returning Null for the missing records.
So, your real fix is to:
Select a detail field that that is always non-Null (I'll assume it is called ID)
Set the control source of your counter control to:
=IIf(IsNull([ID]),0,1)
That way the running sum will show zero for emply detail groups.
I'm seeing some odd behavior with an SSRS report I'm working on. I have a 2 tablix elements that are are populated with the same dataset from a stored procedure. I have applied a filter on each tablix based on an Active field (Active and Inactive) in the dataset. Data looks fine and until I add an expression to the last textbox column field to do a simple calculation (see below). The values based on the data expression come back correct but the tablix now shows a duplicate row for one record (last record) in the tablix that has the filter set to Active. I'm not quite sure what is going on because the data is the same hasn't changed from when the expression is not there.
=Fields!Avg.Value/Lookup("Low Risk", Fields!RiskGroup.Value, Fields!Avg.Value, "ReportData")
Update:
So I haven't solve the problem but have more information. What looks to be happening is due to the order of the records coming back in SQL and how the tablix is filtering. The "Low Risk" record used in the lookup is the last record in the grouping. My 2 tablix I mentioned previous are identical with the exception of tablix filtering on Active field. If the Low Risk is the last record in the data set there are no data issues. However if the Low Risk is not the last record that is when the tablix goes awry. Anyway, still researching but anyone has any information it would be greatly appreciated.
Update:
Still haven't found the issue but found a workaround. I've extracted the lookup expression to a textbox and then reference that textbox in my tablix expressions and seems to do the trick....Still very odd behavior. I actually mocked up a simpler dataset and didn't see the same behavior so must be due to something in my dataset that I can't pinpoint.
I guys
I'm having a slight problem with a report im currently writing.
So when i run this report it gives me a list of outcomes from a data source.
One of results is 'Closed' I want to exclude this outcome in my report. I cant exclude this in my SQL code as it doesn't bring back the null values. ( when no outcome has been given to a task yet i.e no one has had the time to do it yet i have set that in the expression to 'No Outcome'.)
So i want to know if anyone can edit my expression so it does not bring back the value of 'Closed'
=IIF(IsNothing(Fields!OutcomeDescription.Value),"No outcome",Fields!OutcomeDescription.Value)
Any Help on this would be great sorry if iv not explained this well.
Rusty
To do this, you'll want to add a filter to either your dataset or your table object - whichever is most appropriate for your needs.
For a dataset filter, merely open your dataset properties, and look for the filters tab. For a table, you'll need to go into the tablix properties. Setting up a filter from there is simple.
Filtering at the dataset level will drop all of the filtered records before any controls on the report could access them. Filtering at the object level would drop the filtered records from the control, but they would still be available to other controls. If your report only consists of a single table, and no additional objects, I'd recommend filtering on the dataset.
One of our SSRS 2005 reports would time out when executed at the "All" level (was returning upwards of 80K records), so I added a group to the table whose sole purpose was to force a page break after every 500 records. I found the grouping in another post. It looks like this:
=IIF(Fields!ShowPageBreaks.Value = 1, Floor((RowNumber(Nothing) - 1) / 500), Nothing)
The problem is that the user sort no longer works correctly. E.g., "A"s show up at the top of multiple pages. I haven't been able to find any pattern in how SSRS decides to perform the sort. I've tried playing around with the Sort Scope and the Sort Target, like setting one to the Table and one the other to the Group, both to the Table, one or the other to nothing, etc and nothing seems to work.
Has anyone found a solution to a problem like this?
The sorting is happening within each group, aka, "working as intended." You're creating a somewhat arbitrary and random set of record groups based on row position in an un-ordered set.
You need to find a way to sort properly (in the SQL?) prior to applying any sort of grouping, or use a less random means of paging.