general forum

• 

  jsreport 3 beta is released
  • jan_blaha

  3
  3
  Posts
  259
  Views

  M

  Wow, this seems like a really nice release. When do you think you'll release it to production? (edit: never mind.. I'll be patient =)

  Components! I can't wait to use them. We have a quite intricate setup with child report, which really are "components" Better async handling. I'm hoping for better async handling now whe you have reworked child templates. Better performance! Always wecome. Profiler.. will be great for digging out bottlenecks

  //Michael

• S

  Socket Timeout Exception - Unusual Scenario
  • saurabhjain176

  1
  1
  Posts
  5
  Views

  No one has replied

• M

  Basic Authentication - Provide sign-in information
  • MarioSchrattenecker

  3
  3
  Posts
  45
  Views

  

  Theoretically, you could try to do the same HTTP post the jsreport login page does.

  However, the proper solution would be to have an authorization server in place and use a single sign-on.
  Unfortunately, jsreport doesn't support the single sign-on to the studio yet, but we are working on it at this moment.
  It could be ready until the final jsreport v3 which should be release likely in a month.

• V

  Not able to access APIs on localhost installation
  • vatsalyagram

  6
  6
  Posts
  108
  Views

  

  You specified both httpPort and httpsPort in the config.

  Therefore jsreport started to listen on both ports, where the 5488 one returns HTTP redirect to the 5489 which listen to HTTPS.

  It's typically better to deal with SSL in a web server, I would recommend keeping just httPort:5489 in the config and use just HTTP when developing localy.

• O

  Custom module not found on AWS Lambda
  • omasson-perso

  3
  3
  Posts
  39
  Views

  O

  Hi Jan,

  Thanks for the quick reply.

  After more digging, it appears that my modules are found but not formatted as you expect.

  Actually, this is not working :

  'use strict'; const _createAccess1 = require('module1'); const _createAccess2 = require("module2"); const _createAccess3 = require('module3'); const _config = require("config"); const _mongoose = require('mongoose'); module.exports = function () { ... }

  but this is working :

  'use strict'; module.exports = function () { const _createAccess1 = require('module1'); const _createAccess2 = require("module2"); const _createAccess3 = require('module3'); const _config = require("config"); const _mongoose = require('mongoose'); .... }
• T

  jsreport/jsreport:2.10.0-full image in lambda - Runtime exited without providing a reason Runtime.ExitError
  • tyler-shuhnicki

  5
  5
  Posts
  116
  Views

  T

  Will do, thanks Jan.

  I was receiving an error earlier on about Lambda not supporting the image - I solved that by doing the following (note the first line).

  FROM public.ecr.aws/lambda/nodejs:12 FROM jsreport/jsreport:2.10.0 COPY --chown=jsreport:jsreport jsreports/data /app/data COPY --chown=jsreport:jsreport jsreports/license-key.txt /app COPY --chown=jsreport:jsreport jsreports/jsreport.config.json /app CMD ["sh", "-c", "cp -R /app/data /tmp/data&&node server.js"]

  Interestingly, though, I have since removed the first dependency and the function continues to work.

  Thanks for your help.

• D

  Asset created via odata API not accessible when @odata.type of Folder ref is set
  • dbaldes

  5
  5
  Posts
  328
  Views

  D

  OK, thanks for the update!

• T

  jsReport server stops using PM2 after startup
  • tshuba

  3
  3
  Posts
  93
  Views

  T

  Thank you for the reply, and I totally agree. We've been running jserport on many Windows servers for several years without issue. Recently, we've begun moving a few development machines over to Linxux and we know just enough to be dangerous.

  It does appear to be more of an issue with either node.js or PM2. I was just hoping someone here might have seen a similar error when following the install steps.

  I will continue researching the issue looking more closely at PM2.

  Thanks.

