Skip to main content
P
ptc-59266171-Visitor
1-Visitor
January 13, 2015
Question

A SERIOUS BUG OF AFX3 ABOUT SORTING

  • January 13, 2015
  • 1 reply
  • 1811 views

hello,

when we are building 3d about afx3,

fist,we set project name=NF1200,so create some profiles ,such as nf1200-1,nf1200-2,nf1200-3,and so on,

now we should be delete nf1200-2, sure, we are used to use the command"erase not displayed",and then

we should create a new part, the name of this new part is "nf1200-4".This sorting is wrong.

if we use the command"erase not displayed",the name of new part should be "nf1200-2",in afx2,the name of new part is right.

can sombody help me?

    1 reply

    S
    StefanBachschus1-Visitor
    1-Visitor
    January 14, 2015

    Hello

    what you describe is not a bug, but intended behaviour. Most autonumbering mechanisms (including Windchill autonumber) never reuse already given numbers. The reason is simple. Imagine you have checked in your assembly (including old part nf1200-2) in PDM-Link or any other non PTC PDM system, the you check out assembly delete old part nf1200-2, erase it from session and assemble a new part and it will get name nf1200-2. If you then want to check in assembly you will get check in conflicts as part with name nf1200-2 already is in database, but it may be a completely different part ....

    ... anyhow there is a workaround to achieve what you want to get. Usually highest used number is stored in assembly parameter "PROFILE_NUMBER" and from this number on AFX will search for the next unused number. If you create this parameter upfront, set it to 0 and then lock it, AFX no longer can save the higest used number in this parameter and always will start at "0" to look for next free number

    ... but be aware about potential problems when working with and PDM system!!!

    Stefan

    P
    ptc-59266171-VisitorAuthor
    1-Visitor
    January 14, 2015

    Thanks,Stefan

    This problem is barely solved as your method, but this problem isn't produced in afx2 ,so I can't understand

    this sorting.

    if we create the models by stored in memory not in disk ,when we modefy the models, we hope the

    scheme of parts sorting (not in turn)ใ€‚yes, if we delete one part, the sorting should be from this part.

    surly, if we delet the part stored in disk ,when we delete this part, the sorting yet should be from this part.

    We think the resorting in afx2 is very reasonable and right.

    Terms & ConditionsCookie settingsAccessibility statement