topic Re: Report trouble in QlikView

Report trouble

datanibbler — Mon, 09 Feb 2015 10:57:27 GMT

Hi,

I have an app listing the costs of our forklift fleet based on two separate Excel_files.

The output right now is a straight table with all the costs. It does not quite fit on the screen horizontally, so there is a scrollbar (when I print it in landscape_orientation, however, it does fit).

There is also a vertical scrollbar since there is more data than can be displayed all at once.

That might be key to my problem.

When I create a report with a filter so that there are only 2 lines of the table to display, all is fine.

When I create a report with all selections removed to have the complete list, it looks kind of weird. All columns of the table are squashed together in a very small area on the left and all the rest is blank ... Strangely, that 2nd report prints in portrait_format, although the settings are the same as in the other report, that is, landscape_format (I used that "copy datasheet from other report" checkbox).

Can anyone help me with that?

Thanks a lot!

Best regards,

DataNibbler

P.S.: No, I did not look closely - it does print in landscape_format all right, but everything appears very much squashed together.

Re: Report trouble

marcus_sommer — Mon, 09 Feb 2015 11:09:39 GMT

Hi DataNibbler,

it's not quite easy to create reports which looks good.Especially if there are many objects or the objects contain a lot of data ...

Within the object-properties you could define if the object should be showed with the origin-size or adjusted. Maybe you could also use multi-page reports and if you worked with the fat-client or IE plugin you should try it with the print from sheet (it's also not perfect but the handling is better).

- Marcus

Re: Report trouble

datanibbler — Tue, 10 Feb 2015 11:31:54 GMT

Hi Marcus,

I have not done a lot of work with reports before.

I now have five reports in this app and three of those are fine, they contain relatively little data - only up to a dozen lines or so.

The other two are supposedly much bigger and it's there I have that "squashed" look - so that is probably the reason.

What could I do now to split that into two pages, each page with just as many lines as can be done without that happening?

Re: Report trouble

Tue, 10 Feb 2015 11:46:52 GMT

Hi Data,

rather than a single page, you might be best to use a multi page for that table and then it will loop over the required number of pages instead of being all squashed.

You also probably want to create a second object specifically for that report, rather than re-using the main one in the application. I've found you need to make lots of little adjustments to the settings to make the look right on the report end.

Edit: Bottom line is report building in QV is a pain! If it's something you are going to have to do more and more, might be worth looking at something third party, like n-printing for example.

Hope that helps

Joe

Re: Report trouble

marcus_sommer — Tue, 10 Feb 2015 11:50:31 GMT

Hi DataNibbler,

within the properties from report / data-sheet you could set it to multi-pages and could then use different options for printing. I use for a report with usually 3 - 4 pages the setting fit to 1 - 100 pages - and it worked.

- Marcus

Re: Report trouble

datanibbler — Tue, 10 Feb 2015 11:55:04 GMT

Hi Joe,

you're right - making a report look really good IS a pain, and it IS something I'm going to have to do more and more (I actually hope so, it might be a way to get more management_focus on QlikView).

The chances of getting the budget for a third-party_tool are slim - depending on how expensive that is - but I'm going to think about it to make my life easier - as long as I can't see us employing anyone to boost the development_team.

In this instance, however, it's just about plain-vanilla reporting, so the look of it doesn't matter much.

I will try different options to make this a multi-page report.

Re: Report trouble

datanibbler — Tue, 10 Feb 2015 11:56:49 GMT

Hi Marcus,

would you mind posting a Screenshot of exactly what you mean I should use?

I'm not quite sure where that setting is or if we're thinking about the same thing.

I have tried something - I'm not sure that is what you meant - but that splits it by ID, so I get 56 pages with just one line each. That is not quite what I want - two pages should do. So I guess I need some formula in the table that I just don't display, to split it all into groups of 10 or so.

Re: Report trouble

marcus_sommer — Tue, 10 Feb 2015 12:06:20 GMT

I mean this:

- Marcus

Re: Report trouble

datanibbler — Tue, 10 Feb 2015 12:08:20 GMT

Hi,

I have just found out something different that, however, seems to be quite practical: I tried using the rowNo() function right behind my 2 dimensions to have something to use to split that table into parts - and it seems that uses the 2nd dimension (not the 1st) to group the table and it counts the nr. of unique IDs (my 1st dimension) there are in every value of the 2nd dimension.

Is that the way this works or is there something more to it?

However, I'm not really closer to what i want. I have 2 separate tables in the data_model, I haven't gone to the trouble of joining them, so I cannot just use a rowNo() function in the script.

@ Marcus

That results in 28 pages, but every other page seems to be empty!?

I'll try using a rowNo() fct. in the "master_list" in the script.

Re: Report trouble

marcus_sommer — Tue, 10 Feb 2015 12:20:38 GMT

Generally could it be a way to use separate print-objects and split them by using to count their rows - maybe by using directly a rowno() or a calculated dimension with ranking or similar or by creating a rowno-counter within the script. An alternatively could also be to use a field through which the report switched by a print-job.

But before try it with the options from the multipage-settings.

- Marcus

Re: Report trouble

datanibbler — Tue, 10 Feb 2015 12:25:28 GMT

Hi,

I'm just trying the following:

- I add a line_ID in the "master_list" in the script - I load the other one with a WHERE EXISTS() clause, so there
should be no gaps there.

- Then I create a secondary ID by grouping that into buckets of 10 or 12. I suppose that could be done with the
IntervalMatch() function more elegantly than I can do it directly on the GUI.

- I will then tick the "serial printing" checkbox that is on the "selections" tab of the "report settings" in the
report_editor and select that latter field

Re: Report trouble

marcus_sommer — Tue, 10 Feb 2015 12:37:15 GMT

Hi,

instead of intervalmatching I would rather try it with an adjustment from rowno per rounding or mod() like:

floor(rowno(), 10) as Counter

- Marcus

Re: Report trouble

datanibbler — Tue, 10 Feb 2015 12:40:27 GMT

Hi,

yes, that would also have been possible and maybe easier.

But I did it with the IntervalMatch() now. Now the last two reports look fine - they are now split into pages, with 10 line_IDs on each page. The one for one plant now is a bit longer than necessary because, due to the filter, there are not necessarily 10 lines on every page and so the nr. of pages is more than necessary. Here your method is probably better as it would be recalculated with every selection. I will try.

P.S.: No, that won't make it easier as I cannot select, for the "serial-printing" setting of a report, any fields that exist only on the GUI. So I'd have to make that in the script and again it would be insensible to selections.

Never mind. I guess it's good enough and there's tons of other work waiting, so I'll leave it at that for now.

Thanks for all the help!