08-05-2024 -  Sage 100 2022.6 users -  I find that Sage has NOT provided a hotfix on the bug which appears like they introduced it in 2022.6 which is on a fully supported 2022 version.

I find that this problem arises in both Sales Order and Purchase Order. Sage says a fix was released in 2023.x and 2024.x latest PU however I have not seen their referenced 2022.6 hotfix other than they push for the customer to sign a pre-release agreement ( also not posted anywhere in the KB ) and it's not entirely clear to me why a customer would have to sign an agreement because Sage appears late in publishing a fix on a supported version.

With the exception of the first product update, I now advise against purely precautionary PU applications pending further observation of how Sage is handling bug fixes introduced by a product update on a supported version. 

IMO there's something going on here at Sage with regards to what versions they are actually supporting ( regardless of their N-x prior policies )

Good luck in finding out the answer.  Have you looped in the Sage 100 product manager in Atlanta?  She showed interest in moving the ball for us but I haven't heard much from/about her lately.

08-05-2024 -  Sage 100 2022.6 users -  I find that Sage has NOT provided a hotfix on the bug which appears like they introduced it in 2022.6 which is on a fully supported 2022 version.

I find that this problem arises in both Sales Order and Purchase Order. Sage says a fix was released in 2023.x and 2024.x latest PU however I have not seen their referenced 2022.6 hotfix other than they push for the customer to sign a pre-release agreement ( also not posted anywhere in the KB ) and it's not entirely clear to me why a customer would have to sign an agreement because Sage appears late in publishing a fix on a supported version.

With the exception of the first product update, I now advise against purely precautionary PU applications pending further observation of how Sage is handling bug fixes introduced by a product update on a supported version. 

IMO there's something going on here at Sage with regards to what versions they are actually supporting ( regardless of their N-x prior policies )

"She showed interest in moving the ball for us "..... Is her name Lucy by any chance?

Good luck in finding out the answer.  Have you looped in the Sage 100 product manager in Atlanta?  She showed interest in moving the ball for us but I haven't heard much from/about her lately.

08-05-2024 -  Sage 100 2022.6 users -  I find that Sage has NOT provided a hotfix on the bug which appears like they introduced it in 2022.6 which is on a fully supported 2022 version.

I find that this problem arises in both Sales Order and Purchase Order. Sage says a fix was released in 2023.x and 2024.x latest PU however I have not seen their referenced 2022.6 hotfix other than they push for the customer to sign a pre-release agreement ( also not posted anywhere in the KB ) and it's not entirely clear to me why a customer would have to sign an agreement because Sage appears late in publishing a fix on a supported version.

With the exception of the first product update, I now advise against purely precautionary PU applications pending further observation of how Sage is handling bug fixes introduced by a product update on a supported version. 

IMO there's something going on here at Sage with regards to what versions they are actually supporting ( regardless of their N-x prior policies )

Nope, she wasn't a ginger.

I could look it up or even revisit the infamous MOTM thread where she was mentioned.  But I don't feel the need or have the energy or even care at this point.

Hey stock market, time to get back on an upward trajectory!  I am ready to get off the merry go round!

"She showed interest in moving the ball for us "..... Is her name Lucy by any chance?

Good luck in finding out the answer.  Have you looped in the Sage 100 product manager in Atlanta?  She showed interest in moving the ball for us but I haven't heard much from/about her lately.

08-05-2024 -  Sage 100 2022.6 users -  I find that Sage has NOT provided a hotfix on the bug which appears like they introduced it in 2022.6 which is on a fully supported 2022 version.

I find that this problem arises in both Sales Order and Purchase Order. Sage says a fix was released in 2023.x and 2024.x latest PU however I have not seen their referenced 2022.6 hotfix other than they push for the customer to sign a pre-release agreement ( also not posted anywhere in the KB ) and it's not entirely clear to me why a customer would have to sign an agreement because Sage appears late in publishing a fix on a supported version.

With the exception of the first product update, I now advise against purely precautionary PU applications pending further observation of how Sage is handling bug fixes introduced by a product update on a supported version. 

IMO there's something going on here at Sage with regards to what versions they are actually supporting ( regardless of their N-x prior policies )

This old issue seems to have resurfaced.  2 clients reporting this today.  

One uses AvaTax and just upgraded to 2024.1.  The other is 2022.6, no AvaTax, and recently received IRD and PR 2.25.

Nope, she wasn't a ginger.

I could look it up or even revisit the infamous MOTM thread where she was mentioned.  But I don't feel the need or have the energy or even care at this point.

Hey stock market, time to get back on an upward trajectory!  I am ready to get off the merry go round!

"She showed interest in moving the ball for us "..... Is her name Lucy by any chance?

Good luck in finding out the answer.  Have you looped in the Sage 100 product manager in Atlanta?  She showed interest in moving the ball for us but I haven't heard much from/about her lately.

08-05-2024 -  Sage 100 2022.6 users -  I find that Sage has NOT provided a hotfix on the bug which appears like they introduced it in 2022.6 which is on a fully supported 2022 version.

I find that this problem arises in both Sales Order and Purchase Order. Sage says a fix was released in 2023.x and 2024.x latest PU however I have not seen their referenced 2022.6 hotfix other than they push for the customer to sign a pre-release agreement ( also not posted anywhere in the KB ) and it's not entirely clear to me why a customer would have to sign an agreement because Sage appears late in publishing a fix on a supported version.

With the exception of the first product update, I now advise against purely precautionary PU applications pending further observation of how Sage is handling bug fixes introduced by a product update on a supported version. 

IMO there's something going on here at Sage with regards to what versions they are actually supporting ( regardless of their N-x prior policies )

"She showed interest in moving the ball for us "..... Is her name Lucy by any chance?

Good luck in finding out the answer.  Have you looped in the Sage 100 product manager in Atlanta?  She showed interest in moving the ball for us but I haven't heard much from/about her lately.

08-05-2024 -  Sage 100 2022.6 users -  I find that Sage has NOT provided a hotfix on the bug which appears like they introduced it in 2022.6 which is on a fully supported 2022 version.

I find that this problem arises in both Sales Order and Purchase Order. Sage says a fix was released in 2023.x and 2024.x latest PU however I have not seen their referenced 2022.6 hotfix other than they push for the customer to sign a pre-release agreement ( also not posted anywhere in the KB ) and it's not entirely clear to me why a customer would have to sign an agreement because Sage appears late in publishing a fix on a supported version.

With the exception of the first product update, I now advise against purely precautionary PU applications pending further observation of how Sage is handling bug fixes introduced by a product update on a supported version. 

IMO there's something going on here at Sage with regards to what versions they are actually supporting ( regardless of their N-x prior policies )