Dynamics GP
Dynamics GP
Organizer:
- Organized by
-
-
Unhandled Script exception after year-end update
-
Unhandled Script exception after year-end update
I just did the Year end update for Dynamics GP, along with the Integrity Data update. Now, when going to the employee card screen, there is an error. We can click okay, and get past it. I saw something about disabling the HRM resource, under tools\customize\customization status. That fixes it once, but it re-enables itself, after logging out and back in. Any suggestions?
-
3 Replies
-
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
-
David,
I looked at the Dynamics set, and there is nothing starting with APR. And we don’t have any customization, unless you count Integrity Data on the payroll side. It only does this error on the payroll screens.
Unfortunately, we don’t have GP power tools, either.
Any other thoughts?
Thanks!
-
I would check with Integrity.
APR could be Advanced Pay Roll or something like that.
Also look at this Benefits Presentation
https://www.winthropdc.com/ftp/pub/GPPowerTools_Benefits.ppsx
You can easily fix your GP Power Tools deficiency.
Regards
David
Log in to reply.
