Topics created by OffBeatMammal

perfect, thanks!

thanks! Have reported to Sophos, though they don't seem overly inclined to do anything about it (shame I'm stuck with it on Corp machines)

d'oh ... on the subject of "..made a mistake" ... I'd created the asset with the helpers in, and referenced it as

{#asset common-handlers.js @encoding=utf8}

but ... I had a typo in the filename which was why it wasn't finding it. leaving this here so anyone else trying gets to search and learn from my stupidity ;)

Hi Everyone, can we add image dynamically using JS and display on the excel file using .xlsx recipe?

done, thanks Jan. very low priority (but might be applicable to the docx and pptx functionality as well over time) - https://github.com/jsreport/jsreport/issues/664

thanks for the detailed feedback - as I'd worked with OpenXML back in the day I like the way the xlsx recipe lets me get hands-on for some things, but also lets me re-use template items, but ... I also like the idea of moving more to a 'designer' view of things using handlebars within the Word doc (or PowerPoint or Spreadsheet) to achieve the same results without having to know as much about the internals. Will this new model also allow more than just handlebars (so if we want to do some logic within the document based in the data - ie use javascript or VBA to handle something more complex than just what handlebars will let us do) - if not, that's where the current xlsx model would be good to let us extend further.

I'd not tried using the docx as a linked asset, that would certainly save me a few steps as I experiment!

If my current use-case of a table with variable rows supportable, or should I drop in a feature request to github for that?

what would life be without interesting quirks :)
knowing the code workaround is good, and both the proposed solutions make sense (adding the options in v2 defaulting to false would surface the solution, and then in v3 flipping the default for new templates - especially surfaced with the checkbox in Studio - would avoid confusing people with the change)

I found some comments regarding this in this forum topic
https://forum.jsreport.net/topic/59/how-to-add-styling-to-cell-font-color-size-background-color-etc-to-xlsx/4

Btw I found it using the forum search button :)
https://forum.jsreport.net/search?term=xlsx style&in=titlesposts&showAs=posts

tried some small changes (but really need the reports to fit close to 'regular' A4 margins so don't have much wiggle room), and still getting the issue (not on every page, but see it appear both as an extra line at the bottom and a double weight line between the thead/tbody area on different pages.) - looks like this is another issue that should get addressed with the LayoutNG fixed in Chromium so hopefully that's not going to be too far away...

This is kind of a frustrating error, I also suffered this error on my chrome. I fixed this issue by follow some steps from here https://droidtheory.com/pdf-not-opening-in-chrome-fixed/ You can also try them, they worked for me

yes there was - thanks for pointing it out. was able to still get the same centering result I wanted with position:absolute and it doesn't repeat

ha ha! thanks for confirming... as I say, easy enough to fix and not worth distracting from other efforts

works perfectly in the afterRender, thanks!

playing around some more, it looks like the problem may be Sophos anti virus (as well as not liking the .exe Windows runtime, it looks like it might be blocking headless chrome according to some other reports) ... sigh. Time to see if I can persuade out security folks to allow it somehow...!

works perfectly ... thanks.
as there's a bunch of images and I won't know what they will be as new customers are defined in the database the dynamic (rather than import) is the best solution

thanks Jan - the fix seems to be removing the font-size from thead/tbody elements ... which isn't great!
I had tried chrome-pdf but the same report that's working fine in Phantom times out in chrome-pdf (will open a new forum request on that if I can't find a solution tonight)

The css solution is to use page-break-inside:avoid. See the chrome demo
https://playground.jsreport.net/w/anon/iDp6v2lI

The default phantomjs doesn't support this, however here seems to be a workaround
https://github.com/ariya/phantomjs/issues/10638#issuecomment-20186253