general forum

• M

  moment doesn't seem to parse date objects
  • mike-subtilis

  3
  3
  Posts
  23
  Views

  M

  Thanks for the response. It's pretty strange. In the mean time I'll use the workaround.

• 

  Protocol error (Page.printToPDF): Target closed.
  • AB-D

  11
  11
  Posts
  171
  Views

  S

  @jan_blaha
  Thanks for your quick responses :)

  So we use JsReport a little differently to normal case I think, our Request Data (or sample Data) contains URLS of where to get the actual data from, the reports JS file will fetch the data and populate the Request.data context for the template to iterate over.

  However this does not seem to be the problem as I was able to reproduce the error within our Docker test environment with just a Template and a large sample Data file (2000 records) side stepping the JS file altogether, reducing the sample Data to 1000 records and it runs fine - I have not found the breaking point

  But when I copied these 2 files to the JsReport Playground I was unable to make it error, it produced an 86 page document (which is not huge I would think)

  I have checked the Azure Webapp to make sure its not barfing on memory and its not, the VM is not huge but the memory graph shows its sits well under 10% usage always.

  The following Dropbox link has the Template and Sample Data, although I doubt its of much use since the Playground renders it fine

  https://www.dropbox.com/s/w7f59houwk2ao24/JsReport PDF Protocol Error.zip?dl=1

  Below is our straight forward Docker file, from 2.5.0 it installs a config override + a few extra NPM modules and our helper Node module - the Puppeteer downgrade to 1.11.0 also shown

  FROM jsreport/jsreport:2.5.0-full AS prod

  COPY jsreport.config.json /jsreport/jsreport.config.json

  WORKDIR /app
  RUN npm i
  request
  request-promise
  url
  tough-cookie
  @sendgrid/mail
  webpack
  round-to
  puppeteer@1.11.0

  COPY node_modules/virtualmgr /app/node_modules/virtualmgr

  and the jsreport.config.json which essentially overrides some timeouts (this is not a timeout issue though)

  {
  "httpPort": 5488,
  "allowLocalFilesAccess": true,
  "store": {
  "provider": "fs"
  },
  "blobStorage": {
  "provider": "fs"
  },
  "templatingEngines": {
  "timeout": 600000
  },
  "chrome": {
  "timeout": 600000
  },
  "extensions": {
  "scripts": {
  "timeout": 600000
  },
  "html-to-xlsx": {
  "timeout": 600000
  }
  }
  }

  I also tried using the Dockerfile from 2.4.0 as my "FROM" which built ok (and should have used Chromium 64 with latest NPM JsReport) but when I run it it errors with

  2019-08-19T14:51:52.991144204Z 2019-08-19T14:51:52.915Z - info: Initializing jsreport@2.5.0 in production mode using configuration file: jsreport.config.json
  2019-08-19T14:51:52.991177604Z 2019-08-19T14:51:52.924Z - info: Searching for available extensions in /app/
  2019-08-19T14:51:52.991183504Z 2019-08-19T14:51:52.977Z - info: Extensions location cache not found, crawling directories
  2019-08-19T14:51:57.726926059Z 2019-08-19T14:51:57.495Z - info: Found 31 extensions
  2019-08-19T14:51:57.731570662Z 2019-08-19T14:51:57.686Z - error: Error occured during reporter init Error: options contain values that does not match the defined full root schema. schema validation errors: rootOptions.store.provider should be equal to one of the allowed values. allowed values: ["memory", "fs"]
  2019-08-19T14:51:57.731588562Z at Reporter.init (/app/node_modules/jsreport-core/lib/reporter.js:141:15)
  2019-08-19T14:51:57.731594162Z Error: options contain values that does not match the defined full root schema. schema validation errors: rootOptions.store.provider should be equal to one of the allowed values. allowed values: ["memory", "fs"]
  2019-08-19T14:51:57.731599162Z at Reporter.init (/app/node_modules/jsreport-core/lib/reporter.js:141:15)

  this appears to be something to do with my Azure environment variable of

  "name": "store_provider", "value": "mongodb",

  which should be fine as this hasn't changed and surely mongodb is still supported ?

