Cannot update resource name without incrementing version

Follow

Martin

• 26 November 2016 21:04

Currently updating a Resource name forces a version increment.

This should be at the discretion of the user not enforced.

E.g. simple edits to standardise naming conventions should not create a version increment.

 

8

• 

  Michelle Barry

  • 29 November 2016 23:40

  I agree. I find this very frustrating. Sometimes it's easier to delete the file and add it again to get the number right in some cases which defeats the purpose.

  1

  Comment actions Permalink
• 

  Mark Costello

  • 29 November 2016 23:51

  I agree. We uploaded some wrong files recently and the version number in aXcelerate no longer matches the version number on the documents. It was tempting to delete the whole thing and start again but we would then lose the previous versions of the file.

  1

  Comment actions Permalink

Please sign in to leave a comment.