Topics created by Happy Patel

I'm afraid there isn't a good solution. Chrome needs to print the PDF from your rich html/css so it needs to use a lot of vector graphics in the final pdf source. The acrobat on the other hand needs just simple code to be able to edit stuff like bullets or tables. Maybe there is a solution but I don't know it at this moment.

No, I am afraid you need to update.

You can use jsreport.pdfUtils.parse in the script to count the pages in a particular buffer.
https://playground.jsreport.net/w/admin/UpVVJcAk

Thanks! @jan_blaha It's working with merge footer operation should use "merge whole document" option

Thank you!

I don't know any css/html solution that could help. I guess you need to merge it there with pdf utils.
Althought, maybe someone else know

I'm afraid chrome has no such "magical" option.

Although you may try to search in puppeteer repo for some CSS tricks that could help
https://github.com/puppeteer/puppeteer/issues

For example, here I see a CSS trick for font issues in word.
https://github.com/puppeteer/puppeteer/issues/4125#issuecomment-578723661

Thanks! @jan_blaha it's working now

You didn't mention what version you use... but if you have some problems, testing it with the updated version is a good thing to do for better problem isolation.

That depends, details are described here.
https://jsreport.net/blog/jsreport-300-released
https://jsreport.net/blog/jsreport-400-release

Note if you want to update to the v4, you need to update to the v3 first.

Got it Thanks! @jan_blaha

Hello @jan_blaha

I have used original docx recipe and when I download it from local and send it in gmail the preview is working fine but when we test it on server then it is not working. Do you have any idea regarding this?

Thanks!

Thanks! @admin It's working fine

Thanks! @admin

Do you mean with html output? Of course, you can do anything you want there. The simplest is to just provide all required data to the page and code in js the switches.

Or you can take the approach we described in this tutorial
https://jsreport.net/learn/live-reports
(playground demo isn't working now, gonna fix it)

hi @Happy-Patel

it looks your code is the right way, there are multiple ways you can simplify it, one way is that instead of adding pdf page item per property value, you just use a single call with all the properties. then in the header you are sure your data is in the 0 index, and can create just a single function for all your properties access.

if you need to conditionally render something based on the avatar you can still do it in the header, from the main you can just propagate the avatar value (without the if) no matter if it is undefined or not

here is a demo
https://playground.jsreport.net/w/anon/EoeNYCW3

If you use pdf utils to merge header with page numbers, you aren't limited and you can code any algorithm for page numbering you like.

Thanks! @jan_blaha

Can we do anything for this?

hmm i don't know also, this is hard because there is no way to detect the cells that are going to be on next page, so it is not possible to style cells differently, you usually want to ensure same style across pages

@Happy-Patel hmm why don't you use multiple rows in the tbody? i mean, why you put such a big content there in a single row? a single row with large content is not going to break nicely, chrome does not know at which point it should break it, one big row is going to overlap this way because chrome won't have a good idea to break the parts.

perhaps a good idea is to try to refactor the layout to use multiple rows