Aras 11SP9 Chrome remove XSLTProcessor

Tick Tock... it would be good to at least know their plan to address it by 11/17

Any news on this one? I haven´t testet it, but R38 looks like it still uses XSLT. 

For those interested in more info on the depreciation of XSLT in chrome as well as chromes guidance on migration for developers who utilize the browsers XSLT API.

https://developer.chrome.com/docs/web-platform/deprecating-xslt#:~:text=Chromium%20has%20officially%20deprecated%20XSLT,XSLT%20from%20their%20browser%20engines.

One potential migration path they reference is a Chrome extension that would polyfill any use of the old XSLT API for web apps that users don’t have permission to change, and might work as a temporary fix for some users if Aras does not provide a hotfix for their version Aras Innovator.

Gosh.. We've got a major part of our output based on the XSLT reports. I'll subscribe to this topic just to be updated 

I just created a standard SSRS Report in for Innovator and noticed  something interesting. Even regular SSRS reports will be affected! Well, not the reports directly, but the way we call them from Innovator. 

Aras will have to reinvent the complete Report ItemType!!!! For SSRS we can still use Methods as fallback if no patch is available. But the patching they will have to do is massive!

For people who are not prepared, this will become Ara-Geddon! 🤣

Some update:

• Aras is aware of the issue and works on it.
• I don´t have a patch yet.
• It´s unclear whether XSLT Reporting is still supported in the future.

The main question is not whether we will receive a patch for I14, but whether patches will also be provided for I12 and I11. There are still active subscribers using I12, while I11 is barely in use anymore.

There is a small risk that Aras will release the patch only for subscribers. However, this is not a major concern. Experience shows that such fixes usually find their way into the wider community sooner or later, and Aras is well aware of that.

More likely, the patch will be bundled with subscription-related marketing :)

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?

1. I am confident Aras will provide us more information in 2026. There is still some time and now hurry yet. 
2. 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!

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.