Thank you so much, @jan_blaha! Removing data/setting
resolved the issue.
Genhan
@Genhan
Posts made by Genhan
-
RE: Error about creating Excel reports
-
RE: Are there tutorials to integrate jsreport in angular?
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.
-
RE: Error about creating Excel reports
@jan_blaha , I shared the zipped data folder in Dropbox with you. Let me know if you received the share link.
Thank you,
Genhan -
RE: Error about creating Excel reports
Thank you, @jan_blaha. I emailed you the v2 data zip. Let me know if you received it.
Best,
Genhan -
RE: Error about creating Excel reports
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. -
RE: Error about creating Excel reports
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 -
RE: Error about creating Excel reports
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 -
RE: Error about creating Excel reports
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 -
Error about creating Excel reports
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 -
RE: Failed to initialize V3 after upgrade
Hi @jan_blaha,
The same issue came back after I restarted our Express app.
Here are what I did:
- Installed the updated express extension as you suggested
- Started our Express app and it worked!
- Restarted the same Express app and the same error appeared
Do you have any suggestion?
Thank you!