• 

  Generating a report with a lot of data taking longer than expected
  • Caleb Powell

  2
  2
  Posts
  55
  Views

  

  I believe the rendering spends 99% of the time in chrome pdf conversion right? You can see it if you run the rendering in debug mode. Or in the output logs.

  In this case, I would recommend removing the css styles and see the performance difference. There can be a particular style causing performance degradation and maybe you can work around it with a different style. As the second step, I would recommend to at least try/prototype the report without table elements. It seems to be poorly performing in my experience.

  You can also try to run the rendering on better HW of course.

  Sometimes it is also possible to split a long report into multiple sections. Run the rendering in parallel and use pdf utils to append the sections into one pdf in the end.
  However, this is not always possible and also quite complex to do. https://jsreport.net/learn/pdf-utils#usage-in-script

• R

  Error handling from javascript
  • RetoE

  4
  4
  Posts
  19
  Views

  

  If done(err) is returned, I want jsreport to fail the report generation and display the error message. The API request of the report should respond with a 500 server error or something like this.

  This is exactly what will happen.

• 

  Generate a PDF and apend existing PDF with Images
  • Juan D. Sanchez Zamudio

  1
  1
  Posts
  22
  Views

  No one has replied

• O

  How to format text? Font, color, and others... (XLSX)
  • odirleiborgert

  2
  2
  Posts
  25
  Views

  

  You typically prepare styles in the excel and then reference it in the cell.
  Try to open excel, style one cell, save it, unzip it and check how it looks.
  https://jsreport.net/learn/xlsx

  In case you just have a simple table, it is easier to use html-to-xlsx recipe.
  https://jsreport.net/learn/html-to-xlsx

• J

  Support for Docxtemplater pro
  • jamesamurr-bind

  6
  6
  Posts
  244
  Views

  J

  I was able to get this working. a few weeks ago. I had to modify the jsreport-docxtemplater module and the jsreport-scripts module.

  The jsreport-scripts change was just to allow more render calls in a pre-render script. Without this change I was limited to a max of 3 images I could put inside my final document. The change I made is documented in this forum post: https://forum.jsreport.net/topic/1170/error-reached-maximum-number-of-script-rendering-requests

  The jsreport-docxtemplater module change was to attach the image module to the docxtemplater instance and to auto detect the size of the PNG images I wanted to substitute into the document.

  The changes are all to the jsreport-docxtemplater/lib/recipe.js file. Around where the docxtemplater instance is being created and the document is being generated, the code now looks like this

  function base64DataURLToArrayBuffer(dataURL) { let binaryString; if (typeof window !== "undefined") { binaryString = window.atob(dataURL); } else { binaryString = Buffer.from(dataURL, "base64").toString("binary"); } const len = binaryString.length; const bytes = new Uint8Array(len); for (let i = 0; i < len; i++) { const ascii = binaryString.charCodeAt(i); bytes[i] = ascii; } return bytes.buffer; } // This function gets the width and height of a PNG. A PNG’s width and height are always bytes 16-24 of its byte representation. // Here is a stack overflow post where some of this is explained and shows how to convert the base64 to the width and height. //https://stackoverflow.com/questions/15327959/get-height-and-width-dimensions-from-base64-png // In node it works differently because there is no atob function. function getPngDimensions(base64) { // This is essentially the atob() function on the first 50 characters of the base64 representation of an image. // We only care to process the first 50 chars or so because we only need bytes 16-24 after it's converted. const header = Buffer.from(base64.slice(0,50), 'base64').toString('binary').slice(16,24); const uint8 = Uint8Array.from(header, c => c.charCodeAt(0)) const dataView = new DataView(uint8.buffer) return { width: dataView.getInt32(0), height: dataView.getInt32(4) } } const opts = {}; opts.getImage = function(tag) { return base64DataURLToArrayBuffer(tag); }; opts.getSize = function(img) { var sizeObj = getPngDimensions(img); console.log(sizeObj); return [sizeObj.width, sizeObj.height]; }; var imageModule = new ImageModule(opts); var zip = new JSZip(templateAsset.content); var docx = new Docxtemplater() .attachModule(imageModule) .loadZip(zip) .setData(req.data) .render();

  also had to add

  const ImageModule=require('docxtemplater-image-module')

  to the top of the file.

  For any of this to work I needed to first buy the docxtemplater image module. Once you've purchased this module you need to install it in your jsreport directory using npm. They will send you the command to run.

  After you've made the javascript changes above to jsreport-scripts and jsreport-docxtemplater you need to delete the existing jsreport-scripts and jsreport-docxtemplater npm modules from your jsreport app directory and replace them with your customized versions (copy/paste or you can just make the change the the existing module itself).

  To put this all together what I do is create a docxtemplater template with the appropriate markup for image substitution and in that recipe i create a beforeRender script that takes data posted to the template and posts it to another template which returns a PNG from a chrome-image recipe. I feed the return value from the image template into the data of the docxtemplater template. Below is an example of what I'm doing in the beforeRender.

  const jsreport = require('jsreport-proxy') async function beforeRender(req, res, done) { const promise1 = jsreport.render({template: {name: 'MyTemplate'}, data: {"myData": req.data.myData, "otherData": req.data.otherData }}); var myResult = await promise1; myContentAsBase64 = Buffer.from(myResult.content).toString('base64'); req.data.myImageData = myContentAsBase64; done(); }

  Reminder that if you want to generate more than 3 templates in this before render script that you NEED to make the corresponding change in jsreport-scripts module.

  And that's it! Hope this helps someone in the future.

