iproperty idw distinct components

[smoking]

Good morning to all,
I wanted to ask if there is a possibility to insert the custom iproperty of an idw within the "different components" of a set?
I know it's a bald operation, but I have to recompile axioms where the properties of the individual components have been split into part on the ipt models, partly on its idw.
of the same theme, only for indication: from the "document/drawing settings" of an idw you can perform the "copy iproperty template settings". Maybe there is some procedure to perform the reverse operation and then make the properties available in "different components".
Thank you very much.

 

[batleo]

Hi.
yes the possibility exists, --> 1] in ipt file and/or iam create your own custom iproperties
2] in the idw insert parts list
3] enters the list parts --> at the top left "choice columns"
4] where you see drop-down menu "all properties" swipe up to "user property"
5) new property
6] assigns the same name as point 1 iproperties]

 

[smoking]

thank you batleo, unfortunately it is not what I look for. I would need to make available an (or more) iproperty of an idw within the "different components" of a set. what you have explained makes available an iproperty of an ipt/iam in the list parts of an idw. basically I should perform the reverse procedure.

 

[Peppe]

The separate components show the data containing the 3d model and not the idw table which retrieves information from its 3d reference model.
perhaps passing by macro you can copy custom iproperty from idw to ipt/iam but are not very practical of ilogic.

 

[batleo]

what you ask is the opposite of how inventor works, because idw reports the model information that is ipt or iam. so much is that in the options it is present copy all iproperties from model and not vice versa.
But why can't you put what you need in the model?

 

[batleo]

I think the string of ilogics should be something like this:

iproperties.value ("customa," "fintura") = iproperties ("customa," "fintura")

But so it is to be done back that I create the model , then put in the table , then syncronize the properties

 

[smoking]

what you ask is the opposite of how inventor works, because idw reports the model information that is ipt or iam. so much is that in the options it is present copy all iproperties from model and not vice versa.
But why can't you put what you need in the model?

I'm very agreeable, I work exclusively with iproperty on models. It was for me that I would abolish iproperty on the table. Unfortunately I have to deal with customers who are not ordered (to use an euphemism) in the distribution of the properties: idw or ipt doesn't matter. for those who do not have a pdm, it is essential to have good familiarity with "different components", a fundamental tool for managing the complexes and compiling the iproperty.
could be an idea to make the same iproperty appear on both the idw and its model, but should be aligned; Unfortunately the iproperty of the model are completely independent from those of the idw, also presenting the same name. if you have any other idea....

 

[batleo]

but in case of creating an ilogic rule that does, can iproperties of the model overwrite? or changing them is a problem?

 

[smoking]

but in case of creating an ilogic rule that does, can iproperties of the model overwrite? or changing them is a problem?

if you could create an ilogic rule that, compiled an iproperty on the ipt, duplichi automatically automatically The same on the idw, it could be fine. However, the procedure should be automatic (type of opening or saving files) and possibly bidirectional.
or:
1) Implementation/genero iproperties on the ipt (or on theiam) also massively through "different components"
2) I create relative idw
3) to save (and at any subsequent opening or rescue) iproperties align automatically

It might work, but I don't have much experience with ilogics...

 

[DrBarde]

the fact that it is bidirectional is usually a problem in managing documents.
there must always be a master document and one or more slave. Otherwise, who commands on who?
at interaction level, when talking about computer science and management of documents, it is usually a golden rule.

 

[batleo]

but from ipt or iam to idw, you can do without too much debate, in both ipt template files. /iam create your iproperties and saves as a model, in the idw template file go to the command panel tools--> Document setting--> drawing --> the last item is copy from template --selects all

 

[smoking]

but from ipt or iam to idw, you can do without too much debate, in both ipt template files. /iam create your iproperties and saves as a model, in the idw template file go to the command panel tools--> Document setting--> drawing --> the last item is copy from template --selects allView attachment 70063View attachment 70062

It's the operation I mentioned in the first message. the procedure only allows migration of iproperties, but do not remain aligned in the compilation. as said iproperties ipt are completely independent from idw iproperties. by filling out any iproperty on ipt (place to baptize this model as reference) the same does not automatically fill out on idw.

 

