Prev
Next
Forums User Experience Lawson Design Studio

Design Studio custom screens on Chrome

 6 Replies
 1 Subscribed to this topic
 12 Subscribed to this forum
Sort:
Author
Messages
Ragu Raghavan
Veteran Member
Posts: 476
Veteran Member
5/10/2016 9:55 PM

    Has anybody been successful in making the custom screens work on Chrome?

    I have custom screens that make DME calls that work on IE - but fail on Chrome 50.x, Design Studio v10.x.

    As far as I can tell, Chrome does not allow synchronous calls and a DME call makes a synchronous http call.

    This is the message on the developer tools:

    “Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/”

    Any ideas how to overcome this ?

    Thanks.

    Ragu

    Terry P
    Veteran Member
    Posts: 234
    Veteran Member
    5/10/2016 10:09 PM
      I had to modify all my DME calls to work with Chrome and Firefox as follows:

      //Construct DME string
      sDME = portalWnd.DMEPath + "?PROD=" + strPDL
      sDME += "&FILE=GLNAMES&INDEX=GLNSET1"
      sDME += "&KEY=" + vCompany + "=" + vNewRetirementAcctUnit
      sDME += "&FIELD=DESCRIPTION"
      sDME += "&OUT=CSV&DELIM=~&NOHEADER=TRUE"

      //Return value from table
      var sReturn = portalWnd.httpRequest(sDME,null,null,"text/csv")

      Ragu Raghavan
      Veteran Member
      Posts: 476
      Veteran Member
      5/10/2016 10:19 PM
        Thanks Terry. What do the two nulls do ?
        Terry P
        Veteran Member
        Posts: 234
        Veteran Member
        5/10/2016 10:25 PM
          They are required placeholders for the call that are not used. This was the solution given by Support/Development when I opened an incident with them. Made the changes, and it resolved my issues when using other browsers.
          Terry P
          Veteran Member
          Posts: 234
          Veteran Member
          5/10/2016 10:29 PM

            Here was their initial response:


            "In the custom script, some of the server requests uses ActiveXObject("Msxml2.XMLHTTP") which is not supported on Chrome/Firefox. This is the one that causes the error. We can use portalWnd.httpRequest as a replacement for it and it is already being used on other function in the custom script."
            Demi
            Veteran Member
            Posts: 67
            Veteran Member
            8/19/2020 5:49 PM
              I would like to hear more about any Chrome required modifications. I've been tasked to make our design studio forms work in both IE and Chrome and before October 31 ! Yikes If the DMEs are different, can the same be anticipated for the AGS? Any additional information, or things to look for; would be greatly appreciated. I'm am just beginning to get familiar with Chrome's developers tool as well as becoming acquainted with the Infor OS platform, minus the IE development platform. So far, I've gotten a lot of spinning circles that I have narrowed down to lines that contain '.async', '.load' and '.loadXml'.
              Ragu Raghavan
              Veteran Member
              Posts: 476
              Veteran Member
              8/19/2020 10:06 PM
                This link may give you more details
                https://lawsonguru.com/fo...sults-from-ags-call/