<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: iAssembly in Inventor Forum</title>
    <link>https://forums.autodesk.com/t5/inventor-forum/iassembly/m-p/5849208#M360785</link>
    <description>&lt;P&gt;I basically gave up on iAssemblies and I only use iParts for purchased hardware that does not change,&amp;nbsp;because of the limits of Vault.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However, sometimes I need to edit to an iPart/iAssembly Factory.&amp;nbsp; When I do so, I create an Update Assembly that contains all the generated members.&amp;nbsp; I check that assembly and all the members out of Vault.&amp;nbsp; Once the edits to the factory file are complete, I open the Update Assembly and re-build all.&amp;nbsp; Then I add any new members (from my edits), save and check-in to Vault.&amp;nbsp; This also is useful when performing file migrations.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 07 Oct 2015 13:25:59 GMT</pubDate>
    <dc:creator>swalton</dc:creator>
    <dc:date>2015-10-07T13:25:59Z</dc:date>
  </channel>
</rss>

