Posts made by Genhan

I have upgraded jsReport to v4.12, and Node version is v24.11, but I still see the promisify warning. I’ll review the beforeRender and afterRender scripts to see if any updates are needed.

Recently, our jsReport application has been generating a large number of the following DeprecationWarning messages. We are currently using jsReport version 4.3.1.

(node:3268) [DEP0174] DeprecationWarning: Calling promisify on a function that returns a Promise is likely a mistake.
    at node:internal/util:496:17
    at new Promise (<anonymous>)
    at beforeRender (node:internal/util:481:12)
    at executionFn (E:\app-reporting\node_modules\@jsreport\jsreport-scripts\lib\executeScript.js:73:58)
    at sandbox.js:50:18
    at async run (E:\app-reporting\node_modules\@jsreport\jsreport-core\lib\worker\sandbox\createSandbox.js:137:16)
    at async WorkerReporter.runInSandbox [as _runInSandbox] (E:\app-reporting\node_modules\@jsreport\jsreport-core\lib\worker\sandbox\runInSandbox.js:211:14)
    at async executeScript (E:\app-reporting\node_modules\@jsreport\jsreport-scripts\lib\executeScript.js:129:12)
    at async Scripts._runScript (E:\app-reporting\node_modules\@jsreport\jsreport-scripts\lib\worker.js:140:30)
    at async Scripts.handleBeforeRender (E:\app-reporting\node_modules\@jsreport\jsreport-scripts\lib\worker.js:64:7)

I am wondering whether upgrading to the next minor version might resolve this issue. Although these are only warnings, the high volume is significantly cluttering our error logs.

Yes, here is the config:

Thank you!

Hello,

I deployed a jsReport to our production environment and noticed that the header section is overlapping with the report body. However, when I tested this report in our test environment, it displayed correctly. See the following screenshots:

In test environment:

On production:

Do you have any suggestions on how I can troubleshoot this issue? Both production and testing servers are on Windows 2019.

Thank you!

Thank you for your suggestions, Jan. I discovered that the server might restrict external program's access to localhost. I will do more investigations.

Hello,

I deployed my jsReport application on Windows Server 2019, but its API endpoints are not functioning properly.

Here is the error:

Here is my sample request:

The jsReport studio is working:

Pinging API endpoint also returns correct response:

I successfully deployed the same jsReport application on both Windows 10 and Windows Server 2012, and it is operational on both OS platforms.

Any advice is greatly appreciated.

Thank you!

Thank you so much, @jan_blaha! Removing data/setting resolved the issue.

All our projects are about Angular + Express. I integrate jsreport with my Express app following https://jsreport.net/learn/adapting-jsreport#attach-to-existing-express-app . Our Angular programs just call jsreport API (https://jsreport.net/learn/api) to retrieve the reports directly.

In other words, we construct reports using jsreport studio - but our users only access Angular UI and the Angular UI will handle the communications with jsreport through API calls.

Hope it helps.

@jan_blaha , I shared the zipped data folder in Dropbox with you. Let me know if you received the share link.

Thank you,
Genhan

Thank you, @jan_blaha. I emailed you the v2 data zip. Let me know if you received it.

Best,
Genhan

Hi @jan_blaha , do you have a guide about how to add the xlsx template reference manually? I copied xlsx templates (e.g. PublicPrjXlsxTpl) into the assets folder manually - but it did not work.

Hi @jan_blaha ,

I upgraded to v3 again and captured the v3 template folder structure in the following screenshot:

The v2 structure in the xlsxTemplates folder is like:

Those ***.xlsx folders were created by the migration process.

Thank you,
Genhan

Hi @jan_blaha,

Downgrading Node to 14 resolved this issue, but we do need to update them in the near future

I will try your suggestion about linking xlsx templates manually. I think that it might resolve the issue - since I tried the same report in the playground and it works: https://playground.jsreport.net/w/anon/8iI_gl82 .

