Yes MS Excel in Windows.
Posts made by jitendra5792
-
RE: Text in a cell is not visible as whole: html-to-xlsx
-
RE: Text in a cell is not visible as whole: html-to-xlsx
I understand that browser preview is a black box.
But the following screenshot is from the Excel that I created manually on my PC. In that the complete text is visible.
But the file that is generated using jsreport does not show the complete text.
-
RE: Text in a cell is not visible as whole: html-to-xlsx
If we create an Excel manually on our PC with the same content, in that case, the behaviour is the same, like if the rest of the cells are empty, the complete text is visible.
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?
-
Text in a cell is not visible as whole: html-to-xlsx
https://playground.jsreport.net/w/anon/oC498X3B
We are using html-to-xlsx recipe with cheerio.
Please refer to this workspace.
When I view the preview in jsreport, the text in the first cell is visible as a whole even if the cell width is less and the content is exceeding. Because the next cells are empty.But as soon as I download the file and open in Excel, it does not show as a whole text. It shows truncated:
-
PDF reports are failing with large data - 80k rows
We tried generating PDF report with more than 80K rows on a Windows machine after setting it up following the steps: https://jsreport.net/on-prem (without any docker image)
The RAM consumption for 1 lakh rows was around 11 GB, but it generated the report successfully with div (We removed the table tags and created a div structure for the tabular report).
But in the containerised K8s environment, we get the following error:
We need to generate a 100k-row PDF report, and we want to do it with jsreport deployed in a containerised environment. Can you please suggest what we should do to overcome the error we are facing?
If we deploy it on a standalone VM, it works fine to generate the report.
This is a blocker for us.
Can you please suggest a solution? We suspect some issue around the puppeteer/chromium in the base image. We are using this base image - FROM jsreport/jsreport:4.7.0-full.