Posts made by bjrmatos

i just replicated what you were trying to do on your first comment (from the screenshot), and i see it works. see example here: https://playground.jsreport.net/w/bjrmatos/1TEWLWcV

doesn't this cover your use case?

hi!

it seems the problem is how your loops are generating the rows

in your first each you are generating: R2, R3 ... R6
the second each you are generating: R2, R3 ... R7
the third each you generate: R2, R3, R4

basically you are generating duplicated rows, and because of that when you see the file, the preview tries to self-repair the duplicated rows by given them new indexes, so that is why you your content being generated at different rows.

there are a lots of ways you can fix this, but the most simple i think is to group your data and in single loop generate all the rows that you need

this is how it looks for me using MS Excel on macOS. text truncated as expected because you are using a custom width in the HTML. i don't know why it looks different to you, is this MS Excel from Windows?

can you attach these as an export file? if the attachment here does not work send me the file via email to bjrmatos@gmail.com

It is when the file is generated using jsreport with same text width and cell content, the text is not visible. What could be the cause?

unfortunately the browser preview is a black box, we can not know the exact reason you are experiencing these differences

hi! the {{docxPageBreak}} has not been tested with more complex conditional logic. so i would not expect what you want to work, however you can share with us the template you have so we can take a look, maybe we find an easy solution to make it work, but we need a proper test case to run.

hi!

that the browser preview and the local Excel have a difference is a bug in the browser preview, which we don't have control over. always trust the local Excel preview.

however, if you click the cell in the browser preview, you will notice that it has the expected width, just that for some reason the rest of the content is visible because the next cells are empty, we can not change that, the browser preview is something we don't have control.

thanks for the bug report, you can track the progress for this here

thanks for the template, i will get to this soon.

hi! what you are describing is how docxHtml works by default, it is mentioned in the docs, if you want to preserve content defined in the same paragraph that contains docxHtml call then you need to use inline mode

hi! what you are asking is likely not possible at the moment but to be really sure i would need to know the exact output you want to produce. perhaps you can help a lot by sharing what would be your data, what is the output you expect to get and what is the ideal way you expect to define your template in the docx.

hi! can you please share the docx template and the data for this example? i think this should work and likely requires minor changes but i would love not to have to re-create the example if you already have it.

as part of jsreport 4.9.0 we can use a custom loader function to control how images are fetched. this can be used in both docxImage and docxHtml, see the updated docs 1, 2.

thanks, we are going to take a look after the jsreport 4.9.0 release (which we are currently preparing right now)

hi! you need to download chartjs and upload it to the studio (you can drag and drop the js file for chartjs to the studio entity tree) as an asset, then you just need to reference it in your html.

@Aylarann ok, i have created a request to support this, you can subscribe here to get updates when there is progress about it.

i think it is available from 4.4.0, anyway, you should update when you can to ensure it includes any bug fixes.

hi!

you can set table style to style="border: 0px solid red;" and ensure cells do not set any border styles and it should produce table with no borders

hi!

I was wondering if there is a way to create shape or dynamically modify the color of a shape that is present in the template ?

There isn't a built-in way to do it. how are you modifying the XML directly? the XML of docx (and other office related XML) have to be well-formed, otherwise you get a broken document that can not open, so this is likely what is happening with your direct modifications.

what shapes are you trying to modify? just that we get an idea if it is something we can easily support. perhaps you can share a docx with the shapes you plan to dynamically modify, and what modifications do you expect to make.

this is fixed now, it is going to be part of next release