Hello Qlik experts!
We have a unique challenge that we are trying to solve. We have a chart in our QlikView app that is displaying dates on the X-Axis and some measurements on the Y-Axis. Please look at the attached screenshot of the chart. The chart is connected to a server-side extension (SSE), so it sends all displayed data to the SSE and receives and displays the response data (dotted lines). The Qlik app allows you to apply date filters on the chart, however, we still want to send all historical data (dates and measures) to the SSE because it is needed to do the calculation (SPC chart). All of this works as expected, but the challenge we're trying to solve is - how can we only display the filtered data (X-axis) on the chart, even though we want to send filtered as well as historical data to the SSE.
In the screenshot below, we would like to only display the highlighted area of the chart. This highlighted filtered dates approach is a workaround that we would like to fix.
Thanks!
Related
The number of pages displayed when viewed in ReportViewer and in exported PDF are differing.
Eg: 50 records are shown in one single page of Report Viewer. But when Exported to PDF 45 reords come in page 1 and the remaining come in page 2.
Soution Tried:
1)Removed Top and Bottom Margins.
2)Reduced "Interactive Page Size" to match the page count.
But it is not consistent, as it is behaving differently with different number of records.
Can anyone tell me how should I proceed to achieve sync between the ReportViewer and exported PDF ?
Thanks
Short answer - you can't do what you are trying to do: the different renderers handle pagination differently, but appropriately for their output.
The HTML renderer is optimised for screen-based reading and generally allows more content per page than the print renderer does as the print renderer is constrained by the paper size that it formats to. Thus the HTML renderer allows more content on fewer pages for a better browser experience whereas the print and PDF renderers have to conform strictly to the page length.
The best illustration of this is the Excel renderer - the Excel renderer renders the entire report onto a single worksheet in most cases (for reports with grouping and page breaks set on the group footer it will render each group on its own worksheet). You wouldn't want the Excel renderer to artificially create worksheets to try to "paginate" your report or to put it all in one worksheet but insert the header into the spreadsheet rows every "page". It does the appropriate thing which is to include all the data in one big worksheet even though that may be logically thought of as one big "page".
The HTML renderer page length is determined (more accurately, influenced) by the InteractiveHeight attribute of the report (in the InteractiveSize property in the Properties pane for the report). However, the interactive height is an approximation rather than a fixed page break setting and your page breaks may still not conform to the print version even if you set InteractiveHeight to the same length as your target page length. This is because the HTML renderer will vary the page length to group the data together better so the interactive page breaks happen around about, but not always exactly, where the interactive height is set.
This is what is happening in your scenario where the report viewer shows 50 records on one page but the PDF has 45 on the first page and 5 on the second page. The report viewer is making the decision that since there are only a few records left to display it will just include them all on the one page rather than force the user to scroll even though the interactive height will be exceeded. Thus you get a better user experience but a variance in pages between renderers. The important thing about the report is the data and the experience with working with that data in that renderer, not that the pages are the same length no matter how you look at it.
See this discussion of rendering behaviour for more information on why what you are trying to achieve isn't achievable. Just educate your users that the browser pagination is optimised for their viewing pleasure.
I am new to coding in Objective C. Originally I was bringing in a string of data into my tableView and I was having a really tough time with spacing out everything row by row. So I just need some guidance as to whether or not I am headed in the right direction. I have decided to make a custom cell with multiple views within it. So if I feed each piece of the data separately into each view, would that do the trick of having each row align with one another? Do I need to have anything else within each view i.e. labels? Also how should I think about this code logically? I'm not sure how to send data to each separate view?
As you are new to Obj-C coding, go through this sample app.
This sample code demonstrates getting data from server in xml format, parsing the xml response, and displaying in a table, it also uses custom cell to display parsed data.
As seen on the picture below the x-axis is very crowded in this example. I do know that the scale can be changed in Core-Plotr via:
axisSet.xAxis.majorIntervalLength = CPTDecimalFromFloat(1.0f);
...so it will make it easier to read.
My question is if there is a way to automate the scaling of the axis so when it get too crowdy the axis label change to continue to be readable?
I guess that one way is to check the number of data points and change via code but it would be convenient if it is available via Core-Plot.
Here is a picture that shows my test graph:
When is get at this stage i would like to change it so it shows every 5th number and then every 10th etc.
Try the CPTAxisLabelingPolicyAutomatic labeling policy. There's a demo in the Plot Gallery example app that shows all of the available labeling policies.
So I'm working on this chart in Excel, and the chart looks like two sides of a triange, like the picture at the link below:
http://a.imageshack.us/img832/6207/triangle.png.
I'd like to make a line (like, with an autoshape for example) that connects the 2 endpoints to form a triange; ie a line going from coordinates (4,1) to (4,5). I tried doing this by creating a seperate data series in excel with the coordinates of the connecting line, like:
4,1
4,2
4,3
4,4
4,5
However, in excel, all lines in this chart must have the same x coordinates. Does anyone know how to get a connecting line automatically? Say, with a macro or something? Reason I ask is because I want to be able to change these coordinates, and I want the connecting line to adjust with very little effort (ideally I could write a macro and assign it to a button that when you click it would adjust the connecting line). I have some very limited macro experience, but this is just beyond me. The type of chart I'm using is a standard line chart, where the description given by excel is "Displays trends over time or categories". Anyone know of a good resource or have some advice? Thanks.
PS I solved this problem by changing the chart type to a scatter chart, but this messed up the axes and scale, and required that those be adjusted, so I think adding a line in this manner automatically will be easier.
The scatter chart worked OK.
Used formulas included in the following image.
Perhaps you should include an image showing the problems you found.
I created an RDLC report (based on a stored procedure) that contains lists. I need to display data from one of those lists in the report footer across every page. However this data only shows in a list on the first page, so that is the only page on which it shows in the footer also. I’ve researched this but haven’t found much information. Does anyone have a solution for this?
Something you can try, don't know for sure if it will work. Create a formula that returns the data you want to display, then put the formula field on a text area in the footer.
I ended up placing a textbox in the second page area, setting the text color to white and sending it to the back. If I hid the textbox (or table - I tried that too), the footer object could not reference it. So, setting the text color to white and placing it behind another object worked. It seems like this is a kludgy way to do a simple report operation but is apparently necessary.