Any way to force order of changes applied?

Question

After more testing on my install program, I'm running into an issue where I get an exception due to a duplicate named report in a CMS folder.  This is because in the InfoObjects collection that I am trying to commit in a batch, I am deleting a prior archived version of the report, "then" moving the current version into the archive folder (before creating the new version of the report in the original folder).  If there is no prior version of the report in the archive folder, I do not get this exception.  (I am already changing the name of the archived version to include a date, and I don't really want to just keep making new archived versions ad infinitum.)
I tried to create three InfoObjects collections, one for objects to add, one for objects to change, and one for objects to delete.  I then merged all three into one InfoObjects collection to do my CommitBatch().  I tried merging in the order deleteObjects, changeObjects, addObjects, and the reverse (in case the merged collection ends up "on top of the stack"), and I get the exception either way.
I really, really, really want to do this in all one commit transaction.  Is there any way to tell the SDK what order to attempt to apply the changes in?
I am using the XI R1 version of the SDK.  Will upgrading to XI R2 help (which I need to do anyway; just need to get the CD from my sysadmin)?
Thanks for the help,
Carl

Answer 1

It tuns out that I wasn't deleting the prior archived version the way I thought I was.  (The deleteObjects collection was empty.)  I had thought (based on the reply to a prior thread) that the InfoObjects.Delete() would "mark" the report for deletion upon a commit.  However, it just removed the object from the collection. 
I see the InfoObject.DeleteNow() method, but that sounds like it immediately goes out and removes the object from CMS, outside the scope of a CommitBatch() (which was also stated in that same thread).
Is there a way to delete an object from the CMS as part of the CommitBatch() call?
This might be just an issue with my approach to accomplishing the task.  Since I am potentially doing this specific task any number of times, I am creating a InfoObjects collection by querying the CMS for the objects I am looking to delete.  I then call Delete() for each InfoObject in the collection, and then Merge the collection into deleteObjects.  This Merge() apparently does not move the deleted InfoObjects into the deleteObjects collection.  How would I go about doing this?  Should I collect all of the objects in deleteObjects than, right before committing, delete each object in the collection?  Is there another approach that I have to take?  Here is my code, which is in a method that can be called multiple times:
// delete prior archive version (one per date; keep other-dates history until cleanup)
InfoObjects pa = infostore.Query("select * from CI_INFOOBJECTS where SI_NAME = '"
    + archiveName + "' and SI_KIND = 'CrystalReport' and SI_PARENTID = " + pid.ToString());
if (pa.Count > 0)
{ // zap 'em
  foreach (InfoObject oa in pa) { pa.Delete(oa); }
  deleteObjects.Merge(pa);
If I put a breakpoint on deleteObjects.merge(pa), the value of pa.Count is zero, where it is 1 at the point of the IF statement...
[Referenced thread|Clearification of InfoObject.DeleteNow() method, please;
Thanks for the help,
Carl