By Warren Baird-Oracle on May 12, 2016
I wanted to give a quick overview of one of the changes in AutoVue 21.0.0 that I've heard a few questions around. Many complex CAD documents span multiple files - there will be a base document (often called an assembly in 3D CAD), and a series of associated files that we broadly call external references or Xrefs (often referred to as Parts or sub-assemblies in 3D CAD). The way these Xrefs are handled when uploading a file from local disk (not when integrated into a system like Agile, P6 or Web Center Content) has changed in AutoVue 21.0.0, and I'll give you some additional details on that here.
In earlier versions of AutoVue there was a mechanism in place that allowed the AutoVue server to request missing Xrefs from the AutoVue client. The way it worked was that if the user did a 'file open' on a file named 'Assembly1.asm' from their local hard drive, it would get copied to the AutoVue server and processed. If during that processing it found that it needed a file named 'Part1.prt', the server would tell the client, and the client would search the local filesystem for a file named Part1.prt, and if found, it would copy that file to the AutoVue server. That process would repeat until all of the associated subassemblies and parts were copied to the server.
This process has a couple of problems:
- Performance is problematic, since the copying of files happens as a series of separate transfers, with some processing of the file in between
- There is a risk of unexpected results. The algorithm used to find files on the client side was pretty good, but there was a risk that if the files and folders were not set up the way we expected that we might find *some other* local file named "Part1.prt", and the user might see the wrong part in the model.
As a result, starting with AutoVue 21.0.0, this mechanism of finding and uploading local Xrefs has been removed, and our recommendation is that if you need to open a file with Xrefs from a local file system, that you do it by creating a zip file containing the base file and all Xrefs, and then opening the file through the zip file. This ensures that AutoVue gets all of the right Xrefs, and improves performance by sending all of the files in single transfer.
To reiterate - this only impacts files coming directly from the user's local filesystem - if you are integrated into a content management system, and are opening a file from that system, it will take care of providing all of the associated Xref files to the AutoVue server for you automatically, and this change will not impact you.
If you have any questions about this change, feel free to ask below!