• R

  Cors Issue while saving Js report template using Odata
  • reshmajacob93

  2
  2
  Posts
  76
  Views

  

  hi! jsreport by default has CORS enabled, I have done a test from a simple app at localhost:4000 and jsreport running at localhost:5488 and everything works as expected, both the preflight (the one with request method OPTIONS) and the normal request (the one with request method PATCH) pass

  1.- Preflight request

  2.- Save request

  in your case it seems to be failing at the first request, which is the preflight request, since you have the api gateway in front of the jsreport server, it seems to me that this is a problem related to the api gateway, have you enabled CORS there? it seems to be easy to enable that in the console, maybe you are missing that step

• A

  Buying a license
  • AndreaUJI

  2
  2
  Posts
  101
  Views

  

  Thank you for your interest in jsreport.

  If I buy the one time enterprise license, I can only get updates for just next six months?

  Yes

  And, If a JSReport update comes and I am interested in, and the six months of updates have alredy finished, what would be the approximate price to be able to get that update?

  We provided a discounted package for another 6 months of updates for this case. It costs 445$. Please contact our sales at sales@jsreport.net when the time comes.

• G

  local jsreport stuck at rendering.
  • gundogduhasan

  4
  4
  Posts
  109
  Views

  G

  Thanks for your help. system32 path is missing in my environment variables path. I added it and its working. Thanks again.

• G

  sign pdf with trusted certificate
  • giona69

  4
  4
  Posts
  119
  Views

  

  Yes.

  We aren't Certifying Authority so we aren't providing certificates.
  This should be a list of authorities providing the signing certificates
  https://helpx.adobe.com/acrobat/kb/approved-trust-list1.html

  However, I never tried this out, so can't help you further.

• N

  Different margin for each page
  • Nathan-Nhat

  2
  2
  Posts
  125
  Views

  

  I am afraid that chrome can set the margin only for the whole document.
  Typically you solve your case by making an extra template with a different margin and you prepend it using pdf utils to the main template. Unfortunately, your "section 1" seems to be dynamic and spawns to multiple pages, so you can't use this approach. I don't know how to solve this at this moment.

• T

  An unhandled exception occurred while processing the request.
  • TunahannColak

  4
  4
  Posts
  116
  Views

  

  Don't you have your app pool configured to use more than one worker process?

  Could you also try to run the app outside IIS to see if it works?

• M

  Same old memory-crash problem =(
  • msageryd

  3
  3
  Posts
  110
  Views

  M

  I'll do that and get back to you. Thanks.

• M

  JSReport 2.11 not "killed" when express.inputRequestLimit breached
  • msageryd

  3
  3
  Posts
  105
  Views

  M

  Thanks.
  I'm taking care of the error codes at my client, so I'm sure that I didn't get one.

  Quite worrysome that a container can hang without ECS discovers this and kills the container.

  I have never seen this behaviour before. Maybe (hopefully) I won't see it again. I cannot recreate it, so I'll drop this.

• C

  Jsreport on Amazon Linux
  • Ch.K

  5
  5
  Posts
  216
  Views

  

  I tried it out and found this line was missing

  sudo yum install -y libXScrnSaver

  However, I was using the latest Amazon Linux
  Amazon Linux 2 AMI (HVM), SSD Volume Type - ami-07df274a488ca9195 (64-bit x86) / ami-07d397b752b4016f8 (64-bit Arm)
  So I'm not sure if the same helps.

• M

  Parse Error with docximage when getting src with #asset
  docximage docx • • Marsturix

  4
  4
  Posts
  147
  Views

  

  I agree that it is a bit confusing but I believe this is handlebars specific knowledge and our docs are not the best place to explain it, there are lot of handlebars references in the docs and adding explanation of the syntax will be overwhelming

• R

  Not able to start and install jsreport on window
  • RjSingh1529

  1
  1
  Posts
  46
  Views

  No one has replied

• M

  Getting Html Documents instead of docx when calling proxy.render on docx Template
  • Marsturix

  2
  2
  Posts
  115
  Views

  

  hi @Marsturix when you run from studio the render request executes always on preview mode so the results of the render give you the preview mode of the docx. when you render from the http api you should get the normal docx and not the iframe preview version

  I think if you want to force to not use the preview mode when you run from the studio then you can pass in the options

  let options = { "preview": false, "reports": { "save": true }, }