• This forum is the machine-generated translation of www.cad3d.it/forum1 - the Italian design community. Several terms are not translated correctly.

review submitted to the table

  • Thread starter Thread starter stilo64
  • Start date Start date

stilo64

Guest
Bye to all,
Is there a system that disconnects the updating on table on reference set?
I have a set that I have modified but I want the first table to be disconnected, without updating, and on the new table you bring back the changes I made on the whole.
It's a problem that I can't solve, I'd like there to be a brilliant idea of how to handle the revisions for a set with the historian on table.
thank you for the attention but I would be grateful if there were someone who would give me an optimal solution for inventor.
 
the table is associative, so it reflects every slight variation you make on the iam.
If what you want, as requested, is a complete release, export to dwg (autocad and not inventor ).
you will have a document, always editable, frozen to the previous version.
 
in fact a possibility exists: the postponement of table updates (in the table go on tools > > drawing > check postponed updates. until the table comes up.

However I only recommend the possibility as a style exercise: I would do as stefanobruno says it's a mistake if you need the historian. postponed updates should only serve to not have huge designs that are constantly updated, if by mistake the update is screwed.

by curiosity, users of the vault, the original request what is handled?
 
I'm sorry if I answer now, but I've been influenced.
In fact, those who worked before me, were used only autocads and sometimes a former colleague of mine made drawings in inventor and I saw many table masses coming from inventors.
But the question comes to me spontaneously, but if one had no autocad, I think there would be a way to store the revisions in the table masses. and also true that one could copy the axieme then modify it and on put at the table make a save with the name and replace the views with the new model, that what I thought, but it seems complex. I imagine if one has a big set and has a change to make! It does not save by name another set and then change it, it is found with many identical but modified axioms for a small detail.
I thought in the model's axieme, I think with the representations with the views and levels of detail you could work.
thanks to your advice
 
Hello, thank you for responding to me in fact could be a solution the postponement, according to you if I activate the postponement and save it by name a, then I make another copy of the table calling it b, and disable the postponement, could it be a solution?
the aid will always be the same but in the table I will have one with the activated postponement and the other with the disabled postponement!
Thank you for your help.
 
I believe that with the representations with the views and levels of detail you could work.
with this solution,
It doesn't come to any conclusion.

if you want an editable historian, disconnected from the model, save in dwg.
if its a historian not editable saves in pdf.
If you want a model historian, you make a pack & go of the first rel., the archives and send on the revisions without worrying about dirtying the first rel.

postpone updates, in addition to going to be blessed as soon as your colleague opens the design without paying attention, gives you a copy that has the value of a dwg, so, so much worth doing immediately the dwg, without therefore running the risk of a wrong opening.
the representation of views and detail serves anything else.
with the vault you should be able to do it, but simply because it deals with him to store obsolete copies.
I am not sure of this last sentence tomorrow, if I remember, I ask those who use it intensively.
 
Thank you stefano, you're right, I should save in dwg, so if a colleague opens it can't hurt, the master will always be the inventor's table.
I think we don't have access to it.
 
the vault manages the life cycles and keeps the historian not only of the revisions but also of all versions that are archived. you can preview, recall or restore previous versions as last revision.
 
the vault basic however does not manage the revisions.
That's the professional, but you have to get it. . . .
 
hi in case of revisions use design assistant that installs alone with inventor, I make a copy of the model and the put in the table and I reconnect, in this way, a bit sluggish, in case of necessity I can reprint or restore all in a short time.
 
hi in case of revisions use design assistant that installs alone with inventor, I make a copy of the model and the put in the table and I reconnect, in this way, a bit sluggish, in case of necessity I can reprint or restore all in a short time.
vault basic as it has been noted, does not handle revisions (at max you can freeze a situation and return to that configuration at any time). I would use design assistant
 

Forum statistics

Threads
44,997
Messages
339,767
Members
4
Latest member
ibt

Members online

No members online now.
Back
Top