We spent a great deal of time re-developing our Solutions for use in the NetSuite KB feature. We wanted to expose them in the Customer Center, which we did first, and insert the solutions into Cases and we expected that it would work seamlessly since that is native functionality. We tested before going deeply into this but apparently we missed an important use case.
As it happens, a standard Windows path is not supported as in c:\Program Files\app\app because a path written in a Solution and then used in a Case is corrupted. The scope of our need is reflected in the fact that we are in the software business.
According to Support, the underlying HTML support in the Case editor is not the same as the HTML support in other areas of the product. They told us we could REWRITE all of our solutions that contain paths with escape characters and retrain all of our product management, development, documentation and support staff to carefully create new solutions with escape characters. If this sounds either daunting or error-prone...
I applaud that Support tried several conceptual options including exporting all solutions into CSV, doing find/replace and reimporting but we are a dynamic organization that releases code frequently and we keep our solutions up to date. An edit corrupts the import/export fix.
I'm wondering if anyone else has faced this and found a suitable solution? Perhaps we made a bad decision by moving to NetSuite solutions - I would be interested to learn how the backend of SuiteAnswers was built. I'm up for any reasonable ideas that give us an easy way to deliver a KB and insert the articles into Cases without teaching all of our employees about replacing every "\" with, and I quote "ampersand, pound key, number 9, number 2, semi-colon", which inevitably someone will forget or corrupt.
Thanks