Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
I've saved one Hex Nut Metric part to custom part and made it an ipart, then publish it to content center. When I try to edit this family table, I find Filename is not in the ipropertity column list, and get the error message "non-unique filename(s) found in members, Please make sure filenames are unique for every member". Can anyone tell me how to fix this problem? Thanks.
I tried your workflow using Hex Nut Metric in R2008SP1,but Filename column is in ipropertity column list and I do not see error message when edit family table.Could you please attach your ipart?
To fix the problem and proceed with table edit,please edit the filename colum in column properties dialog using expression to make sure the file names are unique.You may set the file name={member} as expression.
Hi, Huan. Thank you for your reply.
We use Inventor 11 sp2. And I"ve tried to set the file name={member}, it still does not work.
Is there a problem with the Content Center in Inv 11? Because when I use "copy to" to make our own library, everything is fine except Heavy Hex Nut Metric and Hex Nut Metric.
Thanks,
Amy
I can reproduce the problem in R11 SP3 using your part.And it is OK in R2008 SP1.
It seems only two parts are impacted?I tried many of my iparts,all is OK.I also tried to find a workaround for you,but failed.Have you ever tried to re-create the ipart?I am sorry for inconvenience.
Thanks, Huan.
We will upgrade our Inventor to R2008 in near future. Hopefully no more this kind problem happen again in R2008.
I created the "brand-new" ipart and then published to our own library, it's working fine.
Thank you again for your response.