Sql Report Builder remove extra rows - reporting-services

I recently started using Sql Report Builder and I'm having a hard time trying to figure out why are there some extra rows on my data.
Basically the grouping is, Referencia > Localizacao > Etiqueta, as you can see from the image. I tried checking my data directly from SQL but everything is correct and these extra rows make no sense to me. If I remove the Details group these rows disappear but then my Etiquetas aren't grouped by Localizacao
UPDATE
Here is the design view

Related

SSRS Published report from MySQL DB shows blank/empty rows

I have created a very simple report in Visual Studio (also tried it in Report Builder) that just returns 10 rows from a table in a MySQL (Not MSSQL) database. I changed the background and foreground color to make sure I could clearly see the rows in the report.
There are no parameters and it does not use a stored procedure. It's a straightforward SQL query:
select TASK_INSTANCE_ID, TASK_NAME, ASSIGNED_NAME, CREATED_DTTM
from task_instance where created_dttm > date_sub(now(), interval 1 day)
limit 10
Here's the result when previewing the report in Visual Studio. You can see that it is showing 10 rows of data.
I then publish that report to our SSRS server:
And when I view that report on the SSRS server I get 10 blank rows.
To confirm that I was actually seeing the rows and they were just blank, I changed the query to return just 5 rows. This shows that there are now only 5 blank rows, but with the defined background color.
For reference, I also created a simple report from an Oracle DB and published it to the same folder on the same SSRS server. This report works just fine.
So it appears to be something related to using a MySQL DB, but I have not been able to find anything that explains what I'm doing wrong. Any pointers/help will be greatly appreciated.
I then tried to add a couple new columns to the SQL query.
I used the ROW_NUMBER function to get the rownum of each returned row
I added a dummy column with a constant value for each row
Works fine in the Query Designer:
Works fine in the Preview:
Shows the new columns when published to SSRS, but still shows blank cells for the other columns:
If your problem is/was the same as mine then I think you will find that if you export your report to excel from the report-portal that all of the data that you expect to see is in fact present.
After some digging into the report properties and trying page width settings etc. I found that I had different values for the CanGrow property of the cells in the row and once I set them all to be the same -- True in my case -- then the report rendered as expected.
I am thinking that the reason that Excel showed the data is because it effectively ignores the CanGrow setting so having a mixture of them didn't matter.
I hope that this helps -- you or others who encounter it later -- as it was a really bizarre thing to encounter...

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.

Most Efficient Way to Display Multiple SQL Rows as a Single Row with Sub-Rows in SSRS Report?

The goal is to take the data shown in the "SQL rows returned" portion of the image and display it in the "How report should look" portion of the image. It's currently being done using a sub-report that takes titleID, languageID, beginDate, and endDate as a parameters from the main report. However, it's really slow to run when a significant number or records are returned. My question is "Is there a more efficient way to accomplish the same thing in the main report w/o using a subreport?" If more information is needed to properly assess this problem, I'll be glad to add it tomorrow. Thank you!
Purely looking at the image.. all you need to do is put a tablix on your main report add a parent group of title_id..
Then delete the column that is created to the left (but NOT the group)
Right click on the detailed group -> insert row outside group. This will create a row inside the Title_id group but Outside the detail group.
In this line.. add the title ID, name etc.
The detail lines will show the details.. obviously.. You need to play around a bit to figure out the rest of it..
It looks to be a fairly straight forward report.. not sure why you need to use a subreport for this

Report Builder (Digital Metaphors) add empty rows in details band until the end of page

I am using ReportBuilder 10 in Delphi 2006 with an Access 2000 database. I am trying to create a report using a filtered query.
Telerik Report : Starch line in Detail band or Add Empty rows
Repeat a vertical line on every page in Report Builder / SSRS
Similar to the questions above, I am trying to add empty rows (or records) in the ReportBuilder's details band after the filtered query records. Until it fills the page. My details band is like an excel table and it can take 25 rows per page. If I have 30 records, the first page is good. But the second page will have 5 records. Then, a huge gap will appear between the details and footer bands. That looks bad.
I tried to search for this, but nothing comes up. Only the second link above. But no solution I can use was posted.
I hope I properly explained my problem to you guys. Any help would be appreciated.
I don't know ReportBuilder well enough to give specifics, but I suggest
Adding 25 blank rows to the report's query result. You should be able to do this using a series of UNION commands. Make sure any sorting actions place these at the end of the results.
Create a boolean variable isBlankLine that is updated for each line of the details as it is being evaluated for layout. This variable simply is set to true if the record is a blank line (one of the lines added in step 1.)
Create another boolean variable isReportEnd that is evaluated on the page footer. This is set to true if isBlankLine is true, otherwise it is set to false.
Finally, for each detail line, suppress the line if isReportEnd is true.
This will allow the page to fill in with blank lines and suppress any additional pages. The only catch I can think of is that if the report ends with exactly 25 records, such that the first line of the next page will be a blank line, then your last page will be blank.

Report rows differ from SQL result

I am stumped.
I have a select statement that returns the data fine in the data pane, but in the resulting report, one row is our of sort order and falls about 25 rows down in the data where it shouldn't be.
How do I trouble shoot something like that?
Thanks!i
Somewhere in the report you must be sorting the dataset. In this case, the data will look fine in the data pane but will be out of the expected order in the report. Try adding a brand new table to the report and apply the dataset. It should match the data pane.
How do I trouble shoot something like that?
You start by posting the select statement here so we can help without having to hone our psychic debugging skills :-)
It's possible that you're not ordering on every column you think you are. It's also possible that SSRS re-orders the data even after you've retrieved it.
They'd be the first two places I'd look.