Skip to main content
Mar 17, 2025 7:29 PM UTC
Acknowledged

Need a mechanism in Creo to 'update' a custom corporate symbol on a drawing to the latest iteration

Related products:Creo Parametric

1. Describe the Problem

Reference:

Ticket: C17727367 

Articles: CS439490 and CS36275

 

There is no method within Creo to simply select a custom symbol and have it 'update' to the latest standard. The issue is that once a symbol is loaded into a drawing, it stores that symbol internally, without a link to allow it to be updated. Once an update to a company standard symbol is deployed, there isn't an easy solution to updating the current ones, or any drawing created from a save-as.


2. Are you using a workaround?
The two articles list a very convoluted workaround. The watered down version, is that the admin needs to make sure the .# extension of the updated symbol is higher than the old one. The user then needs to manually browse to the symbols folder and 'add' the symbol to the drawing. At that point, it will prompt the user to update the other symbols and then the user can select yes and delete the new symbol. This even includes custom bom balloon symbols. The good news is that the code to update symbols is already there. PTC just needs to copy if from the 'add symbol' command, to a new command for 'update symbol'.

3. What is the use case for your organization?
The admin updates a standard custom symbol or BOM balloon. Current drawings and those which will be created via a saved-as could then be updated, as needed.

4. What impact does this problem currently have on your organization?
Some new drawings will lack the functionality of fixes that was built into the updated custom symbols, creating inconsistencies and miscommunication.

7 replies

Mar 18, 2025 12:30 PM UTC

Hi @jwagh 

I wonder if you had the chance to review the "Update Symbol" command in the contextual menu, when applied on symbols?

Here is one small example that I tried, which allows you to update the already placed symbol instances in the drawing, with version 2 of the shock symbol  (which I have updated in a separate Creo session and added a circle next to the symbol):

 

Step 1:

Step1.jpg

Step 2:

Step2.jpg

Step 3: 

Step3.jpg

Step 4:

Step4.jpg

 

Best Regards,

Michael Fridman

Creo Product Manager

 

Community Manager
Mar 18, 2025 12:56 PM UTC
Status changed to: Acknowledged

Thank you @jwagh for your idea. Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.

jwaghAuthor
Mar 18, 2025 1:37 PM UTC

@Mfridman 

Thank you. A few Things. 

  1.  Our main issue is actually stemming from custom BOM balloon symbols, which don't have this option. I did check to see if the command also works for the balloon symbols, and it does. So we might end up adding it to the company admin .ui file. It should probably be included OOTB.jwagh_0-1742304077034.png
  2. The undo command doesn't seem to work after updating symbols. This is important in case the new symbol requires new information from the repeat region table, that might also be too old. The user might want to just keep it 'as-is'.
  3. I did search for "symbol" and initially missed it, because it shows Commands first, then Mapkeys and then Commands not in Ribbon. I just assumed, incorrectly, that mapkeys would be last. Maybe there is room for improvement with reordering.
    jwagh_1-1742304112664.png
  4. The 2 articles should probably be updated, correct? Do you see those articles as out-of-date or incorrect? If so, I can go back to the support engineer.

 

Thanks!

Mar 18, 2025 2:48 PM UTC

Hi @jwagh 

Thank you for your comments, indeed it would be good to have some additional information in the articles to reflect this command and the cases when it can help.

 

If you are planning to reach out to TS, maybe you can also to open a case for the remaining points that you listed, so that R&D can investigate those too.

 

Thanks, Michael

jwaghAuthor
Mar 18, 2025 2:53 PM UTC

@Mfridman , no problem. Do you prefer 3 separate tickets?

Mar 18, 2025 3:03 PM UTC

Hi @jwagh 

As all of the issues are related with the same command, I think that we can start with a single case that includes all the needed descriptions and details.

 

 

Thanks, Michael

jwaghAuthor
Mar 18, 2025 7:22 PM UTC

@Mfridman , ticket 17733281 has been created. Thanks!