iLogic in Frame Generator

[maskintegning_dk]

Hi.

I have iLogic rules in my part template "Standard.ipt". It works perfect.

However when I make a part in Frame Generator, my iLogic rules has disappeared??

What can I do?

Best regards

Lars 

[A.Acheson]

Hi @maskintegning_dk 

See similar thread referring to skeleton. Where do you expect the ilogic rules to act? If you want the ilogic rules in the skeleton then the standard.ipt will achieve that. If you want them in each CC part then this needs to be loaded to family template. 

[maskintegning_dk]

@A.Acheson 

Hi Alan.

I've read all the threads in here. They do not help me.

No. My problem has nothing to do with the Skeleton.

It's only a matter of the part (.ipt).

All my rules have disappeared in all the parts from Frame Generator.

What can I do?

Best regards

Lars

[A.Acheson]

Hi @maskintegning_dk 

If you load in rules locally to specific parts and you then change members by selecting a new profile from CC through the dialogue those parts get deleted from your workspace  and are recreated. In this case you will loose those rules and any change done locally to the part. 

Could this be what happened? 

[maskintegning_dk]

@A.Acheson 

Hi Alan.

Thanks for replying.

The rules have never existed in frame generator parts (.ipt)

But they are present in normal parts.

So the question is:
How do I get my iLogic rules into the parts (.ipt) from Frame Generator? 

They are non-existing when I open a part from Frame Generator.

Best regards

Lars

[maskintegning_dk]

@A.Acheson 

What is CC?

[A.Acheson]

CC is short for content center. The CC parts do not use the standard part folder when creating new or existing parts. Instead they use the template part file that was used to publish them to CC center. So if you want to use ilogic rules you need to replace the family template that the family uses. To do this place a family member, add your rule then save. Go to family template and choose replace family template.

See help page in this method

The fact that your are using frame generator addin has no influence on this setup. 

[maskintegning_dk]

@A.Acheson 

Hi Alan.

Thank you for your effort.

This is simply to difficult to me, so I'm dropping this project.

It seems like I have to replace every file in the list.

What a waste of time. 

Have a nice sunday

Best regards

Lars

[A.Acheson]

Yes , I would agree it is too much work. You can use ilogic external rules to act outside of the assemblies and parts. Have you tried that approach? This is always my preference as I might like to change the rule workflow and I wouldn't want to change every part that the rule is contained in.  What are your ilogic rules doing?

[robbeRtek]

we work around this, with custom iProperty 'typeobject' so you can give a frame member a typeobject= part-type1
Then add an rule to your assembly, or with an trigger.
loop trough all partcomponents :
If  typeobject = part-type1 then
'your action/rules
(maybe you need to make some small differents to the rules, because you call them from assembly environment instead from part)
end if 
next

We use it to check lenght: if profilelength(framegenerator component)>6000mm then color change to red--> not availble on marcket

[robbeRtek]

With custom iproperty, you can add custom value for each design.
so you have lot of control. so we prefer this instead of loop trough all parts and checking document type

an other suggestion
you can make your rules external,
so its easier to call them
If  typeobject = part-type1 then
occ.edit
'your action/external rules
(maybe you need to make some small differents to the rules, because external rules acces parameters a bit different)

occ.exitedit

end if 
next