iParts and iLogic in the factory not pushing to members

[chris_blessing]

I have created an iPart factory in which I wrote an iLogic to convert the weight to a whole number and write it as a custom property. The iLogic rule has been applied to the Event Trigger "Before Save". This set up works fine on the factory and all of my other parts.

Within the member, it seams as if the the iLogic rule does not push to the generated member, but the member remembers the event trigger so it continues to give the error that it cannot find the rule. 

Am I doing something wrong, is this a glitch in this part, or is this an issue with Inventor 2020?

[A.Acheson · Accepted solution]

No glitch, Ilogic isn’t support in iPart members as they are read only. When used as a library part anyhow. They are like a snapshot of the factory. Information gets pushed from the factory to the members through the factory table . You can run a rule on the factory but either suppress and remove the trigger or remove the rule and use as an external rule.  In other words place the mass in the table and disconnect the source. 

Here the mass issue into table discussed.

One of the major drawbacks of having a custom iprop weight is that this is now a second iproperty independent of the mass iproperty. Which means you have to have an iproperty weight in all your regular parts and assemblies. So it becomes a chicken and an egg question. I don’t believe the idea was ever actually implemented and it becomes a big rats nest of workarounds for such a simple implement. 

A workaround would be to have a density change on custom material but it becomes a little awkward trying to get a data sheet mass to be like your model.

[chris_blessing]

I agree with your drawback on a normal basis. In our case, our design department is new for the company and we are having to create new 3d models for all of our machined parts anyway so I'm basically starting from scratch with new templates anyway. I'm using the custom iproperty on a note just for general purpose when they go and try to move these things around they know what they are looking at.

[chris_blessing]

I tried to do it as an external rule, but it wouldn't find it from one user to another. I gave up and just added it to the emulate document. It hasn't been an issue to simply add it to old models when we come across it.

[chris_blessing]

Why would the ipart member retain the event trigger, but not the rule?

[A.Acheson]

Not really sure of the in's and outs of it ilogic is likely blocked to run on the members. I came across the same drawbacks before and opted to have external rule to do any calculating and remove when table was complete. Mostly to bring in a bunch of iproperties from excel. Knowing the member file accepts no modification directly is what I've learned. The mass iproperty works well if the model is accurate.