Correct reason statements on merges
There needs to be an enhancement to allow you to correct errors in the reasons statements that you give on merges!
Thank you
Comments
-
Unfortunately, that type of reason statement (a change reason) cannot be made editable without breaking the fundamental underpinnings of the open-edit format: either the change log preserves everything, or it's not fully open-edit any more.
I mean, I suppose it could be possible to keep both statements, but it'd get rather confusing, no?
2 -
Agreed. Currently, the only option is to restore the archived record and then merge it again with a new reason statement. That makes for a messy change log. We have the same issue when declaring two records not a match. The only way to add to that statement is to declare them maybe a match and then again declare them not a match with a new reason statement. Those reason statements are important and editing should be an option.
0