Skip to main content
May 14, 2019 1:44 AM UTC
Acknowledged

Autonumbering in Creo Parametric - Don't Consume Number Unless Needed

Related products:Creo Parametric

Autonumbering in Creo Parametric is not consistently implemented.  In some places Creo displays <auto generated name> and doesn't consume a number from Windchill until the action is completed.  In other places Creo consumes a number immediately, as soon as the related dialog is opened, before any actions have been completed.  (Just opening the dialog and closing it will consume a number.)  Please change this so <auto generated> is displayed everywhere and no number is consumed from the database until it's actually needed (the action is completed.)

 

Good:

Everything works exactly as desired when creating a brand new file in Creo.  No number is pulled from the database until the object has actually been created.

Creo New File.png

 

Bad:

This falls apart everywhere else.  All of these other actions will pull a number from the database as soon as the dialog is opened:

  • Save As from Creo
  • Assembly - Create New Object
  • Assembly - Replace (even though "Unrelated Component" is not selected)
  • Rename from the embedded browser in Creo

Creo Save As2.png

Creo Assembly - Create New File.png

Creo Assembly - Replace File.png

 

Wasting a number every time one of these other actions is taken is making the whole thing unusable (at least for us.)  Yes, it functions, but it's not acceptable to "waste" 80% of the available numbers.

 

Note:  There was a previous product idea but it was 'Archived' due to its age.  Unfortunately this problem still exists so this idea was created to replace it (and at the direction of the Community management.)

29 replies

Jun 2, 2021 4:34 AM UTC

@ArnaudVandeVeer can you share half a year later any roadmaps info?

Jun 2, 2021 1:52 PM UTC

We didn't manage to get it into Creo 9.0, but we're still interested and have it on the short term road map.

TomUAuthor
Nov 4, 2021 12:00 AM UTC

@ArnaudVandeVeer 

 


We didn't manage to get it into Creo 9.0, but we're still interested and have it on the short term road map.

'Short term' as in 9.0.1.0, or 10.0 and beyond?

Nov 5, 2021 2:10 PM UTC

Hi Tom,


As Arnaud mentioned, it didn't make it to the 9.0 stream, but is still being considered in the next couple of releases. I'll update when I have more information.

 

Thanks,

Nihal

Feb 23, 2022 2:40 PM UTC

Please also include the Assembly Save a Copy Menu when fixing this - see image below.

 

Also, please add some intelligence to keep related file names related when using autonumbering. Currently, users have to do a lot of manual fixing to keep file names related.

  • Skeletons that started with a related file name with _SKEL added related get unrelated numbers without _SKEL - see image below.
  • If an ASM and PRT started with the same File Name, they end up with different unique numbers.
  • Side note: Windchill Save As / Rename also has similar problems.

lhoogeveen_0-1645625569067.png

Feb 25, 2022 3:52 AM UTC

Agreed with all the above comments.  Our company is just investigating the implementation of auto generated Name (ugh! why is this not Number or ID, Name is the wrong word), and I have reservations that the arbitrary nature of generation will wreak havoc on our business systems.

Apr 6, 2022 3:36 PM UTC

Also running out of numbers will be an serious issue because in a lot of situations (examples above) the number is raised but not used.

Apr 6, 2022 3:55 PM UTC

The numbering schema can be changed in the OIR.

You can add a prefix to your numbers, define the length of the number, etc.

Apr 7, 2022 6:53 AM UTC

I know, but after 2 years having this auto number, there are more unused than used numbers.

Jul 4, 2022 12:32 PM UTC

A needed enhancement, not only to fix the inconsistency!