When using ugmanager_clone and specifying a log file, the command exports older revisions having explicitly defined newer revisions in the log file.
Solution
The ugmanager_clone command reads parts in the order they are listed in the log file (from top to bottom). Therefore, if you specify an assembly prior to the components, the components are already loaded as the result of the assembly being loaded. Similar to how an NX session behaves, you cannot open multiple versions of the same part. Therefore, if your assembly contains plate/A and you want to export plate/B, by listing your assembly higher in the log than the component it loads plate/A and will ignore the plate/B entry.
There are three possible solutions:
- Prior to executing the command, set TC_config_rule_name in the NX command window to a suitable revision rule to load the desired revisions
- Reorder the components in the log file so that they are higher up in the list and read before their parent assemblies
- Enable Multiple Revisions in the Customer Defaults. This results in multiple revisions of the component being exported
Notes and References
Hardware/Software Configuration
Platform: INTL64
OS: window
OS Version: 764SP1
Product: NX
Application: NXMANAGER
Version: V1847
Function: CLONE_EXPORT
Ref: 002-7008381