i have checked both templates, i will try to explain why each template does not work as expected.

in both of your templates the table is defined with text wrapping enabled

when this option is enabled it causes the XML of the paragraphs around the table (both the the one at the top and at the bottom) to be affected. what does this mean?

it means that visually the representation of the nodes in the template is like this:

• previous paragraph (visually the one at the top of the table)
• table
• next paragraph (visually the one at the bottom of the table)

however, internally the real representation in the XML is like this:

• previous paragraph (visually the one at the top of the table)
• table
• next paragraph (visually the one at the bottom of the table)

this behavior produces different results on each of your templates

for template v2

the template produces tables overlapping because this is the normal behavior of a table with text wrapping enabled when there is no text around. if you put two tables with text wrapping enabled and there are no paragraphs around them, the tables will overlap.

in this case the loop in the XML is represented like this

• paragraph 1 (start of loop {{#each}})
• table
• paragraph 2 (empty one)
• paragraph 3 (end of loop {{/each}})

in our docx processing if we detect paragraphs with no more text other than the handlebars calls, then after processing the template, these paragraphs are removed in order for them to not affect layout, so based on this the final result of the loop is this:

------ iteration 1 -----------

• table
• paragraph 2 (empty one)
  ------ iteration 2 -----------
• table
• paragraph 2 (empty one)
  ------ iteration 3 -----------
• table
• paragraph 2 (empty one)
  ------ ...continues... -----------

this is why the final result is overlapping tables, because for sibling tables (that have text wrapping enabled) to render correctly in MS Word the internal representation should be like this

• table
• empty paragraph
• empty paragraph
• table
• empty paragraph
• empty paragraph

how to fix the template v2?

you have two options:

• you can either disable the text wrapping in the table
• or prevent the paragraph that contains the end of loop to be removed, if you go with this option then you only need to put a leading space in the paragraph that contains the end of loop. so it should look like this <empty space here>{{/each}}

with either of these solutions you should be able to produce the expected result

for template v2.1

in this case the loop in the XML is represented like this

• table
• paragraph 1 (start of loop {{#each}})
• paragraph 2 (empty one)
• paragraph 3 (empty one)
• paragraph 4 (end of loop {{/each}})

as you can see, the problem is clear, the loop does not wrap the table, there is only empty paragraphs in the loop body, so this template does not produce anything meaningful

how to fix the template v2.1?

you have two options:

• you can either disable the text wrapping in the table
• or you can put the start of loop in a paragraph that is not around the table, you can create a new paragraph before the paragraph 1 and there put that start of the loop, just similar to the template v2

i hope this clarifies the reason of the results, we don't plan to do something to change the output when tables with text wrapping is enabled, as described there is easy solution for this just by changing the template. applying a solution that might try to "fix" this automatically will cause side effects on other cases.

this was recently added on master, not released yet.

hi!

for template v2.1 is clear that the issue is that the loop does not output anything, for template v2 what is the issue?

it is the that the rows are overlapping each other, right?

i have added to the backlog to check this case, we will get to it.

yes, i have it implemented in my local, i am now working on adding it to docxTable too for feature parity

i took a look today and this usage was never intended to work. as the docs shows, you should either use pptxTable as a row loop, or a vertical column loop.

you are trying to use the helper in two rows and this is not supported, you should try using the dynamic columns variation to get your desired layout.

after checking this i now remember what is happening. in 4.5.0 we added the feature to generate dynamic cells to pptxTable. introducing this feature revealed that for both, the vertical and the dynamic mode, it was needed some kind of normalization for the width of the columns, otherwise depending on your data, you will get a table that does not fit in the slide, overflowing the slide boundaries.

so we added logic to distribute the existing full table width between the total of columns generated after the pptxTable processing. it is not the best but this ensures you don't end with a table that overflows the slide by default.

now it is clear to me that we need some kind of configuration in pptxTable to allow setting explicit column width, so this can be set and changed per user needs.

hi @PedroZimmer

the docs mention that you should use overflow: scroll in the cell to get text wrap enabled.

if you do it, this will be the result.

about the pptx issues i am about to start checking those soon, and about the playground we will try to prioritize its update, our backlog is quite full so we are fixing and implementing features, so playground got a bit behind, but we will update it soon.

what jsreport version are you using? i've done a test with latest jsreport (4.7.0) and it works.

using this data

{
    "data": [
        {
            "second": {
                "records": [{
                    "first": "Boris",
                    "last": "2",
                    "value": 1
                }, {
                    "first": "Matos",
                    "last": "22",
                    "value": 18
                }, {
                    "first": "Jan",
                    "last": "12",
                    "value": 10
                }, {
                    "first": "Blaha",
                    "last": "34",
                    "value": 8
                }]
            }
        },
        {
            "second": {
                "records": [{
                    "first": "Pablo",
                    "last": "48",
                    "value": 49
                }, {
                    "first": "Juan",
                    "last": "92",
                    "value": 16
                }, {
                    "first": "Martin",
                    "last": "45",
                    "value": 17
                }, {
                    "first": "Jhon",
                    "last": "10",
                    "value": 7
                }]
            }
        }
    ]
}

hi!

Is there some new setting that I have to set to keep the column widths correct?

no, i am not sure what could be happening for the column width change, we will take a look