Thank you. I was able to replicate the problem. We have the fix ready and will ship it with the next jsreport update 3.5.0