Welcome to NPrinting. I have a similar project that I am working on with 23 columns and a similar requirement. I have attached two screen shots here that seem to solve your issue. Please review and let me know.
I put the headers above the level and each level is a unique number. In this case OrlID
Here is the result in Excel. Sorry this is not pretty. This is just some test data from the Surgical Demo Dashboard
Mike, thanks for the quick reply and example, much appreciated. It would appear this is working for you in the way I’d like to see as well, which is great. I may have left out a critical detail (sorry for the omission, it was late…), I am repeating of a few table dimension columns on line 1, but not on line 2, so the user knows the line has “wrapped”. This might be the difference in what I am seeing. I’m going to experiment with taking the Dim Columns out as I suspect they are triggering some type of grouping of the “line 1s” under the level. I’ll update shortly...
The actually QV table is now:
[Dim 1] (Unique), [Dim2] (Not Unique), [Dim 3] (Not Unique), Expr/Column 1,…. Expr/Column 14
Sample data in table:
D1A, D2,D3, E1, E2….E14
D1B, D2,D3, E1, E2….E14
In NPrinting, the level [Dim2] is a unique selection in my QV list box [Dim2], but NOT unique in the table result. Dim 1 is then the unique key for the table row (but not a level). I think its use of the dimension columns on line 1 could cause it to print all of line 1s together then line2s
<Dim1> <Dim2> <Dim3> <Column1>…<Column 7>
I have 2 ways I might go because the deadline is looming for this project:
Option 1: Is to keep experimenting with NPrinting to see if adding a RowNo() or some unique key to the row or replacing repeating dimensions with a variable would cause it to work per your example.
Option 2: which I actually have working because I was getting nervous and knew how to do this, is to simulate rows line 1&2 in the Qlik table using IF logic to set the calculations based on a higher level grouping dimension I call rowgroup. IF row is in rowgroup 1, use expression 1, if rowgroup 2, use expression 2, etc... Then I can convert the dimension columns back to expression columns in the table and just send it right to Nprinting as is without a line 2 in the template.
I'll keep updating the thread on how Option 1 so I can get back to a pure Nprinting solution as I remain curious why this isn't working as I am expecting.
Just to close this discussion for now, I never did get the line wrap working properly in the NPrinting template where the table had more than one dimension, but there was nothing wrong with the suggested answer as this is how the NPrinting product claims it should work as well.
I ended up just using a qlik table and a "row group" dimension (1 for row 1, 2 for row 2) with some IF, AGGR and NUM formatting statements to break things into 2 rows with different calculations per cell depending on the rowgroup and sent the qlikview table directly to NPrinting with a single row in the excel template. The report is working fine and the client accepted the design. I may try this scenario again in v17 when it becomes GA just to see if I can avoid this in the future and put another group of expressions for a large qlikview table on a 2nd row. Thanks again Mike for your responses.