Bulk-inactivating lists

Is there any way to inactivate multiple lists at once? we have thousands of old lists that haven't been generated in a decade or more, and while I don't think it will cause too many disruptions if I mass delete them, I'm wondering if mass inactivating is an option, without having to go into each list's properties and inactivate them one at a time. 

Parents
  • Okay, I've packaged up my code and I'll send it to those of you who have expressed interest. If anyone else wants it, just DM me.

    Some things to keep in mind with deleting lists: if the list has contents (customer #s) or relationship options you can't just delete the list from the backend; you would also need to delete those contents and/or relationship options before deleting the list. And keep in mind that other dependencies exist throughout the system that might make deleting those lists less than ideal, e.g. due to dependent appeals, or a headache/something you want to avoid, e.g. foreign key references from acknowledgements, etc.

    One other thing to keep in mind: static lists might not have what we would consider an accurate last_used_dt if they're being used as a report parameter. Don't quote me on this one since I can no longer prove it because I took steps to remedy this in our instances, but just something else to keep in mind.

    On the surface this seems like a pretty straightforward task but it's slightly complex. Depending on your needs, it might be easiest and cleanest in the long run to delete the old lists  manually in the front end or check out my utility. 

    Happy list cleaning!

Reply
  • Okay, I've packaged up my code and I'll send it to those of you who have expressed interest. If anyone else wants it, just DM me.

    Some things to keep in mind with deleting lists: if the list has contents (customer #s) or relationship options you can't just delete the list from the backend; you would also need to delete those contents and/or relationship options before deleting the list. And keep in mind that other dependencies exist throughout the system that might make deleting those lists less than ideal, e.g. due to dependent appeals, or a headache/something you want to avoid, e.g. foreign key references from acknowledgements, etc.

    One other thing to keep in mind: static lists might not have what we would consider an accurate last_used_dt if they're being used as a report parameter. Don't quote me on this one since I can no longer prove it because I took steps to remedy this in our instances, but just something else to keep in mind.

    On the surface this seems like a pretty straightforward task but it's slightly complex. Depending on your needs, it might be easiest and cleanest in the long run to delete the old lists  manually in the front end or check out my utility. 

    Happy list cleaning!

Children
No Data