We have do export our dwg as an eTransmitt out of AutoCAD at the end f our projects. This are may fils and exports. It wozld be grate, if there is a job of the job-processor that can do this automaticaly. It schuld be possible to config the settings for the eTransmitt. It have to be possible to define the settings specicicaly for diffrent projects, may be by using the category of the file. Show More

Users would like a way to delete documents linked to an article. Deleting 1 document = no problem Deleting multi-select documents = doesn't work - but is desired   Show More

Please change or allow Admin to change/remove Vault Thin Client Item View Tabs. They are not the same name or order as in Vault Thick Client.   Vault Thick Client:     General | History |Bill of Materials | Where Used | Change Order |View Vault Thin Client:  Properties |History | Bill of Materials | Where Used | Associated Files | Change Order Show More

Hi everybody, if the Thin Client option is set to disable the display of items, I'd like the “item” tab not to be displayed in the file area either. The same behavior is required for an ECO Show More

I spoke to Autodesk Support already about it and they suggested I should submit it here.   In the vault we have projects that are confidential where the files and folders are hidden from users who are not authorized. When confidential files are deleted, they end up in the Trash Bin and to unauthorized users, these appear as "Inaccessible".   But the problem is, unauthorized users can STILL restore these files form the Trash Bin. This does not make sense, why would unauthorized users be able to see these files in the Trash Bin in the first place? Every users must have the restore permission, in case they need to restore files they deleted. (withtin 30 days).   Can you add a filter which hides inaccessible files from users who are unauthorized in the first place. Show More

