Sage 100

Hey @Brett Zimmerman - did you ever get this? I'll be happy to call Sage and tell them I need it. I'm assuming I will soon, even though I haven't heard of any of my 2025 clients having this problem, yet. 

I didn't.  Client is fine with workaround for now.

Hey @Brett Zimmerman - did you ever get this? I'll be happy to call Sage and tell them I need it. I'm assuming I will soon, even though I haven't heard of any of my 2025 clients having this problem, yet. 

ELI 5 why clients/customers tell me they are receiving 10% annual price increases yet the level of service seems to decrease annually. Don't give me the line that Sage wants to be sure that the patch works thats why they are making everyone ask for it and the VAR signs a pre-release waiver. I was born at night - but not last night.

Thanks @Brett Zimmerman, FWIW the patch works on my test system.

@Wayne Schulz, I tried to beat Brett to the punch by duplicating the issue on a recent upgrade and creating a ticket with Sage. I didn't need to sign the Pre-Release Agreement. I was told that the client needed to sign it. In my case this client only creates new Ship To Codes in Customer Maintenance, so they weren't interested in jumping through Sage's hoops.

ELI 5 why clients/customers tell me they are receiving 10% annual price increases yet the level of service seems to decrease annually. Don't give me the line that Sage wants to be sure that the patch works thats why they are making everyone ask for it and the VAR signs a pre-release waiver. I was born at night - but not last night.

How do I as a pro-active VAR who is eager to delight our mutual customer ensure that when I setup a Sage 100 2025 initial upgrade that it's fully patched?

I know that one way is to install the latest PU.

What if we are in between PU releases and the next PU isn't due for several months? 

The prior way to solve this would be to download individual hot fixes which generally were linked off the main download page for the Sage 100 release. Now, there isn't a way to download a version of Sage 100 2025 that is fully patched - because hot fixes aren't listed (publicly).

And before anyone says ( or thinks ) - "Wayne you cranky moron" - the present day status of Sage 100 is that most of the small mom and pop customers are gone.

They were chased away by price increases. Now what you have left are the larger sites typically wholesale distribution. These sites also have from 1 to 5 enhancements.  In my opinion for these sites it is important to get a fully patched system in place before installing upgrades with enhancements because the Sage 100 ecosystem has no standards or rules for making subsequent upgrade straightforward. Which results in it not being uncommon for end users to stay on a release for 5+ years. 

Yea, I know some of you probably threw a random patch on once about nine months ago and nothing happened with the integrations. Congrats. I just don't think that's a best practice if the patches existed at the time. you staged Sage 100. At least not a best practice I want to try out when my customer has 25 people doing heads down shipping in the warehouse and can't afford to be down. Ever run into a sudden bug  on a site with 1 to 5 enhancements? Did you enjoy playing "prove the problem is mine" with the ISVs? I sure don't enjoy that. Customers don't either.

TLDR: The big flaw in Sage 100 is there is presently no way to ensure that you've installed a fully patched version of Sage 100 because hot-fixes are now hidden, frequently not listed in the DL KB, and only available upon request. 

PS - and despite Sage having an N-2 support policy the product updates are often limited to N-1 which really cooks the customer on an N-2 system...

Thanks @Brett Zimmerman, FWIW the patch works on my test system.

@Wayne Schulz, I tried to beat Brett to the punch by duplicating the issue on a recent upgrade and creating a ticket with Sage. I didn't need to sign the Pre-Release Agreement. I was told that the client needed to sign it. In my case this client only creates new Ship To Codes in Customer Maintenance, so they weren't interested in jumping through Sage's hoops.

ELI 5 why clients/customers tell me they are receiving 10% annual price increases yet the level of service seems to decrease annually. Don't give me the line that Sage wants to be sure that the patch works thats why they are making everyone ask for it and the VAR signs a pre-release waiver. I was born at night - but not last night.

How do I as a pro-active VAR who is eager to delight our mutual customer ensure that when I setup a Sage 100 2025 initial upgrade that it's fully patched?

I know that one way is to install the latest PU.

What if we are in between PU releases and the next PU isn't due for several months? 

The prior way to solve this would be to download individual hot fixes which generally were linked off the main download page for the Sage 100 release. Now, there isn't a way to download a version of Sage 100 2025 that is fully patched - because hot fixes aren't listed (publicly).

And before anyone says ( or thinks ) - "Wayne you cranky moron" - the present day status of Sage 100 is that most of the small mom and pop customers are gone.

They were chased away by price increases. Now what you have left are the larger sites typically wholesale distribution. These sites also have from 1 to 5 enhancements.  In my opinion for these sites it is important to get a fully patched system in place before installing upgrades with enhancements because the Sage 100 ecosystem has no standards or rules for making subsequent upgrade straightforward. Which results in it not being uncommon for end users to stay on a release for 5+ years. 

Yea, I know some of you probably threw a random patch on once about nine months ago and nothing happened with the integrations. Congrats. I just don't think that's a best practice if the patches existed at the time. you staged Sage 100. At least not a best practice I want to try out when my customer has 25 people doing heads down shipping in the warehouse and can't afford to be down. Ever run into a sudden bug  on a site with 1 to 5 enhancements? Did you enjoy playing "prove the problem is mine" with the ISVs? I sure don't enjoy that. Customers don't either.

TLDR: The big flaw in Sage 100 is there is presently no way to ensure that you've installed a fully patched version of Sage 100 because hot-fixes are now hidden, frequently not listed in the DL KB, and only available upon request. 

PS - and despite Sage having an N-2 support policy the product updates are often limited to N-1 which really cooks the customer on an N-2 system...

Thanks @Brett Zimmerman, FWIW the patch works on my test system.

@Wayne Schulz, I tried to beat Brett to the punch by duplicating the issue on a recent upgrade and creating a ticket with Sage. I didn't need to sign the Pre-Release Agreement. I was told that the client needed to sign it. In my case this client only creates new Ship To Codes in Customer Maintenance, so they weren't interested in jumping through Sage's hoops.

ELI 5 why clients/customers tell me they are receiving 10% annual price increases yet the level of service seems to decrease annually. Don't give me the line that Sage wants to be sure that the patch works thats why they are making everyone ask for it and the VAR signs a pre-release waiver. I was born at night - but not last night.