Content center, custom description with length fails when using framegenerator

[softwaremanagement]

This seems to me a bug in the 2019.3 (build 278) release, the problem is:

We've created a custom familiy in the content center that has the 'length' in it's description, amongst other changes.

This works fine when the part is placed from the content center, either as custom or as standard (first two entries in the bom list on the screenshot).

However, using the framegenerator (insert frame), the length always defaults to 0,001. The length updates just right in the part number field, but if you'd put it anywhere else, same result: It always reads 0,001.

This behavior basically means it's impossible to get a length indication in an iProperty other than part number while using the framegenerator. Not working as intended..?

[jan_priban · Accepted solution]

Hello,

I suppose you defined new column referencing {B_L}  in Content Center family table and mapped this column to Project.Description. When you create instance by Place from CC, such instance has correct Description = current value of B_L is reflected. But when you create instance by Frame Generator, B_L is not reflected.

This is because Frame Generator uses own instancing mechanism, different from Place from CC. Furthermore/Because, if Frame Generator modifies a frame (by command like Trim to Frame, Notch ...) then B_L does not reflect current length. B_L is base length, not actual/current. For this reason, Frame Generator (Place from CC as well) uses user parameter G_L which is exported also as custom iproperty. G_L reflect actual frame length.

G_L is created when part gets authorized . But G_L is not available in CC family table - column definition. So no way how to define CC family table column referencing {G_L}.

So my proposal is: Let CC table as it is, no column mapped to Project.Description and drive your iProperty Description by yourself. It means by iLogic:

- create instance from your frame family (first member is fine) by File -> Open from CC

- Save as NewTemplate.ipt

- In this file define iLogic rule setting Project.Description using G_L

- Let it run On Save event - define trigger

- Save and close NewTemplate.ipt

- Using CC Editor replace family template, use NewTemplate (with iLogic inside)

- Instances created from your family created by Place from CC or by Frame Generator will have Description reflecting G_L property.

I verified it and it works.

Regards

Jan Priban

[softwaremanagement]

Thanks for the in-depth explanation Jan! I will try/use your solution.

Though this still leaves me a bit stumped, I've been actually using the {DESIGNATION} property in a new column to map the length data to the Project.Description (though {DESIGNATION} is indeed formed with the {B_L} property). However, all 'standard' CC parts all use the {DESIGNATION} property, which includes length, and they wíll work just fine for framegenerator. 

This is easy to test, copy a familiy, add a column with the same expression as the part number column and map it to the description. Now insert some frame members and voila: Part number displays the correct length, description does not.

Some black magic is going on here...

Cheers, Rutger.