subtract two textboxes in ssrs from diff tables - reporting-services

I would like to build a report like this
In this report 2015 and 2016 columns are from different tables and I need the difference of both of them as result in another table the data set for 2015 and 2016 are also different. The data is pulled from cube. I tried this expression to get the result
ReportItems!textbox10.Value-ReportItems!textbox5.Value here textbox 10(2016 column) and textbox5(2015 column) but when I do this calculation I'm getting this result set

Technically you can reference a textbox with an expression like this:
=ReportItems!TextBoxList1.Value
However, I would strongly caution against this as it usually goes against best practices. Textboxes in tables are meant to be dynamic based on the grouping you define. It would be best to refer to the actual values from the dataset using the Lookup function. See here for more info on that.
Edit based on feedback:
There are two ways you can go about this.
Remove the filters from the query and apply the filters on the tables. This way, you can use table grouping to separate out the numbers, but still compare them to the total. The difference expression would look something like this:
=Sum(Fields!Amt.Value) - Sum(Fields!Amt.Value, "RowGroupName")
With your existing structure, use a lookup like this:
=Fields!Amt2.Value - Lookup(Fields!ID1.Value, Fields!ID2.Value, Fields!Amt1.Value, "Dataset1Name")

Related

SSRS report multiple concatenate

I'm trying to join two data sets in my SSRS table report. The problem is that I can only concatenate two columns in my lookup statement. The third is being ignored. I need to do more than two. how can I achieve this? my values are duplicating in my drill-down report.
thanks for the help.
=Lookup(Fields!MONTH_OF_SERVICE.Value+Fields!REGION.Value+Fields!CLINIC_NAME.Value,Fields!C_MOS.Value+Fields!C_REGION.Value+Fields!CN.Value,Fields!CNT.Value,"DataSet5")
Without much more info on the datasets (data types, sample data from each dataset etc) it's difficult to offer much help.
In general though you can ...
Check that the datatypes of the corresponding fields are the same
Pad the values in in each column so they are the same width to avoid things like Month= 1 + Region = 1 matching to Month = 11 in the lookup dataset. For example if month is a number, format it to be 2 characters such as 04 for April
Add calculated columns to both datasets that will generate your lookup 'key'. The advantage of this is that you can show these temporarily in your report so you can ensure they are unique and the LOOKUP function is simpler as you will only be referencing a single field.

Report builder 3.0 Using Reportitems!TexboxXX.Value sometimes creates multiple boxes. Why?

I have 6 Datasets each one is the same query but has a different WHERE clause based on employee type. They generate 6 tables. At the top of the report there is a summary table which uses reportitems!textboxXX.value to grab the totals for 2 particular fields from all the tables. I'm also using a StartDate and EndDate parameter. Each reportitems! expression in the table comes from a different dataset in the report if that is relevant.
When I run the report using dates from yesterday back to the 9th of May I get the desired output.
But when I go to the 8th I get multiple rows all the same.
and as I go even further back I get even more rows of the same information. To my knowledge nothing interesting or different happened on the 8th of May and the tables further down the report look exactly the same. Any idea what might be causing this? The design view looks like this if that helps. There's no grouping or filters on the table.
Still not certain about the mechanics behind this but I found a 'solution' so I figured I'd post it. I just made a new dataset for my summary tables where the query was simply SELECT 1. Now I get a single row every time.

Working with SSRS dynamic fields

SSRS matrix table is a great way to generate dynamic fields as long as values exist.
However, is there a way to "always" show these dynamic fields even if a value doesn't exist for them? The report field locations varies based on data availability and users have to add missing columns in Excel manually.
Dynamic fields go from 3 to up to 30 (at least for now based on run by values). Adding these values manually would make the report hard to maintain.
The way I have handled for this is in the SQL. I build a table of all the values I will always want, I cross join that table to my final output table and update/insert values where they need to exist. That way I guarantee the rows, and eventually columns in the matrix, exists even if they end up being null.
Does that make sense?
Jesse's solution is a good one, but if for whatever reason you can't or prefer not to change the SQL you can do it in SSRS by forcing a blank value in the cell with a expression like this:
=iif(IsNothing(Fields!.xxx.Value)," ",Fields!.xxx.Value)

Report containing sums from different queries in Access

I am currently working with different tables and queries in Access and I can't find a way to do something very simple. I have the following :
Two queries, qry1 and qry2
One table, tbl1
Both queries and the table have a "NET" field of type float (or double)
What I'd like to do is create a very simple report which would give me the total of the NET column for each of those three objects. I have tried to insert a text box in a blank report and selecting sum(NET) on qry1 in Control Source but it doesn't work, it simply prints '#Error' with no more information.
If I use 'Add Existing field' and drag&drop 'NET' from tbl1 and then edit it to add sum it works but it is repeated for each row which is obviously not what I want. It feels like I'm missing something here or that I might not be using the right tool.
Thanks in advance for your help!
Have you considered the DSum() function? Create three text boxes and set the control source for each text box as follows:
=DSum("NET", "qry1")
=DSum("NET", "qry2")
=DSum("NET", "tbl1")
Note: Aggregate functions (e.g., DSum, DLookup, etc.) have poor performance compared to performing the calculations within a query. It's not clear from your question whether that's an option for you or not.

How to avoid summing of numbers in report model in SQL Server Reporting Services

In a report model I have some entities which have attributes which are integers (set to integer datatype) but should not be summed or aggregated in any way.
For examples ID's.
But when I create reports with the wizard, sometimes the report builder will try to sum the values even though it doesn't make sense to sum ID's.
For example let's say I have a list of cars sold in a month. In january I've sold 2 cars, one with the ID 101 and one with the ID 210. In report builder I will then - when using the wizard - get the number 311 for the summed values. I can remove it afterwards, but I would like this to not happen at all (since the end-users will be confused)
I need a way to say to the report model: This is an integer, but it is not really a number you should sum up
Well the wizard isn't perfect as you've found out. It does it's best in trying to figure out what to do. All that you can really do is remove =Sum(carID.value, "datasetname") when it automatically puts it there. Or if you don't need to sum anything at all delete the footer of the table. A workaround perhaps would be to do a Convert in your SQL to make your ID's a varchar.
If you drag an integer field onto the table it generates a sum by default. This is not always what you want - e.g. when the field is an Id or a status code that is the same for all rows shown.
Right-click the "<<Expr>>" and bring up the "Expression..." dialog. Replace "Sum" with "First" - e.g. =Sum(carID.value, "datasetname") becomes =First(carID.value, "datasetname") If the values are the same in all rows, then the first value will do. If not, there are also other functions like Last, Min, Max.
This is a bit of a kludge, but it works for me. I used my text editor to edit the RDL (XML) file and replace "Sum(" with "", then searched (carefully) for the ")" and replaced with "". I only replaced this inside of the ... Reopen in report builder without issues.