@NickBok turn out this is already supported, just that there is no special cell type for it, it is just a matter of changing the format of the cell, the format for "Text" is @ so you can apply it like this:

data-cell-format-str="@" or using the enum data-cell-format-enum="49"

i agree that this is not clear, so we will change the format docs to add a mention the equivalent to the "Text" format.

regarding the image, shall I upgrade the jsreport version?

this is a fix i have done directly in jsreport-docx repository, it is not released yet. however you can install it right now on your local if you execute npm install jsreport/jsreport-docx

could you please provide a full docx helper guidline for me? I look at the docx recipe api, but it have less description and helper(https://jsreport.net/learn/docx), we will convert all pdf report to docx. maybe we will display all forms in the docx.

can you clarify what you mean by "full docx helper guideline"? the docs describes the helpers always in a general way, and in terms of usage, actually, all our docs are similar to that. we are aware that more guided docs in terms of practical steps are lacking, but so far the current docs and the live demos on playground is all we have.

if you need more help with other specific cases in which you get stuck, or maybe find a bug just post another topic here in the forum, we always try to do our best to help with finishing reports.

after checked a bit more actually there is no problem with generating the checkbox in loop, your template produces warning in docx because the image, i will check why

so the problem about this was that your template downloads an image at https://projectportalstorageprod.blob.core.windows.net/png/xusl@shinetechchina.com_20171123111536_MVP%20ro%CC%88d%20(kopia)%20(kopia).png such server returns the content-type header as png, and we were expecting it to be a valid mime type like image/png. i have already added some code to handle servers that respond like this. so this part is fixed

update:

3.- producing a checkbox (and probably other form control) inside a loop (like {{#each}} or {{#docxList}}) can render fine in the word viewer, however it produces an invalid docx that when you try to open on local shows you a warning

after checked a bit more actually there is no problem with generating the checkbox in loop, your template produces warning in docx because the image, i will check why

ah i see, thanks for the simplified example. unfortunately, i don't know a proper fix to this, it looks like chrome just brokes the layout when there is cell with rowspan that passes page boundaries. if you find something let us know, this looks like a common issue when using tables, i will also keep searching if there is some kind of css trick for this

Hi! there are like three problems here:

1.- you are using the docxList helper but it is not used from a list/list item, the docxList requires that you use the helper inside a list. this sample shows the correct usage of the helper inside a list. in your docx you don't a have a list, just a simple text structured to make it look like a list.

2.- the other problem is that nested docxList are not supported currently

3.- producing a checkbox (and probably other form control) inside a loop (like {{#each}} or {{#docxList}}) can render fine in the word viewer, however it produces an invalid docx that when you try to open on local shows you a warning

we need to fix the point 2 and 3, for your case you can still make it look like a list and continue with the design if you change the docxList calls to each, something like this:

it will still produce a docx with a warning but if it someting you can view just fine and works to continue with your prototyping.

we will work to fix point 2 and 3, and post here when it is done

i don't get it, does not work when your folder has a space? if so, what is the error message?

Hi! the services is installed from the directory in which the app is present, for example if my project lives on C:\workspace\jsreport2.8.0 and i run jsreport win-install then the windows services is installed and started from C:\workspace\jsreport2.8.0\..

Hi! hmm i don't have a good trick for this. or at least if there is something that can be done, it is better if it is shared on the playground so we can change and test it quickly, if you are fine with that you can share your template in the playground with some dummy data that replicates the issue and then we can take a look if there is some kind of css trick or option that can be apllied

Hello, the reason it does not render by default on playground or on your local, it is because your reports takes like 79 seconds to render, you can have it render on your local if you increase the reportTimeout to 100000 in your configuration.

however your template is missing a critical pdf-utils optimization, which is the usage of the "merge whole documents" https://jsreport.net/learn/pdf-utils#merge, you report is currently doing two extra renders per page (to render the header and footer), which gives you a total of extra 120 renders being produced just to produce the header/footer for each page. you can reduce those renders and the whole render time if you use the "merge whole documents" option in pdf-utils, with that optimization you should be able to just have 3 renders in total which will dramatically speed the time your report takes to generate. check this example to give you an idea how to enable the "merge whole documents" and the modifications you need to do to the header, footer template.