Hi,
I'm receiving this error randomly while loading report or navigating to next page of report in ASPNET MVC. Any hint what is causing this issue?!
Uncaught TypeError: marginsPx.replace is not a function
Uncaught TypeError: marginsPx[i].replace is not a function
Re: Uncaught TypeError: marginsPx[i].replace is not a functi
Hello.
What version of our product you use?
Could you send more information about the issue?
How can we reproduce it?
Thank you.
What version of our product you use?
Could you send more information about the issue?
How can we reproduce it?
Thank you.
Re: Uncaught TypeError: marginsPx[i].replace is not a functi
We use Product version: 2015.2.3.0. We've tried with your latest version as well.
Well, regarding reproducing it I couldn't track it. It happens when we wan't to display/view the report embedded in our site. We design the report in your designer, we save it, template is saved in our db, then we come back to the website and reload the page to view it. If you can suggest any hint what can cause this we would give a try!
Sometimes after many page refreshes, randomly it happens to display 1st page but when trying to navigate to other pages it shows same error again (can't navigate).
Thank you.
Well, regarding reproducing it I couldn't track it. It happens when we wan't to display/view the report embedded in our site. We design the report in your designer, we save it, template is saved in our db, then we come back to the website and reload the page to view it. If you can suggest any hint what can cause this we would give a try!
Sometimes after many page refreshes, randomly it happens to display 1st page but when trying to navigate to other pages it shows same error again (can't navigate).
Thank you.
Re: Uncaught TypeError: marginsPx[i].replace is not a functi
Solution is in build 2016.1.26.
Thank you!
Thank you!
Re: Uncaught TypeError: marginsPx[i].replace is not a functi
Hello,
Am I right that the issue is already fixed for you in the mentioned build?
Waiting for your reply.
Thank you.
Am I right that the issue is already fixed for you in the mentioned build?
Waiting for your reply.
Thank you.