cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

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

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

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.)

20 Comments
MikkoHinkkanen
13-Aquamarine
This enhancement is urgently needed.
Laukkala
3-Visitor

A needed echancement!

JHall
16-Pearl

Enhancement needed also when using third party CAD systems. 

lhoogeveen
17-Peridot

I'm surprised PTC hasn't acknowledged this yet. It's received a lot of votes and shouldn't be that hard to implement. We would definitely take a closer look at using Autonumbering for Creo if it had these changes.

StephenW
23-Emerald I

PTC has never figured out how to deal with Product Ideas. Over the years since the enhancement request moved from tech support to the community (which I think was a good move), there have been mutliple attempts by PTC to make a process in which Ideas were reviewed and processed internally. Nothing seems to have taken root. 

BenLoosli
23-Emerald I

Very few enhancement requests results in a new sale to PTC. The sales demo guys know what areas to de-emphasize during demos to avoid the weak spots in the code. They want to show how easy the software is to use and dazzle the prospect with color displays and charts.

It would take a very technical person to write a requirements document for PTC to demo against that showed any of these types of weaknesses in their product offerings.

ArnaudVandeVeer
14-Alexandrite
Status changed to: Acknowledged

It has been added to the roadmap.

bmr
17-Peridot
17-Peridot

@ArnaudVandeVeer can you please provide some more information? Is that on the roadmap for 12.0.1 or 12.1 or "13" ?

Thanks

ArnaudVandeVeer
14-Alexandrite

This has been added to the Creo roadmap and is currently under review, but I cannot yet commit to any release.

Kalle
9-Granite

Anyone know if there are any updates to this topic. Is changes planned/committed to any release yet?

bmr
17-Peridot
17-Peridot

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

ArnaudVandeVeer
14-Alexandrite

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.

TomU
23-Emerald III

@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?

nvelpanur
13-Aquamarine

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

lhoogeveen
17-Peridot

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

jrichards-2
3-Visitor

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.

RobertH
12-Amethyst

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.

BenLoosli
23-Emerald I

The numbering schema can be changed in the OIR.

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

RobertH
12-Amethyst

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

rmueller
3-Visitor

A needed enhancement, not only to fix the inconsistency!