Community
Vault Forum
Welcome to Autodesk’s Vault Forums. Share your knowledge, ask questions, and explore popular Vault topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Autodesk vault API 2012 - check-in file bug ?

2 REPLIES 2
SOLVED
Reply
Message 1 of 3
Anonymous
570 Views, 2 Replies

Autodesk vault API 2012 - check-in file bug ?

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:

 

 

VersionFile name
1sample1.txt
2sample2.txt

 

But unfortunately, using Vault 2012 and making the same operation usign API the result is:

 

 

VersionFile name
1sample2.txt
2sample2.txt

 

Is this purposeful behavior or maybe a bug ? Can anobody tell me? Smiley Indifferent

 

 

2 REPLIES 2
Message 2 of 3
Redmond.D
in reply to: Anonymous

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.



Doug Redmond
Software Engineer
Autodesk, Inc.

Message 3 of 3
Anonymous
in reply to: Redmond.D

Hi Doug,

 

Thanks for the answer! Smiley Happy

 

Regards,

Mike

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report