iLogic .....HELP!!!

[Breeze104]

I am trying to convert a standard iPart to an iLogic based part.  The part has some text driven, cells..PatNumber, Description..ect..

But when I try to referance those cells the iLogic code either does nothing or errors out.  Not sure what to do...Need HELP!!

Basicly i have a bunch of flange rings with have several variables theat need to change as the part number changes, sounds simple right??  Well, not for me..LOL

I have rewritten the code so many times...I have gone from hunt and pecking to typing 300 words a min...well maybe not. 

If anyone can give me a better way or examlpe to do what i need to do that would be great.  About 75-80% of all our parts are identical in shape but just get smaller or larger depending on what size portable auger it goes on.

I am attaching the Excel file that has all the info.  I have been trying to get the part to changed based on "PartNumber" but it has text in the value.

[Breeze104]

I am trying to convert a standard iPart to an iLogic based part.  The part has some text driven, cells..PatNumber, Description..ect..

But when I try to referance those cells the iLogic code either does nothing or errors out.  Not sure what to do...Need HELP!!

Basicly i have a bunch of flange rings with have several variables theat need to change as the part number changes, sounds simple right??  Well, not for me..LOL

I have rewritten the code so many times...I have gone from hunt and pecking to typing 300 words a min...well maybe not. 

If anyone can give me a better way or examlpe to do what i need to do that would be great.  About 75-80% of all our parts are identical in shape but just get smaller or larger depending on what size portable auger it goes on.

I am attaching the Excel file that has all the info.  I have been trying to get the part to changed based on "PartNumber" but it has text in the value.

[MjDeck]

Why are you converting the part from an iPart to an iLogic part?
It would probably help if you can post the original iPart and also the latest version with rules.

[Breeze104]

I am converting to iLogic because hopefully the I wont run into the problems I have been having with Vault.  It seems the more iParts and iAssemblies you put into an assembly the harder it is for Vault to deal with updating stuff.

I tried to upload the file but it is over 6MB and it won't upload.  I uploaded it to my BOX.net account instead.

http://www.box.net/shared/1f1rkbpjl8

If you have issues downloading please let me know and we can figure out some other way.

[MjDeck]

It looks like it would require some work to convert this iPart to iLogic.  But once you do it, the part won't behave the same way in an assembly.  It is harder to drive an iLogic part from the assembly level.  For an iPart, there is a dedicated interface to choose a member.  For an iLogic part, you have to create assembly parameters to drive the part.  And each component instance will generally be a separate part.  Unlike iParts, there is are no factories and member files.

 If you have a lot of iParts and iAssemblies, it will take a lot of work to convert them to iLogic.

[Breeze104]

If the embeded file is adding complexity to part, that can be removed cuz I normally don't use embeded objects.  Just trying everything I could think of to help get this part to function.

[Breeze104]

I figured out that i was trying to do to much at one time.  So I have started to break up the code and make multiple rules.  But I having an issue with the first rule.  I cna get the PartNumber to dynamicly update in iProperties but the Description wont.

Please see video:

http://screencast.com/t/COFntvGPN

Here is location to download files: 

http://www.box.net/shared/1f1rkbpjl8

PS

the file you download last time was an old version anyway...I forgot to re-zip the pack'n go folder...Oooopsss.

[MjDeck]

In the Part_Number rule, move the line:

iProperties.Value("Project", "Description") = Description
to the end of the rule.  You might think that line would set up a link between the parameter and the iProperty.  But it doesn't set up a link: it's just a one-time assignment.  Since you're changing the Description parameter in the rule, you have to assign the changed value to the iProperty at the end of the rule.
 Also, since the Description is driven by the Part Number, you might want to make the Description control Read-only on the form.

 About the embedded Excel file question: I would recommend using an embedded file.  It's a bit harder to do, but it makes the part more like an iPart.  Since the Excel data only applies to this part, might as well keep it inside the part.

[Breeze104]

I reworked the part and now parts are updating and other aren't..not sure wht

See video:http://screencast.com/t/en6agr8IQ

File download:http://www.box.net/shared/1f1rkbpjl8