Best Practices for Bulk Data Updates in Cherwell Service Management

Always leave a note - for any record you update, create a journal note against it with a static message identifying the process that ran against it.

Try to make it look friendly to normal users.

This way if something goes wrong, you can search for records containing that note, and even filter on modified time to find the records updated at a specific time, when undoing problematic batch updates.

Created On: 8/29/2020 Created By: Doug
New YouTube Channel For Non-Cherwell Projects!

Follow Us at our new Trebuchet Software - (Non Cherwell) Channel for software development & other technology related videos!


Created On: 8/30/2020 Created By: Doug
How To Migrate Data From A SQLite Database To A FireBird Database

  • Open SQLite Table in Edit Data in SQLite Admin

  • Open Data Menu -> Export Data To Excel

  • Open Excel File

  • In a new column, enter one row as INSERT INTO TABLENAME (Columns) VALUES

  • Add a new row with the following function, where D1 is the INSERT line: =CONCATENATE($D$1, [Columns here with quotes and commas around them], ");")

  • Drag the formula across the remaining rows to generate the remaining insert statements

  • Copy the cells with the insert statements into a query and execute it

Created On: 9/3/2020 Created By: Doug
BugFix for BP Merge Web Client

While testing for compatibility with V10.1.0, we discovered a bug present in our Blueprint Merge web client, in which the output file would sometimes be corrupted by a debugging statement that was being printed on the screen using the .NET Response.Write() method, which was being written to the file when being downloaded by the client as well.
The symptom of this issue is that the resulting BP would have been unable to have been opened when generated from the web client; We have since updated the app to correct this issue and have completed basic testing on the blueprint merge app with version 10.1.0.

Created On: 9/21/2020 Created By: Doug
SQL Server - Recovery Pending Status

A bug we commonly see, especially with personal Cherwell Dev environments / training environments, is an error occuring when connecting to the Cherwell application, that the server is down (3-Tier connections) or that the login failed for the database (2-Tier connections).

The root cause of this typically is discovered to be the database itself being stuck in a 'Recovery Pending' status within SQL Server Management Studio, even though the SQL service is up, the server is up, and there are no other underlying issues.

Most often, simply opening the SQL Server Configuration Manager, and stopping / starting the SQL Service will resolve the problem and bring the database online again.

Created On: 8/26/2020 Created By: Doug