Sage 100

Atlas / Sage Portal Knowledgebase (it doesn't appear this has already been discussed, but sorry if I missed it) So I pull up a write-up in the old SSO Knowledgebase (Res ID 526263) and upon clicking the Engineering Status link, it says the issue has been fixed in PU3 for 4.40. But when I pull up the same write-up in Atlas, there's no mention of the fix (nor does it display the Res ID). Is there something I'm missing?

What are you missing -- a good and useful knowledgebase on the new portal?

At least you found the write-up.

Sage was missing the budget to fully transfer all the data

The data will be transferred over the next few months. They figured it was cheaper to hire summer interns to re-key it all than to pay expensive consultants to migrate it. Can't blame them there.

You sound llke some customers @PeterWolf. ""That's okay. We can enter it."" Then, when they realize how long it will take, they come back and ask about us importing it again, even though we laid that option out at the beginning. Anything to save a buck. Oh wait! Isn't Sage already not spending much on R&D AND taking away margins to save some dough?

Ahh... yes - I should have been more clear. I was speaking sarcastically as a customer. Sage is not going to have that data available ever.

The data IS available on the old SSO - Sage should never, ever, ever lock that up or close it down. It's like the customers who keep the prior system on a backup box for history purposes only.

I had a link to the TRSG on the old SSO saved, and tried to access it yesterday to look up file structures for version 4.05. Guess what? I was redirected to a page giving me the option to open either the Partner Portal or the Customer Portal. So I tried the Partner Portal. Opened the Support page. No TRSG - no mention of older file structures anywhere. So, knowing I had trouble with registration keys, I tried to log into the old SSO to print a list of my customers' old (original) account ID's. Again, I was redirected. The old numbers are not on the new partner portal, so if I have to reinstall for a client, I either have to hope I can access the old system or ask Sage for new keys that correspond to the new account ID? This is progress?

In case you didn't see the response I got from support on some questions I sent them - these relate to the topic: 3.When we call regarding a program issue that is/is not written up is that chargeable? When the issue is known, and is available for reference in the Knowledgebase (which you can access through the Partner Portal), the case is chargeable. When the issue is known but not yet available for reference in the Knowledgebase, then we can no-charge the case. 4.When we call and the article has just not made it over to the new portal or has not been published is that chargeable? If the issue is a Defect, see #3. If the issue is not a defect, the case might be chargeable. As each case/issue is unique, this determination can be made at time of case.

They really should read the page from the Amazon support book that Rose (er Mark) posted on earlier. This is what happens when the support department becomes a profit center. Egad!!!!!! Maybe the Engineering department should be responsible for the support costs. Design it right the first time and give them the incentive to minimize support costs.

Here is what Sage is more likely to model itself on - the crap I went through on my daughter's HP laptop had screen problems. http://friendlysystems.com/blog/2010/08/hp-more-than-the-ceo-needs-to-go/

Hmmmm, not quite the same as my daughters experience with her Lenovo notebook that she received for college. In the three years that she had on site warranty, she went though 4 hard drives, one keyboard, a touchpad, one motherboard and one screen. All were replaced (on site) with no questions asked. The only thing that wasn't replaced was the case. During her senior year, she purchased an Apple laptop. Though I no longer took support calls from her, I didn't need to. However, near the end of her three year warranty, she took it in for a troublesome hard drive. While it was still covered, they refused to swap it out because their moisture detector indicated that it had gotten wet. Sorry, can't help you...................

Fyi, the Res ID for a write-up in the new Sage Portal can be found toward the end of the URL. Also looks like the Res ID defaults as the filename when printing the write-up to .pdf.