Hi @Nani18
for this purposes use Update jobs:
It is no-code method with rollback option.
- Select a table,
- give it conditions and you will see how many records are matching that condition,
- select what fields shall be updated - make it Active to FALSE.
- it is better to deactivate as that user can be referenced in any of the records (Inc, KB article, etc).
I don't recommend update such a big amount of records at once, do it in bulks (by thousands and executed one after another) in early mornings or late night hours.
I recommend to uncheck these two options:
- Auto updating system fields
- if true: it will update the "updated on" and "updated by" fields which can hold some useful detail,
- applied on all the updated record with the time of the execution and updated by "system",
- if false: it will make the job but not update these two fields - recommended.
- Run BR and engines
- an equivalent of setWorkflow(false);
- unless necessary I also recommend to uncheck this.
- As user deactivation can lead to trigger notification or any other recursive actions.
Alternatively, you can do it via fix script, it has the rollback option also. Or a scheduled job.
Let me know what do you think about the Update jobs.
