Here's a good example of where Content Library is critical to maintaining knowledge. And notice that it all relies on members coming to the group and sharing. Especially senior members.
Where CC picks up is to compile three pieces of information - none of which may have the complete solution on their own ( HL comes close )
1. Start with Tablacus Script Host (timeout error during button script execution...) which Kevin posts to the Sage Community ( and probably somewhere on HL )
2. He gets a lot of good feedback - but none of it is a complete solution
3. Sage creates a typical KB -Script host timeout error during button script execution - which is "one and done" to plant the flag that there's an issue and they will issue a fix. These KB are seldom updated unless someone at Sage is leaving and on their last month at work they decide to update some KB. In my view this rarely happens. Notice that this is incomplete as it gives no background about why it happens, suggests a potential workaround that others have said doesn't work. Just a very typical basic Sage KB article. Not super helpful in 'the heat of battle' if someone is doing an upgrade and needs an immediate fix.
4. Then this thread starts on the community - Sage 100 2025.1 custom office button script error - which doesn't rehash the history of the issue but includes a key workaround than neither of the options above include.
5. Which presents 90 Minds CC with the ability to capture all of the above into on article in our library - Resolving "Tablacus Script Host" and "Type V Undefined" Timeout Errors in Sage 100
Nobody at the publisher is taking the time to pull together the beginning, middle and ending of these knowledge articles. IMO, it's up to the CC to do so and it's why this committee exists.
------------------------------
Wayne Schulz
wayne@s-consult.comSchulz Consulting
(860) 516-8990
Connecticut
------------------------------