Unhandled Script Exception

  • Unhandled Script Exception

    Posted by DSC Communities on July 7, 2017 at 3:10 pm
    • Rebecka McKinney

      Member

      July 7, 2017 at 3:10 PM

      Hi everyone,

      We recently did an upgrade from GP 2013 to GP 2016. Everything seems to have went fine except when we go to enter a Receiving Transaction through the Receivings transaction window, we get an error. I can open the window easily, but when I click on Receipt No., I get an error message that says:

      “Unhandled script exception:
      Illegal address for field ‘Invoice Receipt Date’ in script ‘Display Receipt’. Script Terminated.”

      This issue seems to be consistent across all companies. It occurred in one of their lives companies and when I checked their test company, it also exists there. It also is not confined to one user. Another user discovered the issue and then I tested using ‘sa’.Ā 

      Any ideas on what this may be or how to resolve?

      Thanks,
      Rebecka

      ——————————
      Rebecka McKinney
      IntelliPoint Technologies
      Barboursville WV
      ——————————

    • Shawn Dorward

      Member

      July 7, 2017 at 3:24 PM

      Just a quick response – is this/was this a modified window?

      ——————————
      Shawn Dorward
      Twitter: @ShawnMDorward
      Implementation Consultant
      InterDyn Artis
      ——————————
      ——————————————-

    • Rebecka McKinney

      Member

      July 7, 2017 at 4:11 PM

      Shawn,

      Thank you for pointing that out. I’m not very familiar with this window, but I compared it and it is modified by one of their 3rd parties.

      ——————————
      Rebecka McKinney
      IntelliPoint Technologies
      Barboursville WV
      ——————————
      ——————————————-

    • David Musgrave

      Member

      July 10, 2017 at 1:37 AM

      HiĀ 

      If this was caused by security not pointing to a particular alternate window created by a third party developer.

      Please tell them that for Best Practice they should be checking the security access and confirming that their window is in use before any of their triggers reference fields they have added.

      I have written blog articles and KB articles (while I was at Microsoft) on how to best implement this check.

      If they wish they could also pop up a dialog notifying you that security has not been set to the alternate window, but this would need to have an option to be disabled as there might be a reason that you need access to the original window or a different alternate window.

      Regards

      David

      ——————————
      David Musgrave MVP, GPUG All-Star

      Managing Director
      Winthrop Development Consultants

      Perth, Western Australia

      http://www.winthropdc.com
      ——————————
      ——————————————-

    DSC Communities replied 8 years, 9 months ago 1 Member · 0 Replies
  • 0 Replies

Sorry, there were no replies found.

The discussion ‘Unhandled Script Exception’ is closed to new replies.

Start of Discussion
0 of 0 replies June 2018
Now

Welcome to our new site!

Here you will find a wealth of information created for peopleĀ  that are on a mission to redefine business models with cloud techinologies, AI, automation, low code / no code applications, data, security & more to compete in the Acceleration Economy!