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

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

Regarding v3 update problem, are you able to replicate this in playground?

It would be great if you email me your original v2 data in export. I would love to take a look at why the migration didn't process it correctly.

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

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

If it's possible, please send me the v2 data to jan.blaha@jsreport.net

Best,
Genhan

jan.blaha@jsreport.net
jan.blaha@hotmail.com

Thank you,
Genhan

I analyzed the migration of data there and it looks fine.
The problem is that the data already includes a flag that data were migrated so it doesn't run again.
Please remove file data/settings and start jsreport v3 again. It should migrate properly the xlsx templates to assets and fill the references for you.