Deleting case types

[david.a.king]

am i safe to remove case types/deleted cases in the database (i.e. through phpmyadmin) or would this cause problems (with orphaned case activities and the like..)?

[demeritcowboy]

As a general rule if you are editing things in the database directly it means something is wrong, and so at that point the answer is always "no it's not safe". Having said that, doing it on a COPY of your database/installation is always safe, and a good way to see what the effects will be.

[anothername]

Still haven't figured this one out, but I am including a screen shot to help folks out visualize my problem!

In the image below, you see the demo site civicase type admin page. Below that, you see the civicase type admin page on my civi install. As you can see there is no 'delete' button and I can't figure out how to make it appear!

[Dave Greenberg]

Based on a quick review of the relevant code (see my prior post), looks like your case type option_value rows have somehow got the is_reserved flag set to 1 (true) OR they are showing up as "in use" based on the query:

Code: [Select]

SELECT DISTINCT( civicrm_case.case_type_id ) FROM civicrm_case
I think you'll need to do some debugging from your end to learn more.

[anothername]

Ok. Thanks Lobo, I will look deeper into it.

[anothername]

Sorry, I mean David! 

[circlebails]

One of our clients also has this problem. In their case they simply wish to delete all case types and cases. Bearing in mind that all deleted does is set is_deleted = '1', is it safe to simply truncate the civicrm_case table?

Ta

[Donald Lobo]

truncating the case table should not be an issue if the user does not care about any of the existing cases

i would use the UI to delete the unneeded case types

lobo