Sure. Where should I drop the original v2 data?

Thank you,
Genhan

Thank you, @jan_blaha. I am using Node 16.

After upgrading jsReport to version 3.1.1, a new error occurred:

Here is the full error message:

Error when evaluating engine handlebars for template /templates/PublicPrjs_Maps
Cannot read properties of undefined (reading '1')

(sandbox.js)

  150 |     const obj = ctx.root.$xlsxTemplate[filePath]
  151 |     const collection = evalGet(obj, path)
> 152 |     ctx.root.$removedItem = collection[index]
      |                                       ^
  153 |     collection.splice(index, 1)
  154 |     return ''
  155 |   }

(sandbox.js)

  462 |       }
  463 |
> 464 |       return fn.apply(this, arguments)
      |                 ^
  465 |     }
  466 |   }
  467 |

(sandbox.js)

  489 | }
  490 | function xlsxRemove (...args) {
> 491 |   return __xlsx.xlsxRemove.call(this, ...args)
      |                            ^
  492 | }
  493 | function xlsxAddImage (...args) {
  494 |   return __xlsx.xlsxAddImage.call(this, ...args)

TypeError: Cannot read properties of undefined (reading '1')
    at Proxy.remove (sandbox.js:152:39)
    at Proxy.<anonymous> (sandbox.js:464:17)
    at Proxy.xlsxRemove (sandbox.js:491:28)
    at Object.base.apply (C:\CPMS\iroot-new\cpms-reporting\node_modules\vm2\lib/contextify.js:246:34)
    at Object.<anonymous> (C:\CPMS\iroot-new\cpms-reporting\node_modules\@jsreport\jsreport-core\lib\worker\render\executeEngine.js:195:27)
    at Object.wrapper (C:\CPMS\iroot-new\cpms-reporting\node_modules\handlebars\dist\cjs\handlebars\internal\wrapHelper.js:15:19)
    at Object.main (eval at compile (C:\CPMS\iroot-new\cpms-reporting\node_modules\@jsreport\jsreport-handlebars\lib\handlebarsEngine.js:34:30), <anonymous>:71:113)
    at main (C:\CPMS\iroot-new\cpms-reporting\node_modules\handlebars\dist\cjs\handlebars\runtime.js:208:32)
    at ret (C:\CPMS\iroot-new\cpms-reporting\node_modules\handlebars\dist\cjs\handlebars\runtime.js:212:12)
    at Object.execute (C:\CPMS\iroot-new\cpms-reporting\node_modules\@jsreport\jsreport-handlebars\lib\handlebarsEngine.js:66:20)

Any other updates shall I do?

Many thanks,
Genhan

Hi @jan_blaha ,

I do not know what happened - but all the Excel reports suddenly did not work on my computer.

Here is an error example:

The exact same report is working on another machine:

All PDF reports are working fine.

Do you have any suggestions that I can follow to debug the issue?

Thank you,
Genhan

Hi @jan_blaha,

The same issue came back after I restarted our Express app.

Here are what I did:

1. Installed the updated express extension as you suggested
2. Started our Express app and it worked!
3. Restarted the same Express app and the same error appeared

Do you have any suggestion?

Thank you!

Thank you so much, @jan_blaha . The fix works!

We are using the jsReport library in our existing Express app. After upgrading jsReport from 2.6.1 to 3.0.1, we received the following error message during jsReport initialization.

Any help is appreciated.

Thank you!

May I ask what server (IIS, Apache ...) are you using to host this PDF?

Thank you!

Here is the generated PDF: https://www.dropbox.com/s/szn8diubiqkt8q3/Plans.pdf

We did use "pdf utils" to merge headers and footers. This PDF is hosted as a static file on IIS 8. I tried to open the file using Chrome 69.0.3497.92 and Firefox 63, and both failed.

Unfortunately it is hard to replicate the program in playground since it is connected with our local database.

Any suggestion is really appreciated.

Genhan