<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic A SERIOUS BUG OF AFX3  ABOUT SORTING in Discussions</title>
    <link>https://www.ptcusercommunity.com/t5/Discussions/A-SERIOUS-BUG-OF-AFX3-ABOUT-SORTING/m-p/174465#M67</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hello,&lt;/P&gt;&lt;P&gt;when we are building 3d about afx3,&lt;/P&gt;&lt;P&gt;fist,we set project name=NF1200,so create some profiles ,such as nf1200-1,nf1200-2,nf1200-3,and so on,&lt;/P&gt;&lt;P&gt;now we should be delete nf1200-2, sure, we are used to use the command"erase not displayed",and then&lt;/P&gt;&lt;P&gt;we should create a new part, the name of this new part is "nf1200-4".This sorting is wrong.&lt;/P&gt;&lt;P&gt;if we use the command"erase not displayed",&lt;SPAN style="font-size: 10pt;"&gt;the name of new part should be "nf1200-2",in afx2,the name of new part is right.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;can sombody help me?&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 13 Jan 2015 15:30:37 GMT</pubDate>
    <dc:creator>ptc-5926617</dc:creator>
    <dc:date>2015-01-13T15:30:37Z</dc:date>
    <item>
      <title>A SERIOUS BUG OF AFX3  ABOUT SORTING</title>
      <link>https://www.ptcusercommunity.com/t5/Discussions/A-SERIOUS-BUG-OF-AFX3-ABOUT-SORTING/m-p/174465#M67</link>
      <description>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 thenwe should create a new part,</description>
      <pubDate>Tue, 13 Jan 2015 15:30:37 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Discussions/A-SERIOUS-BUG-OF-AFX3-ABOUT-SORTING/m-p/174465#M67</guid>
      <dc:creator>ptc-5926617</dc:creator>
      <dc:date>2015-01-13T15:30:37Z</dc:date>
    </item>
    <item>
      <title>Re: A SERIOUS BUG OF AFX3  ABOUT SORTING</title>
      <link>https://www.ptcusercommunity.com/t5/Discussions/A-SERIOUS-BUG-OF-AFX3-ABOUT-SORTING/m-p/174466#M68</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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 ....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;... 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&lt;/P&gt;&lt;P&gt;... but be aware about potential problems when working with and PDM system!!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Stefan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jan 2015 06:34:39 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Discussions/A-SERIOUS-BUG-OF-AFX3-ABOUT-SORTING/m-p/174466#M68</guid>
      <dc:creator>StefanBachschus</dc:creator>
      <dc:date>2015-01-14T06:34:39Z</dc:date>
    </item>
    <item>
      <title>Re: A SERIOUS BUG OF AFX3  ABOUT SORTING</title>
      <link>https://www.ptcusercommunity.com/t5/Discussions/A-SERIOUS-BUG-OF-AFX3-ABOUT-SORTING/m-p/174467#M69</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 12px; background-color: #ffffff;"&gt;Thanks,Stefan&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 12px; background-color: #ffffff;"&gt;This problem is barely solved as your method, but this problem isn't produced in afx2 ,so I can't understand &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 12px; background-color: #ffffff;"&gt;this sorting.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 12px; background-color: #ffffff;"&gt; if we create the models by stored in memory not in disk ,when we modefy the models, we hope the&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 12px; background-color: #ffffff;"&gt;scheme of parts sorting (not in turn)。yes, if we delete one part, the sorting should be from this part.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 12px; background-color: #ffffff;"&gt;surly, if we delet the part stored in disk ,when we delete this part, the sorting yet should be from this part.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial; font-size: 12px; background-color: #ffffff;"&gt;We think the resorting in afx2 is very &lt;SPAN style="color: #444444; font-family: 'YaHei UI'; font-size: 14px; background-color: #ffffff;"&gt;reasonable&lt;/SPAN&gt; and right.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jan 2015 14:30:24 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Discussions/A-SERIOUS-BUG-OF-AFX3-ABOUT-SORTING/m-p/174467#M69</guid>
      <dc:creator>ptc-5926617</dc:creator>
      <dc:date>2015-01-14T14:30:24Z</dc:date>
    </item>
  </channel>
</rss>

