Reply To: Unhandled Script exception after year-end update

  • David Musgrave MVP, GPUG All Star, Community Legend

    Member
    December 11, 2024 at 6:47 pm
    Up
    0
    Down
    ::

    You have a customization installed which will also need to be updated for the Year End update.

    The trigger that is failing starts with APR, look at your installed products in the Dynamics.set and identify which product is named or written by APR.

    If you have GP Power Tools, you can use the Resource Information window in Procedure mode and enter the trigger script’s name and it will identify which product the script is from.

    Once you know the product, please contact the developer for more information.

    One other possibility is that there is an alternate version of that window that is not enabled and so the URL field is missing. Best coding practice should prevent an illegal address error if an alternate window is not opened by security, either aborting the code or displaying a warning to change security settings. But maybe the developer has not followed best practices.

    Regards

    David

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!