Good afternoon,
I have made a flange with multiple rules so that when I change the parameters, the part changes with it. That works really good. Now is it so that I want to publish the part to the content center, that has succeeded. But when I open the flange in an assembly, I can only choose the exact same part as the part that I published. Is there a possibility that I can publish the part so that I can choose between al the possible combinations of the parameters? I know that you can put all the parameters in the Family table, but that would be a lot of work. So is there an easy way to publish the part with the rules that belong to it?
I attached the flange file to this post.
Thank you in advance!
Good afternoon,
I have made a flange with multiple rules so that when I change the parameters, the part changes with it. That works really good. Now is it so that I want to publish the part to the content center, that has succeeded. But when I open the flange in an assembly, I can only choose the exact same part as the part that I published. Is there a possibility that I can publish the part so that I can choose between al the possible combinations of the parameters? I know that you can put all the parameters in the Family table, but that would be a lot of work. So is there an easy way to publish the part with the rules that belong to it?
I attached the flange file to this post.
Thank you in advance!
@Anonymous
Content center was developed many years ago way before iLogic was introduced. CC Its based on members, values and template definition. So with you changing the configuration of the flange by iLogic, you really can't use that same interface like that in content center. Yes parameters in the CC family could drive the iLogic rule but instead just make a library definition in your project file and store your flange ilogic file there (so others can't make changes to it). Well that's my opinion.
Mark Lancaster
& Autodesk Services MarketPlace Provider
Autodesk Inventor Certified Professional & not an Autodesk Employee
Likes is much appreciated if the information I have shared is helpful to you and/or others
Did this resolve your issue? Please accept it "As a Solution" so others may benefit from it.
@Anonymous
Content center was developed many years ago way before iLogic was introduced. CC Its based on members, values and template definition. So with you changing the configuration of the flange by iLogic, you really can't use that same interface like that in content center. Yes parameters in the CC family could drive the iLogic rule but instead just make a library definition in your project file and store your flange ilogic file there (so others can't make changes to it). Well that's my opinion.
Mark Lancaster
& Autodesk Services MarketPlace Provider
Autodesk Inventor Certified Professional & not an Autodesk Employee
Likes is much appreciated if the information I have shared is helpful to you and/or others
Did this resolve your issue? Please accept it "As a Solution" so others may benefit from it.
Hi! This is an interesting idea. We have heard similar requirements and we are exploring the area. I will need to check with the project team to understand the requirement better. In the meantime, do you mind elaborating the workflow requirement or sharing an example here?
Many thanks!
Hi! This is an interesting idea. We have heard similar requirements and we are exploring the area. I will need to check with the project team to understand the requirement better. In the meantime, do you mind elaborating the workflow requirement or sharing an example here?
Many thanks!
Hi,
I am not sure what you are trying to achieve. Basically:
- if you publish part with iLogic into Content Center then all instances crated from Content Center (command Place from Content Center) will have this iLogic rule and rule will be working
- I publish part with iLogic rule, this rule shows just message box and when I placed for CC, this message box appears, because rule is run on parameter change - which happens during place from CC - parameters from CC family table are applied on the template => CC part (CC instance)
Are you trying to "convert" all you parameters combination to CC family table?
Please explain: I see/understand you publish your flange, you can Place from CC your flange, but not sure what you want to do next. (if you place your flange As Custom then you can open it+modify it = change parameter and iLogic rule runs)
Regards
Jan Priban
Hi,
I am not sure what you are trying to achieve. Basically:
- if you publish part with iLogic into Content Center then all instances crated from Content Center (command Place from Content Center) will have this iLogic rule and rule will be working
- I publish part with iLogic rule, this rule shows just message box and when I placed for CC, this message box appears, because rule is run on parameter change - which happens during place from CC - parameters from CC family table are applied on the template => CC part (CC instance)
Are you trying to "convert" all you parameters combination to CC family table?
Please explain: I see/understand you publish your flange, you can Place from CC your flange, but not sure what you want to do next. (if you place your flange As Custom then you can open it+modify it = change parameter and iLogic rule runs)
Regards
Jan Priban
I think that is what I'm gonna do. Thank you!
I think that is what I'm gonna do. Thank you!
OK,
I will talk to our PD, but I am afraid such functionality converting iLogic rule with many If/ElseIF/EndIf to Content Center family table will not be implemented.
Regards
Jan Priban
OK,
I will talk to our PD, but I am afraid such functionality converting iLogic rule with many If/ElseIF/EndIf to Content Center family table will not be implemented.
Regards
Jan Priban
Hi,
talking to Content Center PD (Poduct Owner who is responsible for current/future functionality) we are not goint to implement such functionality.
Try to develop a parser reading line by line of your iLogic rule (simply said read text file which iLogic is) and transfor it to text file.
J1 T1 V1
13 16 3
19 24 3
Then publish flange into Center Center and modify its family table by Copy/Paste from text file you gnerated by parser
Regards
Jan
Hi,
talking to Content Center PD (Poduct Owner who is responsible for current/future functionality) we are not goint to implement such functionality.
Try to develop a parser reading line by line of your iLogic rule (simply said read text file which iLogic is) and transfor it to text file.
J1 T1 V1
13 16 3
19 24 3
Then publish flange into Center Center and modify its family table by Copy/Paste from text file you gnerated by parser
Regards
Jan
Goodmorning,
Maybe I can do that. I will give it a try.
Thanks for the reply!
Goodmorning,
Maybe I can do that. I will give it a try.
Thanks for the reply!
I know this is older but would like to chime in on the idea...
I use this functionality when I need to suppress a feature on a content center part in order to minimize the about of families. Say I have a RH and LH version of something, I can use a mirror body as the last part feature, then I've been using a user parameter, say, MIRROR_PART with a ul 1/0. Then I set a rule where 1 is that feature is active, 0 its suppressed. Then in my CC table I can just set all parts with either a 0 or 1 in a Mirrored column.
It's very useful as well when I have things where a larger part may have small gussets, but smaller ones don't.
I know this is older but would like to chime in on the idea...
I use this functionality when I need to suppress a feature on a content center part in order to minimize the about of families. Say I have a RH and LH version of something, I can use a mirror body as the last part feature, then I've been using a user parameter, say, MIRROR_PART with a ul 1/0. Then I set a rule where 1 is that feature is active, 0 its suppressed. Then in my CC table I can just set all parts with either a 0 or 1 in a Mirrored column.
It's very useful as well when I have things where a larger part may have small gussets, but smaller ones don't.
Can't find what you're looking for? Ask the community or share your knowledge.