Excel in assembly and parts

[berry.lejeune]

Hello all,

I've made an excel file that I linked in my assembly. This file contains dimensions to create multiple parts.

What I normally do is make first a "sketch part" In this part, all lines and dimension can be found to make all of the parts. I know it's also possible to link the excel file to this "sketch part" but in my main assembly are some rules which link also to this excel file to get items from the library.

If I link both the "sketch part" and the assembly to this excel file and I copy my assembly, then I have to reconnect the assembly and the "sketch part" to a new excel file. In order to minimise the risk of forgetting to relink the assembly and part, is there a way that the parameters in my assembly are pushed through to my "sketch part"?

Here you can see all the parameters from the excel file linked to the assembly. These parameters need to go into the "sketch part"

[Mario.VanWiechen]

I have been wrong many times and I could be here.

I do a lot of my work with a skeleton ( your sketch part ), which can be just sketches or a combination of shapes and sketches.

But the "skeleton " file has to have all the parameters, if the top assembly has the parameters Inventor will give a lot of circular reference errors. my top assemblies get their parameters from the skeleton file. In the parameters for any other part you use "Link" to get parameters from your "sketch part"

Not sure it helps but may be the way to go. 

[johnsonshiue]

Hi! This has to be done using an iLogic rule in the assembly. Essentially, the rule will get the assembly parameter value and then assign it to a part parameter. This is because the part itself isn't aware of the assembly, though it is consumed in the assembly. As a result, the part document cannot obtain the assembly parameter.

Many thanks!

[berry.lejeune]

@Mario.VanWiechen 

First I linked the excel file to the assembly and then I create a new part, my sketch part. And in my part, I tried to link it my assembly but it gives the fault of cyclic dependency.

Then I tried the other way. Linking the excel to my part and then linking my part to the assembly. This works, but it won't help me alot I think. Because in my assembly I've got some rules which look at the excel file to get stuff from the library.

Or I need to figure out a way that the rules in the assembly look at the excel file in the part. But as I'm no expert in writing iLogic's I think the best way of work is to replace the linked excel file in the assembly and the part everytime I do a copy of the assembly when I start a new project

[CGBenner]

@berry.lejeune 

Hello, did you ever get this solved?  Did the answer given by @johnsonshiue at least explain why it isn't working right now?  Maybe you can post a question in the iLogic forum for additional help on a new rule.