Inventor-Vault (Copy Design) iLogic ThisDoc.Document.FileSaveCounter bug

[ReneRepina]

Hello,

I came across as it seems Inventor-Vault (Copy Design) iLogic ThisDoc.Document.FileSaveCounter bug.

I am using Inventor 2020.3.4 and Vault 2020.3.3.

How to simulate the problem:

1. Use this iLogic code to get the value of how many times was the file saved. First on original file. (In my example it was 5.)
   

   MsgBox(ThisDoc.Document.FileSaveCounter)

2. Use Vault Copy Design function to copy this file.
3. Again use above iLogic code to get the value of how many times was the copied file saved.
4. You get the same value, eventhough you did not save it yet or at least it should be different value. It does not reset the value. (In my example it was 5.)

Bug?

If you use VDS to copy the file inside Inventor, it changes counter to lower number. (In my example it was 2.)

Best regards,

Rene Repina

[Xun.Zhang]

In your sample, it seems that the target file does not request a save and copy/paste from windows API rather than inside of Inventeor. 

To prove this, please share a file and the copy designed file here and we can take a look.

Thanks!

[ReneRepina]

@Xun.Zhang 

Sure. I attached them in attachments.

VLT-047622.ipt - original file

VLT-047624.ipt - copy-designed file

[Xun.Zhang]

By checking the files, thre are exactly the same, no save as or save copy as happen inside of Inventor.

So the version keeps the same as original one.

Hope it helps!

[ReneRepina]

@Xun.Zhang 

FileSaveCounter is still not logical. Why it does not reset?

For example if I copy-design the model (as in example), FileSaveCounter stays the same (meaning NEW part was saved 8 times, which is not true, because it is a new part). If I copy-design it inside Inventor (save as, ...), FileSaveCounter resets. Why? Both of examples are the same, only difference is where you copy it.

[Xun.Zhang]

Hello @ReneRepina,

Think in this way, in most of case, the part is just renamed during copy design process, most of part are not necessary to open and resave. so after rename it, the file is exactly the same file with a different name. You can do it in your local as well. In windows explorer, copy a file and paste, rename the newly pasted file, they are exactly the same.

But if open that file, save as or save copy as, they are different file ID, so the version will reset to 1 at the beginning.

For example, assembly A1 has a part1 inside. Copy design, the part1 now become part1 - copy, but it is just a copy file operation since nothing has to be done. However, for A1 - Copy, it has to change the reference to Part1 - Copy, so it calls API to modify the file reference inside by opening A1 and save A1 as A1-Copy, thus, A1 - Copy will be set to v1 during the process.

[ReneRepina]

@Xun.Zhang 

I understand what are you trying to say. Copy and Save As are different functions, but do the same thing - creating new instance of the same file. One resets the counter, but other does not (+ other things).

I tried locally with the example files. They stay the same, BUT creation date is changed (which is logical, because it is a new file and new should should have their own counter).

I tried what you wrote. I inserted the part into assembly. Checked the counter. Then I tried 2 things. First was copy design both of them and check counters on new files (both, assembly and part had the same counter as the files copied from). I also tried on that same assembly to change the reference of the part. When I saved the assembly with different part, counter just went from that number + 1. So on none of the files counter was reseted.

For me it is strange that counter reseted. If you can understand me, my logic is like this. I create a part, change it 100x times (dimensions, color, material, shape, ...). Then I come to the final version, which has "FileSaveCounter" of 100. Then coworker comes and copy-design it and change it for their function, let say 10x times. Because coworker copy-design it, it should have a counter of 10x, not 110x, like in my situation.

Let say we copy from only one model. Every next model will never have the lesser number of "FileSaveCounter" comparing to previous model. This is strange logic behind it.

For me, every new part (copied, saved as, ...), should have "FileSaveCounter" saved to 0 (or 1 when saved), because this is the 1st version of that new model.