Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations cowski on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!
Load Latest Rules and Syntax
- Thread starter FXjohn
- Start date
JohnRBaker
Mechanical
In the user documentation, try:
Common Tools -> File -> File Options -> Assembly Load Options. You will probably have to review the content of several of the documents found at this location to get a complete picture of how this works and how the rules are applied.
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA
To an Engineer, the glass is twice as big as it needs to be.
Common Tools -> File -> File Options -> Assembly Load Options. You will probably have to review the content of several of the documents found at this location to get a complete picture of how this works and how the rules are applied.
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA
To an Engineer, the glass is twice as big as it needs to be.
- Thread starter
- #3
If you are just starting out to set this up then you may not have made any final decision about how you name the files yet. If you already have all your files named as such then the answer is different.
What the variant rule does is look for a delimiter to separate the core file name from the revision.
In your case you could use the underscore "_" and code to use that as a delimiter. However you have two of those separated by the would "Rev". So if you're just setting up you naming standard I would dump the word "Rev" and just call it "4010-13_A.prt". This will save on typing and eliminate differences between "Rev", "REV" and "rev" which aren't necessarily the same thing in file naming syntax.
I would be so keen to get rid of that Rev that I'd clone the assemblies in necessary to remove it.
If however you're forced to stick with it then use the whole thing as your delimiter coding for "_REV_" should separate the core file name "4010-13" from the revision letter "A" or "B".
Lastly again if you're starting out then why not use the Military versioning method, "4010-13.1.prt" works as does "4010-13.1.1.1.prt" you can concoct as system whereby you have full releases, milestone releases, and versions that users increment rather than allowing them to overwrite each others work. It is the best and most flexible option. You don't have to have a high level of complexity but you can choose to use it if you need to.
When you get it to work set up your directories simply and not too deeply nested. If you search a deeply branching directory structure you find that an earlier version in a higher directory often gets preference over a later one buried further down the directory tree. This is just a limitation of how versioning rules work that depends on you controlling your work flow sensibly. We have worked with it for some time with few problems in this regard because we understand and work with the system.
Cheers
Hudson
What the variant rule does is look for a delimiter to separate the core file name from the revision.
In your case you could use the underscore "_" and code to use that as a delimiter. However you have two of those separated by the would "Rev". So if you're just setting up you naming standard I would dump the word "Rev" and just call it "4010-13_A.prt". This will save on typing and eliminate differences between "Rev", "REV" and "rev" which aren't necessarily the same thing in file naming syntax.
I would be so keen to get rid of that Rev that I'd clone the assemblies in necessary to remove it.
If however you're forced to stick with it then use the whole thing as your delimiter coding for "_REV_" should separate the core file name "4010-13" from the revision letter "A" or "B".
Lastly again if you're starting out then why not use the Military versioning method, "4010-13.1.prt" works as does "4010-13.1.1.1.prt" you can concoct as system whereby you have full releases, milestone releases, and versions that users increment rather than allowing them to overwrite each others work. It is the best and most flexible option. You don't have to have a high level of complexity but you can choose to use it if you need to.
When you get it to work set up your directories simply and not too deeply nested. If you search a deeply branching directory structure you find that an earlier version in a higher directory often gets preference over a later one buried further down the directory tree. This is just a limitation of how versioning rules work that depends on you controlling your work flow sensibly. We have worked with it for some time with few problems in this regard because we understand and work with the system.
Cheers
Hudson
- Thread starter
- #5
DavidTolsma
Mechanical
Regular expressions. A very simple implementation of the Regular expressions syntax.
([0-9]{4}-[0-9]{2}_REV_)([a-zA-Z]{1,2})
\1
\1([a-zA-Z]{1,2})
\2
This is close to what you want, I didn't put it into NX to try. Once you have enabled the site standards, you can do a test from within NX to see which matches. This check location is dependent on what version of NX you are running.
-Dave Tolsma
Tolsnet LLC
([0-9]{4}-[0-9]{2}_REV_)([a-zA-Z]{1,2})
\1
\1([a-zA-Z]{1,2})
\2
This is close to what you want, I didn't put it into NX to try. Once you have enabled the site standards, you can do a test from within NX to see which matches. This check location is dependent on what version of NX you are running.
-Dave Tolsma
Tolsnet LLC
- Status
Similar threads
- Locked
- Helpful tip