Autodesk Vault Professional - BOM Row Property Behavior Feedback Subject: Usability Concern: Non-Mapped BOM Row Property Propagation To: Autodesk Vault Product Development Team We are experiencing unexpected propagation with non-mapped BOM Row Properties in Autodesk Vault Professional. Problem: When a BOM Row Property (e.g., "Specific_Attribute") on a "grandchild" component (C) is modified within the BOM of a "grandparent" item (A) – where C is nested under a "parent" item (B) – the modification propagates. Instead of remaining unique to A's BOM, the change is applied to B's internal BOM definition. Consequently, if B is used in other "grandparent" BOMs (A'), they also reflect this unintended change. Example: Modifying Specific_Attribute for C in A's BOM leads to B's internal BOM being updated. This change then appears in A''s BOM, if A' also uses B. Impact: This behavior significantly limits our ability to manage item variations specific to a higher-level assembly without duplicating "parent" items. It increases complexity and can lead to data management challenges. Request: We request a mechanism to define and modify BOM Row Properties that are truly unique to the specific instance within the highest-level BOM, without altering the master BOM definition of intermediate sub-assemblies. This would greatly enhance flexibility and usability for complex product data. Show More

Can we please have the ability to add "File Link State" as a property column to export to CSV?     Show More

Wir würden gerne in der Dokumentenansicht neben dem Symbol "Verknüpfung mit Artikel" auch ein Symbol für den Artikelstatus sehen. So erkennt man schnell, ob der Artikel am Dokument auch freigegeben ist. Unsere Arbeitsweise sieht vor: 1. Dokumenten- Freigabe 2. Artikel- Freigabe 3. mit der Artikel- Freigabe werden die Daten ins Fusion PLM übergeben. Bei einer Änderung erhät das Dokument eine neue Revision. Bei der Freigabe des Dokument wird der Artikel in "Bearbeitung" genommen. Der Artikel muss nun noch freigegeben werden. Leider kann der PDM User den Status des Artikels direkt am Dokument nicht sehen.   --------------------------------------------------------------------------   We would like to see a symbol for the article status in the document view next to the "Link to article" symbol. This way you can quickly see whether the article in the document has also been released. Our way of working is as follows: 1. Document release 2. Article release 3. With the article release, the data is transferred to Fusion PLM. If a change is made, the document receives a new revision. When the document is released, the article is put into "processing". The article now has to be released. Unfortunately, the PDM user cannot see the status of the article directly on the document. Show More

In the Articles area, users miss the possibility to integrate commands in the headers, as is possible in the Documents area   Show More

Dear Autodesk - we HAVE to fix this in the next release of Vault. This is insanely annoying to work with. As a summary, when Assigning / Updating Items, Vault will automatically choose to associate other files which it seems to think are appropriate to associate to the Item, and more often that not these automatically associated files are not intended to be tied to the Item. When the Item is released, this then will then lock down these unrelated files, and the solution is painful. I will relay the solution below: 1. The Item has to be edited and the unrelated files have to be removed from the associated list. Note, to make things additionally annoying, only one file can be removed at one time. It may look like you can select more, but as soon as you hit Save, every file other than the first selected pop back again. So you have to select one, right click remove, save, then move to the next and repeat. 2. After removing the unwanted association, the file itself still stays locked. The quickest solution to this is to then create an Item from that file, Release it, then Roll Back the Lifecycle. This will unlock the file. Crazy.   Then, to make matters worse, the next time an upper level assembly which contains the Item (which has had its non-intended association removed) is Updated - the non-intended associations are added again! This is completely insane to be told that this is by design, and that there is no solution for it.   PLEASE, can we have this resolved in an upcoming release Show More

We are using purely Item centric way of working with Vault. This means that files are controlled by the Items lifecycle states. If the Item is Released, files are locked and so on.   Problem is when it comes to components marked as Phantom, Reference or Purchased as they are handled differently in the Assign Item process. And they should, but there is no way to handle these with an Item Centric lifecycle.   Phantom - Never becomes an Item Reference - Never becomes an Item Purchased - If an assembly is marked as Purchased, its children will never be Items   What I would like to see is that Vault do create Items out of these components to a specific Item type i.e. with same names "Phantom, Reference etc." so they get visible and handled in the structure.   I would also like to see the CAD BOM inside Vault which corresponds to the Model tab in Inventor. There is no way to identify for example a Phantom assembly inside Vault. Preferrably one tab with the CAD BOM and then another tab with the EBOM (corresponds to the Structure tab, same as it is now).   There are numerous ways to solve this with different workarounds, I know. One way is to never, ever use Phantom or Reference and use a Property telling i.e. an ERP integration to do the needful. Another could be to have a small lifecycle for these files with "Locked" and "Unlocked" states. But still it is a hassle for the engineers and I am sure it can be done by making Vault better.   I have a feeling that there has not been any real development on the Item Master side in Vault for ages, now we see a lot of interest in using the "Item centric way of working" so maybe it is time for a makeover.   Thanks! Show More

We just implemented workgroup replication for our overseas subsidiaries. We have been using items in Vault form the start in 2012 and heavily rely on those for a lot of processes (Vault-ERP integration, manufacturing, quality documents linking etc.). Our output usually is more than 200 items a day. Now we start facing issues caused by the ownership design in replicated environments. One issue is, that if you update an item, the ownership of all child items is transferred to the workgroup that tries to update the parent item. This is a killer for re-use. Some of our bolts and nuts are used in thousands of designs. Their items are released and typically do not change a lot. Even if a user is not even allowed to modify the items of these bolts and nuts, whenever a assembly is released which contains one of these items in the BOM, the item ownership will be transferred. That means ownership likely will be passed for these items all the time between the different workgroups.   I foresee that this will impact us a lot, because people will start seeing error 370 and 321 all the time.   My idea is: If someone does not have priviledges to modify an item, leave the ownership where it is when updating parent items.         Show More

supplier documents (PDF, images, etc.) are linked to the design Inventor documents (IAM and IPT). When the Inventor documents are released, the supplier documents should be linked to the article. ------------------------------------------------------------------------------------------ Lieferanten- Dokumente (PDF, Bilder, usw.) werden an die Inventor Dokumente (IAM und IPT) verknüpft. Bei Freigabe der Inventor Dokumente sollen diese Daten an den Artikel verknüpft werden. Show More

It would be a benefit to see the quantity in the Where Used tab of an item. It would be nice to see how often the item is used in different BOMs.   Show More

The 3D model has a 2D drawing derivation and is linked to an article. = ok Users now need further initial views of other models on the "original drawing" in order to be able to better represent or explain certain things. Document link within Vault = o.k. Item link on "main document" only links model = primary and IDW = tertiary. I.e. there is no extension to linked files for referenced views = o.k. BUT!!! In the article link of the model from the referenced view, the drawing in which the model was installed as a reference view is also displayed. From a purely data point of view, this can be understood. From the user's point of view, however, this is very confusing and leads to uncertainties and errors, especially if a model has been installed as a view in umpteen different drawings, the list of linked 2D drawings on the article is very long and you have to be very precise to find the correct drawing for the article. As a workaround: 1. Removing the link is a hassle and not sustainable, since the link will be restored the next time the article is updated. 2. Alternatively inserting the view as a screenshot (JPG or similar) prevents the item linking, but the screenshot of the view is not tracked when changes are made to the original model. In connection with other processes in the company (e.g. PDF creation and assignment of the PDF to the article), further risks arise that incorrect data may be passed on to the ERP. Requirement / wish: • Possibility of adding a property to a reference view in Inventor, so that this link is not relevant to the article. • Identification of 2D drawings in linked files on the item (symbol / color / separate area / ....) if they only contain a reference view to the 2D drawing. Ideally, this identification is created and updated automatically.   More Details see Support CaseNo:20578567   Show More

Our company wants to utilize installation/location codes as a way of parts kitting for assemblies.  Currently the only way to produce a BOM from AutoCAD Vault with the reference designators visible is to save the BOM view as an Excel worksheet.  This then requires additional manipulation in order import into our purchasing system.    It would be ideal if reference designators were available when setting up a BOM export mapping.  This would eliminate all the extra columns and clutter that is currently associated with saving of BOM views. Show More

Allow users to paste images when describing lifecycle change, or check in / check out transactions. This would help users to insert imagens with notes of which places to change.   For instance: Allow insert of imagens in the following interface:   Thus, users also would be able to link with Standards to help next changes. As Follow X requirements could have a print of a bending guideline.   Appreciate any support from the community. Show More

I would like the ability to use the Job Processor to publish PDF files of office documents. This would allow us to attach released documentation of our products to their corresponding items ready and approved for internal/external use.   Our organisation has 2 user groups for the Vault. Design Engineers - Using Vault Professional and non-design engineers, sales, planning, production and purchasing using Vault Office. The second group is starting to notice the security and relative ease we manage our files. We have fully integrated Vault's Project Folder, Item Master and Engineering Change Orders into our product lifecycles. We now want to expand this to additional design documents such as:   Product Brochures Product Datasheets Product FMEA Internal/ External assembly/installation instructions   As well as QHSE documents: Norms Procedures Workflows etc.   All these files have a revision system which is currently managed by hand. We would like to transfer these files into the vault and attach the released (.pdf) versions to corresponding Items. Show More

 I would expect that the property set of the new category would be applied during the the category change, or at least a pickbox to force the new property set. currently you have invoke a separate command Add/Remove properties to bring them in or remove them. Show More