iAssembly

[Anonymous]

Hi

I have created an  iassembly in autodesk inventor 2014 And it's drawing but whenever I modify the assembly Drawing is getting out of date.

drawing shows all views are out of date because of this I have to create Drawing again and again I have updated all views by Global update and normal update but still it's not getting updated Can you give me solution on this

[-niels-]

Welcome to the forum!

I'm not too familiar with iassemblies, but i'm wondering; are you generating the files again after you make your changes?

Also, on the drawing, make sure the "associative" checkbox is checked.

[salariua]

Niels is right, you need to update members as per my error here:

There are work-arounds but that's just being lazy updating from the drawing instead of doing it correctly and I might add that these don't always work and you still need to do it in the model.

(work arounds that force update would be to switch back and forward the member in the model state of the view, or to suppress/unsuppress the view).

What you need to understand is that Inventor will generate separate files for each member so these need regenerating from time to time (when major changes occur).

[sam_m]

I get soo frustrated with iAssemblies - they should be great, but add Vault unto the mix and suddenly they're v frustrating.

It's fantastic that the BOM manages the parts lists for each varient and you can easily jump between each when modelling, but (as of 2014 and I hope it's a LOT better with the newer releases) Vault really doesn't play well with them.  I even asked a VAR if I was doing things correctly and their response was to use iLogic instead of iAssemblies - but (afaik) that doesn't offer the same BOM varient control.

Generally, working with them and Vault is fine, until you want to update them...

Check in from iam and it will usually remember to grab all the varients, but try from the idw and it seems to forget them all except those on the idw - with normal work you can design a part/assembly, bring it into a drawing and then check it all into Vault when finished with the drawing, but not iAssembly, create assembly, then drawing, then back to iam to check in that with the varients, then back to idw to check in that...  argh!?!?  Come to update the design and you want to assign it a new part number, no problem, use Copy Design - oh, wait, it doesn't work with iAssemblies...  I seem to remember that Change State can also forget about the varients/generated files too, leaving the parent file saving fine but none of the generated/varient files, so drawings don't update.  I can't remember all the quirks with them, just that I have to pay a lot more attention what's happening with Vault when using them than I feel I probably should.

Sorry, this doesn't really help the topic, just felt I needed to vent about Vault's "fun" with them 😉

[mcgyvr]

Whenever I modify an iassembly I always do a "rebuild all" then generate the members again..

Its just habit now.. rebuild all, generate, save then go to the drawing

[Anonymous]

very helpful!

[swalton]

I basically gave up on iAssemblies and I only use iParts for purchased hardware that does not change, because of the limits of Vault.

However, sometimes I need to edit to an iPart/iAssembly Factory.  When I do so, I create an Update Assembly that contains all the generated members.  I check that assembly and all the members out of Vault.  Once the edits to the factory file are complete, I open the Update Assembly and re-build all.  Then I add any new members (from my edits), save and check-in to Vault.  This also is useful when performing file migrations.

[Anonymous]

Great help , tried your suggestion now every thing fixed.

issue was i need to make the assembly configuration on inventer so i opt iAssembly in inventor , then i achived the variable dimension on 3D assembly but when i am trying to get those on 2D dwg i was getting error (image attached) after implementing your suggestion issue is fixed.