topic Re: visualization file issues in Vault Forum

visualization file issues

Anonymous — Fri, 16 Jun 2017 12:55:39 GMT

Recently we have came across a problem while renaming a file the visualization file is broken from the part/assembly file. Autodesk has supplied us with a fix once broken but the core problem has not been fixed. It would be nice if this error would be corrected.

Thanks

Re: visualization file issues

ihayesjr — Fri, 16 Jun 2017 18:19:21 GMT

Hello @Anonymous,

Thank you for posting this to the Ideas forum but I would like to discuss this with you further. The visualization file is broken on purpose when you perform a Rename of the parent file. If you do not wish this to occur, Open the Vault Settings -> Visualization tab -> click the Commands button under the Visualization Management section. Uncheck the box next to Rename. This will do what you are wishing.

Re: visualization file issues

Anonymous — Fri, 16 Jun 2017 18:31:49 GMT

What would be the purpose of breaking the link for these commands? I see a lot of actions that I wouldn't want the link to break.

Re: visualization file issues

Anonymous — Fri, 16 Jun 2017 18:31:49 GMT

What would be the purpose of breaking the link for these commands? I see a lot of actions that I wouldn't want the link to break.

Re: visualization file issues

ihayesjr — Fri, 16 Jun 2017 19:09:20 GMT

When any of these commands are performed, the visualization file is technically out of date with the latest version of the design file. In the case of a rename, it could drive some confusion as the design file is renamed but the visualization file is not. If you performed a pack-n-go of the design file and included the visualization file, you would get the old name on the visualization file which might be confusing.

We place the following in the Help on this topic:

If the option for a command to remove the link is turned off, then when that command is performed, the Visualization Compliance property for the data file is set to Not Synchronized to indicate that the visualization file attached to the data file is out-of-date and may not accurately represent the contents of the data file. When the data file is viewed, you are warned that the visualization file is not synchronized. You can either update the visualization file or manually verify that the visualization file is correct. When a visualization file is verified, the Visualization Compliance property for the data file is set to User Verified.

Hope this helps.