part file name rules

[bxbzq]

Hi,

I'm using native NX8.5. If I want the master part file name to be:
PartNumber.Description.Version.prt. For example, 234567.SUPPORT WELDMENT.006.prt

and drawing part file name to be:
PartNumber.Description.DWGxx.Version.prt, eg. 234567.SUPPORT WELDMENT.DWG01.006.prt

How do I set up Custom Defaults->Assemblies->Site Standards->Part Name Versions?

Thanks.

 

[bxbzq]

And, which part is $PART_NAME_CORE, $PART_NAME?
I would like part number, part name and version to show up in the title block and parts list automatically.

Thanks in advance.

 

[bxbzq]

Somebody please help.

 

[looslib]

Look in the online Help for examples of setting up the versioning rules. They are unigue for each company. They are based in Regular Expression terminology.

I would not put part description in a file name as it complicates the substitution searching.

The variable names for versioning have changed since I set mine up at V10, almost 20 years ago.

$Part_Name defines how the part name is built
([0-9]+\\.)([0-9][0-9][0-9])
This would define a multiple numeric character string for the base part number: [0-9]+
This defines a 3 digit numeric revision: [0-9][0-9][0-9]

For part versioning to work, you then define what portion is static, in this case the Part_Name portion and it is marked as part 1 of the naming string: \\1

Now you define the match portion for searching which is the base part number and then the substitute porion: \\1([0-9][0-9][0-9])

Finally you define which portion is to not change: \\1

You can make longer rules and use alpha characters but it complicates the searching Also when searching multiple folders, if you are native filing, not TeamCenter, the first match is the ONLY folder the substition will be applied to. You cannot move released files to a released folder and have WIP in another folder and have part versioning work properly.

I also believe that there is (or was) a method of using the file open load option rules to check and see what files in your system will be found with your versioning rules. I haven't done this since NX4 in 2009.

Below is the versioning rule section from what we did at a prior company with V10 and used for the whole 11 years I worked there. Once you set up versioning rules, you do NOT want to change the file naming criteria in your company.

! The following rules are used to describe the part names the system will use
! when searching for the version of a part for an assembly. The syntax for the
! rules follows the Regular Expressions used by the UNIX system. Leaving the
! rules blank means the system does not recognize versions of files and will
! compare complete part names when searching for parts.
! Examples follow.
!
!
! This pattern specifies the general format of versioned part names.
!
Assemblies_PartNameFormat: ([0-9]+\\.)([0-9][0-9]|([0-9][0-9sm]|([a-e]\\.[0-9][0-9sm])))


! This value decides which portion of the Assemblies_PartNameFormat rule is the
! version independent portion of the name. It consists of 2 back-slashes "\\"
! followed by the number of the section.
!
Assemblies_PartNameSubstitution: \\1


! This value is used to match all versions of a part in a directory.
! It consists of the Assemblies_PartNameSubstitution rule specifying the
! version independent portion of the name along with the section of the
! Assemblies_PartNameFormat rule specifying the pattern for the part version.
!
Assemblies_PartNameMatch: \\1([0-9][0-9]|([0-9][0-9sm]|([a-e]\\.[0-9][0-9sm])))


! This value decides which portion of the Assemblies_PartNameMatch rule
! is the version portion of the name.
!
Assemblies_VersionSubstitution: \\1


! This value decides the sorting order that will be used to determine the latest
! version of a file if several exist.
! Note: A valid option must be specified even if file versioning is not being used.
!
! Valid options are: [MILITARY,NUMERIC,REVERSE_NUMERIC,ALPHABETIC,REVERSE_ALPHBETIC,
! ALPHANUMERIC]
!
! where: MILITARY : 1 < 1.2 < 3.2.1
! NUMERIC : 2 < 5 < 11
! REVERSE_NUMERIC : 15 < 7 < 2
! ALPHABETIC : a < m < z < av < ff
! REVERSE_ALPHABETIC : z < a < vv < aa
! ALPHANUMERIC : a2 < a5 < b2 < b23 < aa12 < bc22
!
Assemblies_VersionType: NUMERIC

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

Ben Loosli