Allow to remove snapshot when no enforced evaluation was done
R
René de Jong
When testen or changing things at te source. I recently found out after an evaluation that to many accounts will be delete. En new corrected import did not help. After that evaluation the accounts the system will delete and then create the accounts. @#$%^& If could have removed the last two snapshots (I did not enforce any evalutation) I had a lot less problems. And whats the use of evaluation if you can't do anything about it to prevent it from happening.
Niek de Melker
This feature is much needed. Alternatively a dry-run snapshot just to see what would change after a connector update would be just great.
I needed to change the manager criteria, and the only way to see what would happen is to get a new import. an tiny error in calculation resulting in to many updates and a dirty log which cannot be undone.
R
Rick van den Dijssel
René de Jong So your problem here was that you deleted persons by a faulty import/snapshot and you wanted to repair this before evaluating? And the issue here was that because of the deletion of the persons new persons where created which resulted in entitlement revoke for old person and entitlement grant for new person. Is that correct?
R
René de Jong
Rick van den Dijssel: I did a faulty import/snapshot. There where no records removed or added, the contract dates where wrong. So a the import there was no warning. I did an evaluation first, not an enforcement, to see what would happen (I had this feeling there was something wrong). The evaluation said it would remove lots of accounts. This was bad. So corrected the source query and did an import again. This time again no removing or adding of records, but correct contracts. I did an evaluation (no enforcing) first to see what would happen now. And I see that it would first remove the accounts and then create the same account again.
I did evaluation no enforcement so in production nothing happened yet. So if I could have remove the last 2 snapshots and then import/snapshot again, the result would have been what should have happened. But you can't. So to me there no other option, than to break the powershell code to skip things and to make the problem less worse and do the enforcement and contact the users.