Custom Content Center Part Template

[BK-MTFNE]

So I have approached this in every possible way I can think of with no luck so I am hoping someone has dealt with this or can point me in the right direction.

I have gone through and created my own content center library. This is just a copy of a lot of the items already in the content center but altered to fit our company standards such as File Name, Stock Number, Part Number and so on. I also have custom templates for Sheet Metal.ipt, Standard.ipt, Assemblies and Weldments as well as a comprehensive .idw template. My problem is that when I open from Content Center and it creates the part it does not use the custom designed .ipt file that has a lot of iLogics in it that are needed. Is there a way to ensure that any Content Center part is created with my custom .ipt file?

[Frederick_Law · Accepted solution]

Don't think so.

CC got it's own ipt.  The one when part was published.

You can try publish new one with your template.   I don't know if iLogic will get publish with it.

Do you need the iLogic rules in the parts?  Can they be external rules?

Maybe you need iPart or Model State.

What does your rules do in the part?

[BK-MTFNE]

I do need the iLogics but I never looked into the external iLogics cause having them in the .ipt files worked great until now.

[gregory_nickol]

If I'm understanding correctly, you have a set of templates with all sorts of iLogic in them. You want your content center parts to have that iLogic also?

Content center doesn't pull from your generic part templates, it pulls from what is essentially a parameter driven copy of EACH part family. It's essentially like taking a pre-existing .ipt, changing parameters, and doing a saveas. I don't know if content center parts can handle iLogic, so try this with just one part to see if it works:

1) Save a backup copy of your CC Library.

2) Save a copy of a part to your machine that you want these rules in, any size/configuration from the family is fine.

3) Save a backup copy of this file.

4) Put the iLogic rules into the freshly generated part file and save it.

5) Back in the library editor window right click on the family that you added rules to and "Replace Family Template" with your modified file.

6) Place any row from that family now (as custom) and see if the rules are there. If so, repeat 2-5 until all your parts have rules added (doing steps 1 and 3 as often as you feel necessary). If this doesn't work, it's likely not possible at all.

[BK-MTFNE]

Thank you Pineapple, that fixed my headaches in about 10 minutes. It's not exactly what I was looking for but it certainly works.

[BK-MTFNE]

@gregory_nickol  I tried that method and everything changed over EXCEPT the iLogic. I believe you and @Frederick_Law are correct in the assumption that those .ipt the Content Center uses cant handle iLogics.

[gregory_nickol]

Having internal rules is nice for the sake of making it easier to tell it which file it's supposed to be running on, but if you can make it work with external rules I'd consider that best practice. Any time you have rules built into your template files, you're now copy and pasting that code into every single instance of the file which does 2 things. Wastes hard drive space, and slows down your opening/saving of files. And if it's on a shared drive or a vault server, it may annoy your IT guy too with extra unnecessary network traffic.

[Frederick_Law]

The question remains, what does the iLogic do for CC parts?

Do you really need it?

Update part number?

[BK-MTFNE]

It changes file names and part marks according to information pulled from another system we us. I was able to write some iLogics to make it read that information but I cant link that to the actual content center library I created as there are too many variables associated with said information. I would need to write some serius scripts to be able to get it to work write.

[jean-francois.morin-verville]

Hello,

I have a question also in regard with the content center ''part template''.

The template that i use when creating a new part has some custom Iproperties and when i create a new part using my custom content center, the  custom Iproperties that i thought would have been available in that new part are not there.

I know i could use the Design Assistant to copy those custom Iproperties but is there a way to have those new part from the custom center already have those properties every time?

Thank you

[Shag_Bore]

It was a little bit of groundwork, but I created a part (.ipt) or iPart of every part or profile that we use, angle, flatbar, HSS, etc...imbedded my iLogic rules into those parts, ensured the event triggers were set,  and published to my custom library. Been working so far. I decided doing this instead of trying to run rules externally. 

It is easier to manipulate any iProps, part numbers, etc using ilogic instead of trying to concatenate in the family table, more options for formatting. 

[jean-francois.morin-verville]

hello,

Yes, ipart is could be a solution.

Thank you