I am working on my first report designed in Visual Studio (2015) SQL Server Data Tools.
My sub-report is only returning one record for each parent event though the sub-report's dataset is returning multiple records.
My Report:
On-the-clock-report in design view
The linking value for the sub-report is the field [EmployeeWorkSessionID]
The Sub-report
Breaks Sub-report in design view
The sub-report's dataset also contains the field [EmployeeWorkSessionID]
Sub-report preview #1
Sub-report for WorkSession 293
Run by itself this sub-report returns 2 records for WorkSession 293, including a Lunch still in progress.
Sub-report preview #2
Sub-report for WorkSession 288
Run by itself this sub-report returns 2 records for WorkSession 288, including a Lunch that is completed.
The (not so) complete report
The full report preview
The preview of the full report shows the first record for each WorkSession,
but none of the others. The EmployeeWorkSessionID's are associated with the correct Employee. The report space is large enough for three lines. The correct records are return by the datasets, they are just not displayed. The open lunch break (containing NULLs) is not the only record being skipped.
Any ideas?
This does not constitute and answer but is too long to fit in a comment...
Basically the design, from what I can see, looks OK. (BTW: Thanks for posting plenty of screenshots of the design and outcome, so many people don't..)
There are a few points and thing to try, more to eliminate them than solve it but give them a go and see what happens.
Make a copy first !
Check if any items have CanGrow = false and set them to true
(True is default)
Remove the rectangle around the report items
You have several text boxes overlapping, just ot be oin the safe side, move these so they don't overlap
Move the sub report so it's below the Breaks: text box
A few more comments just for reference.
The subreport placeholder in your main report can be smaller, it will expand to fit the content
You don;t need the blank space at the bottom of the subreport, the report will expand to fit the contents, any additional white-space, by default, will be appended under the subreport's tablix. In other words, shrink the subreport body as small as you can, this will also help to eliminate issues with pages spanning more than you want further down the line.
See how you go and post the results back here. Once these things are eliminated we can look further.
This issue is caused because SSDT Report Designer caches the data collected the first time you preview the report and does not rerun the dataset queries on subsequent previews!
Obviously some actions must cause it to renew the datasets because my report did change over the course on the days; but it did not change often enough to make it obvious what was happening. The solution below looked like it was working because moving the sub-report caused an update. But after that run the report data remained static while the database changed.
Here is a tool to reset (delete) the cached data.
And the stackoverflow article that saved (what's left of) my sanity.
My report was working the whole time; Visual Studio was being lazy.
If anyone knows of a way to force live data access for all previews I would love to know about it too.
Related
Hope you're well. I'm currently building out a report, but despite my best efforts so far, I can't get some information to populate within the report. It does not appear to me that salesforce is recognizing the field "Agent Incoming Connecting Time" within the object "AC_Agent_Performance". However, I can pull in some other fields within the same object into the Agent Performance report, so I'm not clear on what is not taking place in the field that I wish to see within the report. Here are some of the things that I've tried:
I have checked the access to the field. The first photo (Photo 1) Shows an example of a working object, the the second one shows an example of one that does not.
The API name seems to work, and is consistent with other fields within the object that work.
I have checked the page layout for the object (even though I don't think this is the issue), and I have mirrored other fields to the best of my knowledge that ARE populating within the report.
I reviewed the CTI flows to see if there was something missing in there on a lark, but there was nothing in there that would lead me to believe that this was the source of the problem.
I have tried setting up a new field in the object (formula), that references the field that I'm trying. to pull in, but that just returns a result of 'zero' for all values.
One thing that I have done that appears to be working, is I have set up a joined report, which uses both "AC Agent Performance" object and "AC Historical Queue Metrics" object in the report. The result that is returning appears to be accurate (please see the picture (picture number 3)). However, I don't think that this is the right way to go about this, and I don't want to do it this way. I want to use the report with one object rather than with two.
I know that permissions are the most likely issue, so I've taken a close look at these. Please let me know if there is something wrong with how I have the permissions configured. The First image depicts the 'Field Level Security'. The second image depicts the'field accessibility'. They are both like this, the whole way down:
Please note one other thing, which is that the last picture depicts a different field within the object displaying in the report.
Does anyone have any ideas on how I can proceed so the field "Agent Incoming Connecting Time" will display within the report?
Please also note, that these are objects that contain data that is populated from AWS' Amazon Connect.
This last photo, shows that the object does not have any information in it within the report.
If the field isn't populated there's not much you can do on the reporting side of things. You already tried "joined report". You should check why the integration doesn't populate it, maybe read integration documentation, contact the managed package's support...
The tables are connected with lookup or master-detail, right? In a pinch you could try making formula field on "AC Agent Performance" looking "up" and pulling the value from related AC historical queue metrics. If the relationship is other way around (performance -> down to related list -> metrics) you could try to make-do with a master detail and rollup summary field. I don't know this package, no idea if you can pull it off when you don't have full control over the fields.
If you can't really use the relationships and absolutely need to report on single table - you could capture intermediate results of the report to a helper table and then report on that. It's called "reporting snapshots". Or write some nightly (hourly?) batch that recalculates stuff and writes homemade "rollup" to these fields?
First off, I am new and just learning about databases and reporting functionality.
Background: Let's say that I am an end user and I have requested a report from my IT department. I know that my company uses SQL server and they generate SSRS reports frequently.The SQL Server database is connected to a PIM(product data) application. Within the PIM there is a numeric field holding a quantity of bulbs. In the event that there is no bulb, that field is left blank. I do not have access to our database or the reporting parameters. I am at the mercy of someone else essentially.
When I receive my report, I see zeros '0' for every item that doesn't have a bulb. That is not the desired output, I want to see the field as a 'blank' just as it is in our PIM system. When I expressed this to the report writer, he informed me that this could not be done because that is a numeric field.
Does this seem correct? Please help!! I am fighting an uphill battle. I have a job to do and it relies heavily on IT support. I now have to go to my boss and tell her that this can't be done. I also understand that I can manually manipulate the report myself in excel but this is time consuming and if this can be handled before the report hits my inbox, that would be ideal. If there is a solution that someone out there can relay to me, I would be so appreciative-Thanks!!
If the report is definitely generated in SSRS, it is absolutely possible to set zero values as a blank field. To me, it sounds as if the person responsible just doesn't want to make the change because it's a fairly simple fix. It's as simple as opening the properties window of whatever field needs to be fixed. Since the field is numeric, you would want to format the textbox as a number anyways. The highlighted option displays where this change can be made. There's actually three default options for Show zero as: being blank, a dash(-), or displaying (None).
I have a report using a SSAS dataset, basically gives me a Reps sales figures by customer. The rep field I use has one rep called ST, and within this field at a lower level, includes ST and STS. The report was previously built using a different rep field which was incorrect. Now I have changed it, the data for some reason is not accurate.
When i see the query in the designer, the figures for STS are visible when selecting the ST rep. However, when viewing the report in preview, these figures are now omitted. I have cleared the report data cache which has had no effect.
If I attempt to rebuild the report, then I get the data as expected. Is there any way of recovering the existing report, or does this type of thing happen without a seemingly good reason?
I have a report that has one table with two rows. The first row is just a header, the second is a subreport. The subreport consists of a single table. I want to pass one parameter into the subreport (Fields!patient_id.Value) and have the subreport repeat for every patient id. I have that working, but for some reason it inserts a pagebreak after every instance of the subreport when I look at the print preview, even though it could easily fit four of them on one page. I haven't set anything to insert a pagebreak at any place in the report or the subreport. I do want the page to break, but only when there is not enough room on the page to fit an entire subreport.
I've done enough troubleshooting to be able to say for certain that it is the subreport control or the subreport itself that is causing the problem, not the table. Any help would be appreciated.
Edit: It's also important to note that when I preview my subreport, there are no page breaks.
I found a solution. Instead of putting the subreport into the table, I put it into a list with a grouping expression of "=Fields!patient_id.Value".
set the ConsumeContainerWhitespace = True on the Report Properties
default is set to false and it attempts to preserve the blank space next to your table
I'm working on a series of reports which need to be shown in two languages so I've created a common header that I planned on embedding into the content of each report. I have two data sets, one that looks up a set of strings in English or French (depending on a parameter passed to the report), and another with numerical data.
The original header worked fine and when I extracted it into a separate report it also runs fine. I am just passing the name of the report to the subreport. When I run the main report, it seems that the values in my string dataset are all null (I've tried all of them) yet if I try data from my numerical dataset, the fields have values and get displayed as the title.
If I also insert a text field with the same expression to display the report title after the subreport, it works fine but the title still does not get passed to the subreport.
I cannot make any sense of why this would be happening, anyone have a clue?
I'm using Report Builder 2.0 and SQL Server 2008.
Thanks!
Alright, so I worked around this issue by simply passing my parameters on down to the subreports and letting them call the stored procs again. Not ideal since I now have to call that one stored proc 3 times but it probably won't be noticed.
I tried several other work arounds and received errors like rsAggregateInCalculatedFieldExpression, so my best guess is that this was caused by attempting to use an aggregate function (First) where it is not allowed but the error was never shown.