A fix for older versions of Infor CRM and Chrome incompatibility

At the end of May Chrome released a new version that makes it incompatible with the xstyle parsing of css that older Infor CRM clients use. You can read more about it here.

The fix for this is pretty simple but a pain in the butt to make since it requires editing the Sage-Combined.js file, which is minified for your inconvenience.

What you need to do is open this file which is located in the portal under support files\jscript\sage.

The file is minified but what you can do is search for “x-parse”. You should only find one instance of that. If we look at the unminified format of the function containing “x-parse” it will look something like this (note depending on your version of Infor CRM this may look different. However the general structure should be the same. You don’t want to copy the code shown here exactly if your code does not match exactly):

    function _1457() {
        var _1458 = _144b("x-parse", null, "content");
        if (_1458 && _1458 != "none") {
            _1451([eval(_1458)], _1452);
        }
        else { _1452(); }
    }

What we need to do is make one small change of adding “&& _1458 != “normal””, like shown here (again the exact code may look different based on your version):

    function _1457() {
        var _1458 = _144b("x-parse", null, "content");
        if (_1458 && _1458 != "none" && _1458 != "normal") {
            _1451([eval(_1458)], _1452);
        }
        else { _1452(); }
    }

Save this file and you are back in business. Note that this file also exists in the Customer Ticket Portal also and would need to be changed in the same fashion there.

As I said an easy fix but a painful one since it is in the minified format. Just a word of warning. This fix is actually bypassing the client side script code that was causing the issue. Because we have bypassed how it is handling the xstyle parsing of dojo, some areas of the system may not look the same. But hey, at least the system will be operational again in Chrome.

The alternative is waiting for a fix from Infor. A wait that is likely a long one.

ABOUT THE AUTHOR

Kris Halsrud

Kris Halsrud is a Senior Analyst / Developer for Customer FX Corporation.

2 Comments

  1. Kris – we experienced this with Chrome last year and at the time advised our employees to use IE. That worked fine up until today and now IE is doing the same thing. I applied the fix (we’re on Infor CRM 8.1) but it did not fix our issue. Any insights on how to get around this for version 8.1?

    Reply
    • Kris – never mind, we figured it out.

Submit a Comment

Your email address will not be published. Required fields are marked *

Subscribe To Our Newsletter

Join our mailing list to receive the latest Infor CRM (Saleslogix) and Creatio (bpm'online) news and product updates!

You have Successfully Subscribed!