• R

  License Verification
  • rrobertddean

  2
  2
  Posts
  32
  Views

  

  There is an automatic 30 days trial after you reach the 6th template.
  Try to restart jsreport, you should see this in the output log

  2019-08-15T09:24:47.699Z - info: Using enterprise trial license

  and you should see also trial warning modal

• 

  js report : Failed to launch chrome error
  • Rakesh Patil

  12
  12
  Posts
  577
  Views

  

  Thank you so much. That is exactly what I needed to do.

  Would be nice to include a link to that page in install instructions for other users of headless servers.

  I do like the report I am seeing. Now need to figure out how to write my own reports.

• C

  How to apply license key on Docker image?
  • cjrutherford

  4
  4
  Posts
  980
  Views

  

  hi! i think you can just set env var for license key in the azure application settings page.

  relevant post: https://jsreport.net/blog/render-reports-using-azure-app-service#configure-jsreport

• F

  API to create users?
  • fellars

  3
  3
  Posts
  37
  Views

  F

  Great, this should do it. Thanks!

• A

  Render footer content based on page number
  • ABoudreault94

  2
  2
  Posts
  35
  Views

  

  No. The chrome doesn't evaluate javascript in the header.
  https://github.com/GoogleChrome/puppeteer/issues/2167

  Try using pdf utils and merge the dynamic header instead.

• M

  TypeError: The header content contains invalid characters when encountering ™©®’
  • MKuenzi

  4
  4
  Posts
  131
  Views

  M

  Nevermind after looking through your source code it turned out to be easier than I thought (I thought I had to pass the template etc based on the documentation)

  var rs = new ReportingService("http://localhost:5488"); var report = await rs.RenderAsync(new RenderRequest() { Template = new Template() { Name = "sales-order" }, Data = data, Options = new RenderOptions() { Debug = new DebugOptions() { LogsToResponseHeader = false } } });

  Just a thought, if the Name property said something about the name of the template to render I would have intuitively tried it. (Right now it says "Readable name, does not need to be unique")

• A

  API OData Query filter operators not working as expected
  • Angelo4

  4
  4
  Posts
  60
  Views

  

  There is no configuration to disable this specific API call.
  Personally, I don't see a reason. Maybe you could elaborate more on this.

• P

  Drag and drop designer
  drag drop designer • • pauls-pan

  3
  3
  Posts
  335
  Views

  V

  The drag and drop designer would be just about amazing to offer to users.

• G

  Timeout with a lot of rows
  • gastonmunoz

  3
  3
  Posts
  53
  Views

  

  Please try to increase this configuration value

  { "templatingEngines": { "timeout": 60000000 } }
• V

  Import timeout
  • VincentSurelle

  11
  11
  Posts
  131
  Views

  

  It seems to be related to your particular export package if you say it doesn't work on your local pc as well.

  However, I've tried the 10mb export package and it imports in 1s.

  I believe it is not related to the actual content of your templates and data. You should be able to replace characters in your templates/data with some 'a' values and share the export with me.

• 

  API Timeout | JsReportOnline
  • Matthew Ward

  7
  7
  Posts
  121
  Views

  

  Unfortunately, you can't get response headers using browser client at this moment.

  However, in the real production, you would anyway use another method to make rest request and you can easily get the headers there.

• A

  Chromium revision not downloaded
  • ajphillips

  10
  10
  Posts
  397
  Views

  S

  @jan_blaha I did installation from the docker file like you suggested but the error still exists.
  Will try to set up manually and write result after that.
  Thanks for your kind answer.

• 

  Getting complete logs when using chrome-pdf
  • AB-D

  2
  2
  Posts
  51
  Views

  

  The size of the logs we store for jsreport studio startup is limited. This is hardcoded at this moment, unfortunately.
  However, you should be able to get standard jsreport logs in the file system logs/reporter.log. Would this work for you?