Lorenzo77
Guest
Hello everyone, in these days I found myself having to implement the management of the versions in the parts of the assemblies to return the order in mechanics, I want therefore to share with you as I got the result prefixed me since in Italian I did not find much on the internet.
to manage the versions of part I opted for a point followed by a number of one or two digits in the tail to the name (e.g. "the name of the particular".1.prt or "the name of the particular".56.prt)
at the same time I wanted to have the possibility to initially create details without version extension and then start the management with the version number (e.g. 012-13_plastrina_inferiore.prt that once modified becomes 012-13_plastrina_inferiore.1.prt and subsequently 012-13_plastrina_inferiore.2.prt and so on).
In this way, regardless of the version of the file I open, the program automatically uploads the latest version, the same thing happens if I open an un updated axis that contains a part with a newer version.
the configuration I used is as follows:
custom default --> axiemi --> standard site --> versions name partsfull file part name format: ([a-z0-9A-Z\-\_]+)((.([0-9](sing)
independent part file name session: ♪
mating name part file: \1((. ([0-9](sing)
match of session version of the name part file: ♪
version type: numerical
Axial loading options --> part versionMost recent charge (sent)
Axial loading options --> behavior while loadingAllow replacement (sent)
analyzing, the name part format where it should be indicated as a name starts through the expressions that are illustrated in the nx guide in the section "version name part" --> "regular expressions".
in my specific case I created the section "()" describing the name part "([a-z0-9A-Z\-\_]+)" as the sequence of one or more "+" elements taken from a group "[]"of tiny letters "a-z", of numbers "0-9", of capital letters "a-z", of the special character - "\-" and of the special character _ "\_". this section will then be abbreviated as "\1" as it is the first section of the expression.
the second section describes the version in the name part "((. ([0-9]{1,2})" which is nothing but the special character of the point "." followed by 1 or 2 elements "{1,2}" taken by the group "[]" of numbers "0-9" or "|" the version name part can be empty, which means that the version of the part can appear as a point followed by one or two numbers or not exist but the name part will still be considered a version. This other section will then be abbreviated as "\2" as it is the second section of the expression.
with this format the names of the parts should be written without empty spaces within them (e.g. 012-13 lower plate 3.prt will not be considered a version part name while it is correct 012-13_plastrina_inferiore_3.prt).
I hope to have explained myself in a understandable way and not to have created confusion, if someone wants to correct or add to the argument well come.
to manage the versions of part I opted for a point followed by a number of one or two digits in the tail to the name (e.g. "the name of the particular".1.prt or "the name of the particular".56.prt)
at the same time I wanted to have the possibility to initially create details without version extension and then start the management with the version number (e.g. 012-13_plastrina_inferiore.prt that once modified becomes 012-13_plastrina_inferiore.1.prt and subsequently 012-13_plastrina_inferiore.2.prt and so on).
In this way, regardless of the version of the file I open, the program automatically uploads the latest version, the same thing happens if I open an un updated axis that contains a part with a newer version.
the configuration I used is as follows:
custom default --> axiemi --> standard site --> versions name partsfull file part name format: ([a-z0-9A-Z\-\_]+)((.([0-9](sing)
independent part file name session: ♪
mating name part file: \1((. ([0-9](sing)
match of session version of the name part file: ♪
version type: numerical
Axial loading options --> part versionMost recent charge (sent)
Axial loading options --> behavior while loadingAllow replacement (sent)
analyzing, the name part format where it should be indicated as a name starts through the expressions that are illustrated in the nx guide in the section "version name part" --> "regular expressions".
in my specific case I created the section "()" describing the name part "([a-z0-9A-Z\-\_]+)" as the sequence of one or more "+" elements taken from a group "[]"of tiny letters "a-z", of numbers "0-9", of capital letters "a-z", of the special character - "\-" and of the special character _ "\_". this section will then be abbreviated as "\1" as it is the first section of the expression.
the second section describes the version in the name part "((. ([0-9]{1,2})" which is nothing but the special character of the point "." followed by 1 or 2 elements "{1,2}" taken by the group "[]" of numbers "0-9" or "|" the version name part can be empty, which means that the version of the part can appear as a point followed by one or two numbers or not exist but the name part will still be considered a version. This other section will then be abbreviated as "\2" as it is the second section of the expression.
with this format the names of the parts should be written without empty spaces within them (e.g. 012-13 lower plate 3.prt will not be considered a version part name while it is correct 012-13_plastrina_inferiore_3.prt).
I hope to have explained myself in a understandable way and not to have created confusion, if someone wants to correct or add to the argument well come.