As Chrome plans to remove support for XSLTProcessor, Aras 11 SP9, which heavily depends on this technology, will be impacted.Could you please provide a hotfix or an alternative solution besides upgrading the system

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 :)

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.

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!

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.

IMPORTANT UPDATE! Aras has released patches for every version above R22! Perfect timing, as there is still plenty of time to test and implement them.If you plan to upgrade anyway: R39 already fixes the issue. Just note the SSRS/Power BI information in the release notes.Question to Aras:Could you provide the patch for the community releases 2025 and 2023? These should correspond to R23 and R35, but it would still be helpful to have an official patch specifically for these releases.There are still many users running these versions, and not everyone will be able to switch to a subscription in time. In many cases, these versions are also used for test systems, which still need to be secured.Anyway..thanks, Aras! From what I have seen, this has been handled really well.

Aras 11SP9 Chrome remove XSLTProcessor

20 Replies

angela
Catalyst II
1 month ago
-
angela
Catalyst II
1 month ago
Update: Aras will not provide any patch for the open community.

For those with more than 1,900 contributions to this forum: no, this still does not qualify you for the patch. We´re sorry.
Anyone affected and interested in creating a community-based patch is welcome to join the group. Let me know! Using Innovator 10, 11 or 12? Every version welcomed!
- patricia_baxter_matrix_co_nz
  Ideator I
  26 days ago
  Hello Angela,
  I am interested in the community based patch for Release 12SP9. Could you please help.
  Thanks,
  Patricia
  - angela
    Catalyst II
    26 days ago
    Hi! I am working on a I12 version. I already have some of the fundamentals needed.
    If I succeed, I will post my result.
    If I fail, there is a fallback that will give us more time.

Forum Discussion

Aras 11SP9 Chrome remove XSLTProcessor

20 Replies

Recent Discussions

Does anyone see performance issues in Chrome

Aras 11SP9 Chrome remove XSLTProcessor

How to highlight a custom CUI Button like the Notification Button based on events of interest?

Is it possible to create custom ConversionServer tasks without external DLL?

Edge upgrade kills search grid - find workaround here