Forum Discussion
15 Replies
- angelaCatalyst II
I made a quick test in Open Release 2025 (=R35). I deactivated XSLTProcessor and XSLTDocument in the browser debugger. Not sure if it was the right approach!
This is what I get: I can still open Innovator, but as soon as I open a grid, I get this error message:
Used code for browser debugger:
// Simuliere Chrome ohne XSLTProcessor Object.defineProperty(window, "XSLTProcessor", { value: undefined, writable: false, configurable: false }); Object.defineProperty(window, "XSLTDocument", { value: undefined, writable: false, configurable: false });How to solve it?
- I am confident Aras will provide us more information in 2026. There is still some time and now hurry yet.
- I expect we have to customize the codetree to avoid XSLT related code is loaded on startup. To what I have seen im my quick text, code for XLST Reporting is loaded on startup, even if we don´t plan to generate an XLST report. XSLT reporting will probably die as feature, but I personally don´t see this one as a big loss. We have better reporting alternatives.
There are huge differences in the startup routine between I14 and I12/I11. In my quick 5 minute test I12 version seems a bit more easy to understand. But we will see.
Please note that all of the above are just my rough thoughts and may be technically incorrect!
- angelaCatalyst II
Great question! To what I see XSLTProcessor is still used in some corners in Release 37, so even newer versions are affected.
But I wonder which parts of Innovator still use XSLT at all? I right now think of the XSLT Reports. But we can replace these reports which a different technology. So not a an instant show stopper.
What other parts are affected? Maybe Project Management and TechDocs? I am not sure.