ProcessCommandBranch for a single file
Posted: Mon Dec 28, 2009 5:52 pm
Attempting to use API to create a new major version for our product - which requires 3000 operations, mostly copy-branches and shares as appropriate.
When we attempt
ServerOperations.ProcessCommandBranch(fromItem, newpath)
Where:
a) fromItem is the full vault item path (not working folder path)
b) newPath is the target vault folder path (OR full target vault item spec -- e tried it both ways)
c) it has been determed we need a copy-branch (its a .sln file in this case...don't want to share that across versions...)
d) the item does not yet exist in the target location
we get a VaultClientIntegrationLib.UsageException : {"$/sourc-item-exists, but this command may not be used to branch individual files."}
How can this be accomplished using the API?
When we attempt
ServerOperations.ProcessCommandBranch(fromItem, newpath)
Where:
a) fromItem is the full vault item path (not working folder path)
b) newPath is the target vault folder path (OR full target vault item spec -- e tried it both ways)
c) it has been determed we need a copy-branch (its a .sln file in this case...don't want to share that across versions...)
d) the item does not yet exist in the target location
we get a VaultClientIntegrationLib.UsageException : {"$/sourc-item-exists, but this command may not be used to branch individual files."}
How can this be accomplished using the API?