NX5: Wanting to better understand part versioning

[DET100]

I have done just a little with part versioning in NX 5 but do not understand all of the parts.

A. The part numbers I would like to have:
1234567.prt
1234567_3d.prt

B. Current setup--Does this look correct?
Full Part File Name Format
([0-9]{7,7})([a-z]{1,2})([0-9]{1,2})((_3d)|)

Version Independent Section of the Part
File Name \1\4

Part File Name Match
\1([a-z]{1,2}[0-9]{1,2})\4

Version Section of Part File Name Match \1

C. Can you help me understand what ()[] means and how to separate each of the sections?

D. I've read over the NX documentation and it does not seem totally clear.

 

[uwam2ie]

maybe this blog helps.

http://nxway.blogspot.com/

 

[looslib]

Give us a sample list of your part number revisions sequence.
1234567.prt
1234567-B.prt
1234567-C.prt

This is what we have and I tried to make this work but versioning won't pick it up.

If I did 1234567-A.prt as my starting point, then it works.


The () designates groupings.
The | is an OR function.
The [] designates repeated characters.

I copid a bunch of files to a dummy folder and use a custom ugii_env.bat and ug_english file for testing when on NX2. We just went to NX4, so I have to start over because corporate now has us on a network shared drive loadpoint.

As a last note, search option path order has a big impact on the success of file versioning.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[hudson888]

You haven't really supplied enough to know and even if you did then I think you're better to solve it for yourself because it can take some time. What I'm missing in your post is the Version Type. I advise everyone that I can to use Military because it is the best most flexible and easiest to set up.

In terms of writing the expressions the best way to work is to try different things on a test directory of file names that you can create for testing purposes. So you set up your version rules first and then restart NX. Then you go into load options and set your search folders to the single folder where you have saved a collection of known valid and invalid file names. Then you can turn on load latest and hit the verify folders tick to receive a report on whether your version expressions are working as you would expect. Using this method, what Ben has mentioned above, and the Documentation examples you ought to be able to iterate towards something that works.

When you think you have a solution then change your search folders back to your working directories and run a "verify folders" check over the lot to check for unintended consequences based on the odd file names that you may not have realised existed etc.

The only other thing that I can tell you by way of recommendation is that any system which by dent of forethought contains the flexibility to maintain the model releases separately from the drawing releases will be vastly easier to maintain for everyone involved. Many people's first instinct is to the opposite I know, but when you think on it then it can be seen that it is both inflexible and not automatically maintained for you unless you go to something like Teamcenter. The problem to get your head around then is how otherwise do you deal with human errors that will inevitably creep in or operate on a needs be basis so that the system works for you and not you for it.

Best Regards

Hudson

www.jamb.com.au

Nil Desperandum illegitimi non carborundum

 

[DET100]

Thank you very much for the feedback. I will review the comments and try a couple of the suggestions and try to respond later today.