Bug #4662
closedroll revision vs. new object ID
0%
Description
My current auth namespace is 3371. I have a file with an old auth namespace of 1347. If I open the XML file, view LSID, and roll revision, then generate a report and attempt to save the KAR, I get an error saying it can't be saved because the report is NULL. If I open the XML file, view LSID, new object ID, then generate a report, I can save the KAR as expected. If I open the XML file, delete an actor then undo, then generate a report, I can save the KAR as expected.
Thing seem to work fine if the auth namespace is the same.
What's the difference between roll revision and new object ID, why do we need 2, and why doesn't roll revision seem to work in this case.
Updated by Aaron Aaron almost 15 years ago
This sounds like a WRP specific issue. Reassigning to Ben for the meantime.
Oliver the short answer to having Object ID and revision is that having both provides a finer level of categorization and increases the number of unique ID's that you can generate in one namespace.
Updated by Oliver Soong almost 15 years ago
At 23040, the revision buttons no longer seem to exist, so I guess these exact symptoms will no longer occur. I'm not sure if the underlying problem has been resolved, but it may have been fixed with 4682.