Sage 100

Had a client report that my Customizer event scripts I created for them weren't working anymore after they upgraded from 4.40 pre-PU7 with JobOps to PU7 with JobOps R3 Nanook. I took a look and specifically scripts for PO Entry and PO ROG Entry do not work (all events). The MAS scripting object is not even being called, as if it's being overridden. All other event scripts outside these 2 places (AP, AR, etc incl where JobOps is present) work just fine. As a test, if I rename the Links folder, the PO and ROG scripts work fine. Has this happened to anyone else with client using JobOps R3 Nanook? I'm pretty sure they don't have any of the fixes that @JaneScanlan has posted.

I am having a similar issue at a JobOps client that the scripts aren't working.in Sales Order. My client is on 4.40 PU6 R2 Nanook. I haven't spend much time troubleshooting yet.

Just an update -- we found that if you try to have more than one script at a time, it won't work. Having just one script only, seems to work. Our testing so far has been on the Service Ticket and Work Ticket entities.

Any updates on this? We've got an issue in S/O Entry where we have the same script being fired on a few different fields but the script only fires on one of our fields not all of them. After we've compile any changes if we look at the MAS compiled script only the one field has a subroutine built the other fields aren't being written to the file. I manually added them for the missing fields but apparently MAS doesn't know to call them.

Slight correction to last post. It's PO Entry for us as well.

FYI: After talking with Chris at Synergistics they found a problem with a change they made to MAS90\LINKS\CM_SCRIPTCOMPILE_UI.PVC . If you rename that file and recompile your script you'll find they fire when they're supposed to.

I can confirm that this resolved my problem too. Thank you Brett .

Thank you very much @BrettLyder much appreciated. I didn't have any updates on this myself. But about your script that doesn't run the subroutine, this is one of the limitations of event scripting. You may not know it, but when your script is executed by MAS it is actually being called as a subroutine routine already from the master script for the business object. Because you are already in a sub, you cannot call another sub or call a function or similar. As an example, let's say you have a PreTotals script for S/O Entry. When you compile it, it gets inserted into the master script which is SO_SalesOrder_bus.vbs (or SO_SalesOrderDetail_bus.vbs if you're executing from the Lines). If you take a look there you will see your PreTotals script pasted in there with the heading of Sub PreTotals500() - where the 500 represents the priority level. Good or bad, the reason for the master / child script concept to begin with is to support different priority levels.

You are welcome, Jim. BTW Chris wasn't sure why they'd changed that file in the first place. He is going to investigate and respond with a proper solution/fix. I'll post that info once I get it.

Thanks @AlnoorCassim I may have worded my post badly. I did know that scripts are added to the master script as subroutines. What I meant was, I checked the MASTER script and noticed that only one of my scripts had been inserted as subroutines instead of all the PO detail scripts that I was trying to use. This one had us going for awhile. We suspected JobOps but they didn't even believe it could be them. But to Chris' credit he was more than willing to dig into it for us.

Ah I see. That was great detective work on your part! And it corroborates @DawnAnastasi findings. And great to find someone like Chris ..

Just got this fix from Chris at JobOps. If you need it before the next fix release here you go: 1) If you renamed that file in the link directory, make sure you rename it back it should be named ""CM_ScriptCompile_UI.pvc"" (need not be case specific). 2) Put the attached, repaired program in your MAS90\CM directory, overwriting your existing.

@BrettLyder Do we need to compile again after we add this program back,

Chris didn't say and I didn't think to ask. My guess would be that it's not necessary. But, if it's not a huge inconvenience for you i'd probably just go ahead and just compile them again.

The JobOps script was my only script but I will recompile tonight just in case.