general forum

• K

  Rendering report with image sometimes takes to long
  • Karthik22296

  2
  2
  Posts
  4960
  Views

  

  https://playground.jsreport.net/w/jan_blaha/HUNmlyBw

  You could implement a custom helper converting url to base64 that aborts image download after some time.

  const jsreport = require('jsreport-proxy') const axios = await jsreport.npm.require('axios@0.25.0') async function imageToDataURIWithTimeout(url) { try { const response = await axios.get(url, { responseType: 'arraybuffer', timeout: 100 }) const base64 = Buffer.from(response.data, 'binary').toString('base64') return 'data:image/jpg;base64,' + base64 } catch (e) { return 'some placeholder image maybe' } } <img src={{imageToDataURIWithTimeout "https://jsreport.net/img/home.jpg"}} />
• F

  Load balancing with schedules?
  scheduling • • fmmich

  2
  2
  Posts
  4724
  Views

  

  Yes, there is a built-in mechanism. The schedule will run just once.

• R

  This topic is deleted!
  • reshmajacob93

  1
  1
  Posts
  22
  Views

  No one has replied

• R

  Report render failed: Invalid PDF: startxref not found
  • reshmajacob93

  3
  3
  Posts
  4872
  Views

  

  Are you able to replicate the problem in the playground?

• 

  Embeded Microsoft Excel in Angular
  • Thiago Akio Tanaka

  3
  3
  Posts
  5303
  Views

  

  Thanks!

• S

  html to xlsx merging cell issue
  • sbrown

  2
  2
  Posts
  3494
  Views

  

  This seems to be supported in jsreport v3 which wasn't deployed to the jsreportonline yet.
  We are working on it, but the migration path is more complex. We should deploy it to jsreportonline in Q2 this year.
  (There is no way for you to update on your own in jsreportonline)

• S

  How can I import an existing PDF into JsReport so that I can leverage the merge feature of pdf-utils?
  • sjd2021

  3
  3
  Posts
  5746
  Views

  S

  That worked great - thank you

• R

  Cannot set property offset of [object Object] which has only a getter TypeError: Cannot set property offset of [object Object] which has only a getter
  • reshmajacob93

  8
  8
  Posts
  9151
  Views

  

  I'm sorry I don't have further details. This is nodejs error code telling you there is not enough memory on your machine.

• 

  Converting to PDF times out
  • Axel Hallez

  5
  5
  Posts
  10274
  Views

  

  Is there a specific reason for the version choice?

  We wanted to keep a consistent chrome version across the official images and npm package. That time the 79 wasn't available for alpine yet if I remember it right.
  Also, the 79 version was sometimes 20% faster than the newer chrome versions.
  Nevertheless, the jsreport v3 uses chrome 93 now.

  If you want to try to use the same chrome version as it's in the jsreport 2.11, you could inherit from the official alpine jsreport image

  FROM jsreport/jsreport:2.11.0
• R

  Report generation takes too much time using dummy data
  • reshmajacob93

  5
  5
  Posts
  6480
  Views

  R

  ok sir

• X

  How to render a content contain '&' in the docx?
  • Xushlin

  5
  5
  Posts
  10166
  Views

  X

  thanks.

• R

  This topic is deleted!
  • reshmajacob93

  3
  3
  Posts
  220
  Views
• W

  '''Unable to access on-prem JSReport instance'''
  • Welzey1348

  3
  3
  Posts
  4189
  Views

  W

  We have the credentials in all environments, but when we enter them into one of the on-prem versions we cannot gain access. Below is a screenshot of our staging site with the username and password.

  [0_1643210018610_jsreport-stag.docx](Uploading 100%)

• M

  Configure https
  • Mashohle

  3
  3
  Posts
  4084
  Views

  M

  Thank you for the prompt response

• M

  Mark Folder as Hidden
  • mdeforest

  3
  3
  Posts
  6237
  Views

  M

  Great!

  I'll follow that issue for now.

  Thanks so much!

• O

  Carriage return text recipe
  • omasson-perso

  3
  3
  Posts
  4433
  Views

  O

  Great thank you !

• T

  Localization Helper in 3.3.0
  • ThomasJReiter

  7
  7
  Posts
  11930
  Views

  T

  For me it would be fine to stay with your current implementation and document the use-case somewhere in a how-to.

  Currently our complex case is implemented like this.

  async function translateWithFallback(key) { const template = jsreport.req.template const templatePath = await jsreport.folders.resolveEntityPath(template, 'templates') const folderPath = templatePath.substring(0, templatePath.lastIndexOf('/')) return jsreport.localization.localize(key, folderPath + '/translations') .then(translation => { return !translation ? fallbackTranslation(key) : translation }) .catch((e) => fallbackTranslation(key)); } function fallbackTranslation(key) { const defaultDataPath = "translations/en.json"; return jsreport.folders.resolveEntityFromPath(defaultDataPath, 'assets') .then(function(resolvedValue) { return JSON.parse(resolvedValue.entity.content.toString()); }) .then(function(data) { var v = data[key] return !v ? "[" + key + "]" : "*" + v; }) }

  Of course neither capable of special translation folders nor any other fallback language then English.

• A

  Incorrect parallel license usage on kubernetes deployment
  • AlexGoris-KasparSolutions

  7
  7
  Posts
  13464
  Views

  

  But are you sure that it's broken? Because I do see (development) in the license modal when looking in studio

  Because of the bug, the server thinks it runs in the production, but the studio thinks it runs in the development.

  Just for my information, is there any restrictions in the API when this license verification fails?

  I believe you mean when the parallel usage check fails. There are no limitations. Just the warnings you see. Everything runs the same.

• 

  Single Instance enterprise license on AWS Lambda
  • Andre Pechio

  3
  3
  Posts
  4902
  Views

  

  Thanks Jan,

  We are playing with different instance types and configurations, seems like it is going to work, we decided to limit the date range parameters for our reports.

• A

  Several questions for setting up SSO with authorization server
  • AlexGoris-KasparSolutions

  4
  4
  Posts
  8804
  Views

  A

  Thanks for all the great feeback @bjrmatos!

  I indeed overlooked the group permissions. This completely fixes that point I made.

  The feature to be able to map users to groups works perfectly, and combined with the group permissions, eliminates a lot of situations where the team would previously had needed admin access (and having to resort to using the shared credentials), like adding a new request under a specific group, or granting a new user access.

  Thanks again, it's so nice to use a product which ticks all the boxes :)