topic Re: iPart Part Number do not match document's current values in Inventor Forum

iPart Part Number do not match document's current values

Anonymous — Fri, 13 Jul 2018 17:16:36 GMT

I am fairly new to Inventor and iParts. I created an iPart with an SAE port iFeature. In the Part Number field, I have created a code for the individual configurations. However, I keep getting the prompt that the Part Number value does not match the document's values. For some reason, the SAE Port configuration is defaulting as the document part number. Why is this happening? Is there a way to keep the part number that I created without having to hit 'No' every time?

kelly.young has embedded your image for clarity.

Re: iPart Part Number do not match document's current values

mcgyvr — Fri, 13 Jul 2018 15:02:39 GMT

At some point the part number is being overridden or more specifically differs from the value in the table..

You mentioned some code? ilogic?

Re: iPart Part Number do not match document's current values

Anonymous — Fri, 13 Jul 2018 15:20:16 GMT

By code, I meant the company has specific codes for their configurations and I jut inputted those into the table manually. I have not used any iLogic. Is the override happening because of the iFeature file itself?

Re: iPart Part Number do not match document's current values

johnsonshiue — Fri, 13 Jul 2018 15:48:48 GMT

Hi! I suspect the Part Number in the iPart factory was changed to something different than the one on the author table for the specific member.

If you cannot figure out, please share an example here. There should be a logical reason to the behavior.

Many thanks!

Re: iPart Part Number do not match document's current values

Anonymous — Fri, 13 Jul 2018 16:12:15 GMT

Seems like the iPart part number keeps trying to change to the iFeature part number. Can't figure out how to make it not do that!

Re: iPart Part Number do not match document's current values

johnsonshiue — Fri, 13 Jul 2018 16:33:20 GMT

Hi! I see the issue now. There is indeed another variable trying to drive Part Number. Open Ex.ipt and expand the iFeature node. You will see the iFeature itself is table driven. Edit the iFeature table. You will find "Part Number" is captured on the table.

This means, you have nested tables. So, iFeature table is trying to drive iPart table. This is not a good practice. iPart table should have all the definitions required for each member. Any change outside of the table can cause confusion like this. If I were you, I would open the .ide file and edit the table. Then change the "Part Number" column to "Description or something else which is not controlled by iPart table. After that, you will need to re-insert the iFeature to the iPart since iFeature is not linked to its ide file.

Many thanks!

Re: iPart Part Number do not match document's current values

Anonymous — Fri, 13 Jul 2018 16:57:57 GMT

Thank you so much for your help so far!

Do you mean I will need to create a separate iFeature for each port size and will not be able to edit it from the iPart table? I am still slightly confused on how to fix the issue.

Thanks!

Re: iPart Part Number do not match document's current values

johnsonshiue — Sat, 14 Jul 2018 13:58:06 GMT

Hi! To fix it, you will need to open .ide file and edit the table. Simply rename the "Part Number" column to "Description" or something else. Save the ide file. Then reinsert it to the iPart factory. The old iFeature will have to be deleted.

Many thanks!

Re: iPart Part Number do not match document's current values

Anonymous — Tue, 17 Jul 2018 17:14:28 GMT

Thanks! Took me a little bit to figure out how to change the name. Ended up editing spreadsheet which worked perfectly!