Sage 100

Good day. My first 2018 install has been painful. In part because the client we picked had brought Sage inhouse and put it on a data center with a VPN connection. That being set aside they then came to a screeching hault when AP checks would not post through to AP or JC. Called Sage. I was asked if I put on the hotfixes to 2018.1. They gave me the list and then added there was another that addressed my specific issue. Here is a list of the ones they provided me. Download Sage 100 2018.1 Program Fix LM6005 Download Sage 100 2018.1 Program Fix AP5030 Download Sage 100 2018.1 Program Fix AR6004 Download Sage 100 2018.1 Program Fix JC5031 Download Sage 100 2018.1 Program Fix JC6000 Download Sage 100 2018.1 Program Fix JC6001 Download Sage 100 2018.1 Program Fix JC6003 (""don't install if using WIP accounting - causes other problems"") Download Sage 100 2018.1 Program Fix JC6004 (Bundle of 9 Hotfixes) Download Sage 100 2018.1 Program Fix WO6002.exe

That's all? LOL!

#SageLiason #ThingsWeShouldn'tHaveToOpenASupportCaseToFindOut

Sage should include links to these updates that didn't make the PU right in the 2018.1 download page and label them as ""Also download these fixes which are not in 2018.1"".

Our liason should be called Captain Obvious, because they'll be relaying information that should not need to be said. We discussed there isn't a central place to find them anymore. It does help to search the KB for Program Fix and choose your version. Bit of a work around, though.

#2018pioneer

It's been out for months!!! At this point it should be #2018follower

#ItsAllBetaTillServicePack2 (at least)

BTW, when is the next PU due out??

March 30 - 2018.2

Description of each was added to the list by Sage support and sent later in the day... Sage 100 2018.1 Program Fix LM5029 Error 12 while processing data entry for legacy programs Sage 100 2018.1 Program Fix LM6005 General Ledger Financial Reports do not display on Sage 100 2018.1 Premium Sage 100 2018.1 Program Fix AP5030 AP Check Register hangs during update when integrated with Job Cost Sage 100 2018.1 Program Fix AR6004 A/R Invoice with job referenced is adding $1 Sales Tax Billed to the invoice in Job Billing History Sage 100 2018.1 Program Fix JC5031 Cost Code Format Invalid Sage 100 2018.1 Program Fix JC6000 Error 65 CI_JobNo_VAL.pvc Line 69 occurs in Job Billing Selection or Job Billing Data Entry Sage 100 2018.1 Program Fix JC6001 Unable to enter Actual % Complete Sage 100 2018.1 Program Fix JC6003 A Missing G/L Account was found in Job Type: xxx"" Sage 100 2018.1 Program Fix JC6004 (Bundle of 9 Hotfixes) -PO Material Requisition Register update hangs when there are multiple lines with Job Cost detail. (D108953 KB89623) -Job Billing Data Entry line Bill Amount does not recalculate when Bill Rate is changed for a Time & Material job. (D108937 KB89594) -Unable to enter an Amount on a Credit Memo in Job Cost Distribution Detail when reversing an electronic payment. (D108917 KB89293) -The Transaction Date in Job Posting Entry defaults to System Date instead of the Module Date. (D108901 KB89332) -The Job Billing Data Entry Fixed Bill Totals tab displays the Year-To-Date Cost instead of the Job-To-Date Cost. (D108895 KB89496) -The Receipt of Goods Posting Comment to Job Cost is missing the Vendor Number and Receipt number. (D108880 KB89429) -Error 26 JC_JOBTRANSACTIONDETAILRPT_UI.PVC 107 or Error 26 JC_JOBTRANSDETAILHISTRPT_UI.PVC 109 when selecting ""Save As"" in Job -Transaction Detail Report or in Job Transaction Detail History Report. (D108878 KB89428) -The Calculated Overhead Allocation amounts from Job Posting Entry transactions are incorrect. (D108877 KB89421 Sage 100 2018.1 Program Fix WO6002 The Warehouse Code is Required when adding Material to a Work Order Template

wow... at this point it should be 2018.1.2 at least.

Hopefully some or all of these will be in .2 released in another week or so.

This is why I asked for an RSS feed from the KB (or some sort of subscription) during the MOTM guru session. Knowing there are issues and fixes can save so much time. Reinventing the wheel each case, wasting time troubleshooting only to uncover a known issue later (buried in the KB), instead of having a news feed to know what fixes are available...

I am having an issue visualizing how a feed of all this information would allow me to find this more quickly. In older iterations of the knowledgebase there was a listing of all patches and fixes centrally available. It also indicated what version and update it was to be applied.

I find the Sage KB search to be painful. An RSS feed into a folder would allow Outlook search to pick up key words... and if I am watching blue bars creep across the screen, I could browse new / updated KB article subject lines for anything interesting. I also miss the hotfix listing by version. That was very useful.

The only workaround I've found is poking around the KB while I'm on hold or otherwise tied to a PC but not actively doing work. From observation, during presentations, I get the impression that the portal team is separate from the support team is separate from the development team which is separate from the marketing team which is separate from sales operations. The only time they seem to all work together is when they pose for a selfie on Twitter.

Wouldn't it be nice to have a routine to download all of these at once.

It is critical that we have easy and immediate access to fixes like we used to. PU2 is about to be released, but it is not the end to v2018 fixes, especially to PR, JC, and TC. As a group, what is our most effective way of getting action from Sage on this? Do each and every one of us need to email Linda Cade and/or Jennifer? Other ideas? Also, I was notified yesterday that the fix for the major flaw in JC6003 is being included in PU2.