Hi,
In Vault 2011, when we invoke:
File CheckinFile (
Long fileMasterId,
String comment,
Boolean keepCheckedOut,
DateTime lastWrite,
Long [] dependFileIds,
String [] dependSources,
Long [] attachFileIds,
String [] attachSources,
BOM bom,
Boolean copyBom,
String newFileName,
FileClassification fileClassification,
Boolean hidden,
System.Byte [] fileContents
);
and specify newFileName different (than actually checked out file has), in file history we can see that:
Version | File name |
1 | sample1.txt |
2 | sample2.txt |
But unfortunately, using Vault 2012 and making the same operation usign API the result is:
Version | File name |
1 | sample2.txt |
2 | sample2.txt |
Is this purposeful behavior or maybe a bug ? Can anobody tell me?
Solved! Go to Solution.
Solved by Redmond.D. Go to Solution.
This is not a bug. Starting in Vault 2012 renaming a file will now retroactively rename all versions of the file. This behavior is in all of the Vault clients and the API as well. There is a new property called "File Name (Historical)" that contains the original file name. At the API level, File.VerName has the original file name.