Sage 100

From @PhilMcIntosh who originally posted issue under Job Ops when in fact, it is a Sage issue. Updated a customer to R3 Astro/4.40.08 and now have the following weirdness in SO entry. When a user tries to change the customer on an existing order, getting error 88 so_commonentry.pvc line 1662. This customer also has CRM, and on orders that are tied to an opportunity, most users have the customer field grayed out, but one user has it live - she still gets the error when changing a customer. I am thinking the grayed out is the normal behavior and it being open is not, but can anyone confirm that?

More from @PhilMcIntosh OK, this was not a JobOps issue, but Sage imitating what we finally got JobOps to quit doing in fixing mistakes but leaving the file names the same. The SO-4084T I downloaded on 3/10 actually contained the 4.50 version of SO_CommonEntry.pvc dated 1/17/12, which does have a line 1662 which refers to new pricing features not in 4.4. Somewhere between 3/10 and today, Sage fixed that problem and it now has the 4.4 program dated 2/22, but it is not mentioned anywhere.

From @JeffSchwenk I just installed PU 8 at a client yesterday (along with misc subsequent patches) and have encountered this exact error. Is this patch dated 2/22 on the OLD BOSS web site? I have spent 15 minutes looking for the patches on ATLAS and I'll be danged if I can locate ANY of them. Phil, do you have the ""good"" patch for v4.4, PU8 that you could post here?

I believe you cannot change the customer on an order generated from CRM. (You also cannot copy them we discovered.)

@Jeffschwenk I am out of the office now but the old portal had the correct file in the so4084t download today. I could not find patches on Atlas either.

Here is a link to the patches on the new portal. I stumbled upon it by accident. https://partners.sagenorthamerica.com/irj/go/km/docs/sageKM/Sage%20MAS%2090%20and%20200/Ungated%20Customers/Browsable/Support%20Home%20Page%20for%20Sage%20100%20ERP.html

@ThereseLogeais - The problem that Phil and I both experienced was due to a bad Sage patch - SO-4084T. The correct one for v4.4.8 is posted now.

Sure wish SC would hurry up with the functionality to move posts between categories........