Sage 100

Running into these error (200 v4.5 PU 4) while trying to run the Lookup Conversion Utility (error 42) and trying to create a custom lookup in SO entry (Error 43). I suspect they are related. Client migrated from v4.3 a couple months back. Trying to put to rest some outstanding issues. Thoughts.

Found this: http://infosource.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=526905

Do they have a lot of custom lookups or could they recreate them?

Well, if their option to eliminate these errors is to start all over, they don't have much choice...........

This has to do with having 30+ UDFs in SO Header. You won't be able to do any custom lookups. We had to defer an upgrade until it's fixed in v5.0.

Wow, I thought I was the only one washing my hair on Saturday night....... Thanks...

Did they indicate why they are being lazy in fixing it for 4.5

This client ""only"" has 47 UDF's in SO header....

Why do they have so many UDF's???

Most of them are for their Radio Beacon warehouse management program. Unfortunately, not many are used.

@JeffSchwenk - best chance to get Sage off their butts about this for 4.5 is to post in the Sage 100 Users & Consultants group on Linkedin. Then @MichaelNottoli should add his comment about a customer wasting a year's maintenance because they have to wait for the bug to be fixed.

@JeffSchwenk Sadly, I logged a case with Sage 4-5 months ago regarding this issue. Was told that it was due to too many UDF's. I replied that customization was supposed to be a MAS 90 strength. Was told I'd hear back from a product manager. Never happened. If you haven't started a post on Linkedin, I can. If you have, post a link so I can add my .02.

Thanks. And note that it isn't schedule for a fix release until 2013 PU 1.

Was this working OK in 4.4? Wasn't a problem in v4.3 as the client had 45 UDF's in the SO header. I can't determine the v4.4 as they skipped over that version.

Here is the linked in post. Have at it. Your support is appreciated. http://www.linkedin.com/groupItem?view=&gid=106271&type=member&item=182094176

This was working in 4.4, as that's what I upgraded my client from. Added my .02 to your Linkedin post and encourage others to chime in as well.

I think if we hit them on customer expectations and that Sage is justifying the price increases on R & D and keeping bug fixes current, we may get some movement on the issue. They broke it in V4.5, they should FIX it in v4.5. We need more posters to pile on this. http://www.linkedin.com/groupItem?view=&gid=106271&type=member&item=182094176

@JeffSchwenk did you contact Jeff Constanzer? Let us know what he says.

Still need people to post their two cents. He is hiding behind corporate speak. I will reply publicly to him first. Then maybe call him this PM.

I don't care that it will be available in 4-6 weeks with PU 1 - that's not acceptable.

I'm getting very tempted to start using ""#fucus"" in public...

Now don't go stealing my thunder...... We really need more posters on this to demonstrate that it is NOT just a couple rotten apples bitching. C'mon everyone......

Wow! Great responses from the Linked In community! If Jeffrey Konstanzer really follows up with a fix for v4.5 that'll be a real coup. @JeffSchwenk great post!

It makes no sense why the plus 40 UDF worked in Version 4.3 and Version 4.5. Both Versions as we know the SO MOdule is Business Framework, so what changed to module in Version 4.5, or for that matter any module. Version 4.5 was virtually no changes other than some new functionality. This should not be broken and I agree should be fixed in a SU hopefully soon.

I meant to say Version 4.3 and Version 4.4, sorry for the confusion.

@JeffSchwenk - Have you actually been able to find the Sage management contact info on Atlas? I want to send Jeffrey the email trial on the September screwup that I mentioned, but I cannot find the contact info....

In the ALE, the counter for fields only has 3 characters, so it can only handle 999 fields. V4.5 added a bunch of new tables to the SO_Header lookup, so baseline it's at ~ 970 fields. 30+ UDFs puts it past 999 and causes the error.

Not sure why I waste my time writing responses to Kanstanzer................

Nice response @JeffSchwenk!!

Does this address our concerns? http://www.linkedin.com/groupItem?view=&gid=106271&type=member&item=182094176&commentID=103034365&goback=%2Enmp_*1_*1_*1_*1_*1_*1_*1_*1_*1&report%2Esuccess=8ULbKyXO6NDvmoK7o030UNOYGZKrvdhBhypZ_w8EpQrrQI-BBjkmxwkEOwBjLE28YyDIxcyEO7_TA_giuRN#commentID_103034365

It's probably the best we can get at this point given the poor decisions that lead to it: (1) The 640kb/y2k style decisions made when ALE was first implemented (""No one will ever need more than 999 fields here."" Are software publishers EVER going to learn this lesson?) (2) It shows that Sage knew they had a problem in 4.5 SO (or should have, anyway) and chose to ignore it and hope no one noticed or complained too loudly.

I think they knew they were going to have a problem much earlier than that. I would bet someone raised the issue by at LEAST v4.3. I think someone should call them out on it!!!!!!

I think they're justifying it by saying it affects too few customers to warrant additional time and money, just like many of the enhancements we/customers ask for.

Oh, the infamous one off scenario that Wayne is famous for. In their defense (ouch), my number #2 UDF power user only has 15 in their SO Header.....

Pay me now or pay me later................ When someone else has to deal with the problem!!!

Hotfix was posted Friday night under the product update tab of Atlas. Still no PU 5. I guess PU 5 will have the YE updates. For those not in the mood to fight Atlas today, here is the patch with explanation for v4.5. I've installed at the client. It no longer blows the error. However, it does appear to blow away ALE customizations.

Wow, lots of good comments on the linkedIn post. Perhaps for Christmas Santa Sage will actually act on our wish list. Wishful thinking I know, but keep on posting....

PU5 is currently scheduled to release on December 10th - per Sage Developer support.

Latest comment on linkedin: Champ Systems, Inc has a fix available for this today. Contact Calvin or Norm 916-424-4066 Our fix increases the limit to 9999 Posted by Norm Champ I don't have any experience with Champ Systems. Might this be worth looking into?

Interesting. I wonder how they did it so quickly but it took Sage months (or more than a year) to get it done. I downloaded the hotfix last weekend and installed at client. They have been using it for three days. Feedback today was that it was working like a ""champ""....

@JeffSchwenk how does the hotfix affect the ability to see UDFs in the Advanced Lookup Engine?

I wonder how Sage ""fixed it"" in 4.5 when the real fix is scheduled for 2014.

@MichaelNottoli - No clue what the exact fix was. Issue for the client was the error message when trying to create a custom lookup. Client is able to create custom lookups now. They are happy. So am I until the next Sage snafu. Nirvana may be short lived!!

My understanding was that the hot fix and the change in version 2013 suppresses the error message when there are more than 999 fields, but only 999 fields will be available for the lookup to use. In version 2014 the 999 limit will actually be increased so that all the fields are available for use in the lookup.