Renaming default occurrence name for already-instantiated content center files

[Anonymous]

Hello

I noticed only after customizing a bunch of content center parts that it's possible to rename the default occurrence name--too late, apparently.

I can't find a field to change it anywhere in the part file properties, but maybe I missed it.

I can change the occurrence within a specific assembly, but this won't change the occurrence name going forward, in others.

Let me know if it's something I missed, or, hopefully not, if it really is uncontrollable at this point for these files.

Thanks

[blandb]

If you are referring to the browser name, then in the family table, choose the column (or add one) that you want to use for the browser name, and in the column properties choose "Member.Display.Name". This will force the placed item to have this browser name. It will also have it if you chose to place it as custom. If placed as custom for whatever reason, and you want to have the file name, you could open the part, slow click the browser name and delete. It will remove the override from the family table and show what you saved the part as.

Hope that helps.

[Anonymous]

That is what I'm talking about, and I know about the ability to change the property in the family table.
But the problem is, when a content center .ipt file has been generated locally in the library, it doesn't seem possible to alter any future instances' occurrence name for that family member.

[blandb]

Did you do a refresh standard content? When you place a version from CC, it will then look local first. So, in the assembly, Manage tab > CC panel > Refresh

[blandb]

You can also go to Tools > Application Options > Content Center Tab > Check the "refresh out of date standard content"

[Anonymous]

No that doesn't work. Refreshing destroys the edits made to the generated components.

[Anonymous]

No that doesn't work. Refreshing destroys the edits made to the generated components.

[blandb]

Refreshing will refresh all locally generated CC items with what is in the family table.

CC will always look to the local versions first. It will not go get the new one unless you tell it to. Are you using vault with this as well? If so, and these files have been checked in you would need to update them as well by checking them out.

Seeing screen shots of what you have and are seeing, or video will help vs. trying to interpret also.

[blandb]

Please see if the attached video helps.

[Anonymous]

I appreciate the help, but unfortunately that won't work in our case.

Our library components have changes made to the components that have been generated already, and refreshing erases all these changes.

It seems like there's no way to change the prototypical occurrence name for any of these components without starting over (and this requires that we get it right the first time).

[blandb]

To better understand, can you share images, or video to see what you are seeing?