Content Center Family Table Annoyance

Content Center Family Table Annoyance

jimm.motyka
Enthusiast Enthusiast
1,493 Views
15 Replies
Message 1 of 16

Content Center Family Table Annoyance

jimm.motyka
Enthusiast
Enthusiast

jmotyka2QEPQ_0-1663012313803.png

I'm using the Autodesk supplied family table (Content Center) and only adding a column for the Stock Number.  Yet, when I attempt to save the file, it displays the dialog box shown.  So many whys here.  If the Autodesk crew can get to save, and all I'm doing is adding one additional column, why would (should) I even see this error.

 

That said, what would be the quickest and least painful way to rectify this dialog error?

0 Likes
Accepted solutions (1)
1,494 Views
15 Replies
Replies (15)
Message 2 of 16

Frederick_Law
Mentor
Mentor

You have duplicate field in the table.

Check the table.

Probably changed something by mistake.

Message 3 of 16

jimm.motyka
Enthusiast
Enthusiast

I was using the family table "as is", just adding one more column for the Stock Number.  Hence, why I termed it annoying, because nothing else was updated or changed in the other fields.

0 Likes
Message 4 of 16

jimm.motyka
Enthusiast
Enthusiast

Maybe this will help clarify things better.  If I suppress part rows in the current table, as supplied by Autodesk, and try to save the changes, the same error dialog pops up.  I just want to know how they made it happen and I cannot.

0 Likes
Message 5 of 16

Frederick_Law
Mentor
Mentor

Whatever you've added created a duplicated field somewhere.

Can't tell you which one cause I can't see your table.

0 Likes
Message 6 of 16

pcrawley
Advisor
Advisor

That can be a misleading error depending on the table you are editing.  Non-unique file name errors are a problem for "standard" content - like nuts and bolts - where Content Center decides where to save the part files and can't have duplicate file names in a folder. 

 

For other content like structural shapes - they are always placed using the "custom" setting.  File names/locations are the responsibility of the user.

 

Which component are you editing, and which version of Inventor?  Maybe someone here will try and replicate the problem to see if it is a defect, or something you can ignore.

Peter
0 Likes
Message 7 of 16

jimm.motyka
Enthusiast
Enthusiast

Hopefully this helps explain the situation.

  1. I created a read/write CC library.
  2. Under Fasteners > Bolts > Hex Head > selected Heavy Hex Bolt - Inch.
  3. RMC (right mouse click) and created a "Save Copy As" and retained the link.
  4. Saved the file to the read/write library.
  5. Selected the Save As Copy version.
  6. RMC on it and selected Family Table.
  7. Selected UNF fasteners and suppressed those.
  8. When selecting Apply (button), that's when the dialog box error pops up.
  9. Have to Cancel, due to inability to suppress fasteners.

So, what I really am looking for is to suppress the UNF fasteners and add the Stock Number column to the read/write library.

 

Let me know if this is clear enough to replicate.

 

Thank you!

0 Likes
Message 8 of 16

Frederick_Law
Mentor
Mentor

Get a screen shot:

CC-Edit-02.jpg

This is a copy of ANSI Channel modified to CSA to show size in metric.

I've also copy and made A325 bolts.

0 Likes
Message 9 of 16

jimm.motyka
Enthusiast
Enthusiast

jmotyka2QEPQ_0-1663073812888.png

 

0 Likes
Message 10 of 16

blandb
Mentor
Mentor

I do kind of remember that in the Default Hex Head Cap Screw family, down in the 1" unc area there was some lines that would be the same output. Never knew how ADSK was able to make that happen without errors, but they did. I never had to deal with it once we copied because we never used fasteners that large so I was able to just delete the lines. But that has been a while ago, not sure if it has been fixed in default libraries as of yet.

Autodesk Certified Professional
0 Likes
Message 11 of 16

CGBenner
Community Manager
Community Manager

@jimm.motyka 

 

Your workflow description was perfect for being able to reproduce this.  Thank you.

I can only guess that as these were created, Autodesk used some magic override to be able to save and bypass the error.  I'm still looking at the table to see if I can find the line or variable that is causing the problem.  If I find it I'll update the thread.  Meanwhile, I'll tag in @johnsonshiue in case he knows something we do not.

Did you find a post helpful? Then feel free to give likes to these posts!
Did your question get successfully answered? Then just click on the 'Accept solution' button.  Thanks and Enjoy!



Chris Benner

Community Manager - NAMER / D&M


0 Likes
Message 12 of 16

Frederick_Law
Mentor
Mentor

CC-Edit-03.jpg

0 Likes
Message 13 of 16

Frederick_Law
Mentor
Mentor

Delete duplicated one that don't have "UNC" in Part Number.

Actually you might want to "combine" them to one.

One designation use decimal, one use fraction and different grip length.

0 Likes
Message 14 of 16

CGBenner
Community Manager
Community Manager
Accepted solution

@jimm.motyka 

 

Looks like @blandb is right.  For some reason even though these two lines have some different information (one does not include the UNC), the rest of the columns that are part of the File Name expression are identical and cause duplicate File Names... and the error.  This must have been ignored somehow when the table was created, but editing it brings it forward.  As @blandb suggested, since these are essentially the same bolt, I would just delete the extra row.  It appears to only be in the 1" sizes.

CGBenner_0-1663076038646.png

 

Did you find a post helpful? Then feel free to give likes to these posts!
Did your question get successfully answered? Then just click on the 'Accept solution' button.  Thanks and Enjoy!



Chris Benner

Community Manager - NAMER / D&M


0 Likes
Message 15 of 16

jimm.motyka
Enthusiast
Enthusiast

Son of a pup! How did they get it to save is the bigger question.

 

I'll try this out and post my results.

 

Thank you to everyone who helped me out on this.

Message 16 of 16

jimm.motyka
Enthusiast
Enthusiast

That did it!  It will nag me that it was able to happen from the supplied family table, yet I'm happy for the solution. 😏

0 Likes