[batleo]

excuse ops I forgot a piece to align them to the model, in the idw file when the model, go to the management board--> updates properties, and every time you update them in the model

 

[smoking]

the fact that it is bidirectional is usually a problem in managing documents.
there must always be a master document and one or more slave. Otherwise, who commands on who?
at interaction level, when talking about computer science and management of documents, it is usually a golden rule.

bidirectionality is an accessory feature, it could go very well to elect the ipt or theiam as master and proceed with the compilation of the related idw.
If someone gives me some input to compile a possible ilogic, then I can arrange.. . .

 

[smoking]

excuse ops I forgot a piece to align them to the model, in the idw file when the model, go to the management board--> updates properties, and every time you update them in the modelView attachment 70064

...you could then create automatism only to automatically launch the command in opening or saving

 

[batleo]

by clicking updated property goes to copy the iproperties of the model inserted in the table, (be careful ) if you put multiple models in single table iventor will always take those of the 1st inserted

 

[smoking]

by clicking updated property goes to copy the iproperties of the model inserted in the table, (be careful ) if you put multiple models in single table iventor will always take those of the 1st inserted

I tried and everything seems to work. Obviously it is a procedure that involves some risk because it requires manual intervention. if you have any idea (or if someone has already done something similar) aboutautomatism with ilogicCome on. in any case thank you for the availability, you were very kind

 

[batleo]

good to make, looking I found code

modelname = io.path.getfilename(thisdrawing.modeldocument.fullfilename)

'read the values from the iproperties in the part file
'then apply to the iproperties with the same name in the drawing file

iproperties.value("project", "description") = iproperties.value(modelname,"project", "description")
iproperties.value("project", "revision number") = iproperties.value(modelname,"project", "revision number")
iproperties.value("project", "project") = iproperties.value(modelname,"project", "project")
iproperties.value("status", "checked by") = iproperties.value(modelname,"status", "checked by")
iproperties.value("status", "eng. approved by") = iproperties.value(modelname,"status", "eng. approved by")
iproperties.value("status", "eng. approved date") = iproperties.value(modelname,"status", "eng. approved date")
iproperties.value("status", "status") = iproperties.value(modelname,"status", "status")

ilogicvb.updatewhendone = true

with this rule copy iproperties from model to idw
insert all you want and then put it as an external rule, and then put an event trigger so you run when you decide, or create a key module.

 

[smoking]

good to make, looking I found code

modelname = io.path.getfilename(thisdrawing.modeldocument.fullfilename)

'read the values from the iproperties in the part file
'then apply to the iproperties with the same name in the drawing file

iproperties.value("project", "description") = iproperties.value(modelname,"project", "description")
iproperties.value("project", "revision number") = iproperties.value(modelname,"project", "revision number")
iproperties.value("project", "project") = iproperties.value(modelname,"project", "project")
iproperties.value("status", "checked by") = iproperties.value(modelname,"status", "checked by")
iproperties.value("status", "eng. approved by") = iproperties.value(modelname,"status", "eng. approved by")
iproperties.value("status", "eng. approved date") = iproperties.value(modelname,"status", "eng. approved date")
iproperties.value("status", "status") = iproperties.value(modelname,"status", "status")

ilogicvb.updatewhendone = true

with this rule copy iproperties from model to idw
insert all you want and then put it as an external rule, and then put an event trigger so you run when you decide, or create a key module.

great, I customized as well as from image and I introduced a trigger in rescue and it worksa detail for those interested in this type of procedures:
the "physical" property group of the model is not recognized in the rule within the idw.thanks again batleo for the collaboration.
a curiosity: do you know a path from which you can find common utility ilogics, such as this for example?

 

[batleo]

Hi.
for the material the string could be this:
properties.value("custom", "material") = iproperties.value(modelname,"project", "material").
in what you've done, you have customised it.

to answer where to find ilogic rules, as the first source I look for in this forum, because many times I face a problem that probably someone has already met and solved, or google with "inventor+ilogic+{domanda}"