When using the Data Migration Utility you can have failures if the assignment of File Format to Item Types have not been made properly. Checking this on the Process Modeler could be a very tough task especially if you have a great number of Type to Format assignments.
download [ -n [ -s script-file ] ] [ -r ] [ -W workset-spec ] [ -D workset-dir ] [ -f rule ] [input-file] Additional information can be found in the Data Migration Utilities manual.
2 Select Configuration Object Management | Upload rules 3 Expand the Dimensions Clients node and select the product to which you are migrating the files, for example QLARIUS.
The second error which you are receiving of: Error: Label SAMPLE:SAMPLE_LABEL_GAP_RE1 & GAP_RE3 _QA (1 revisions), Baseline SAMPLE:SAMPLE_LABEL_GAP_RE1 & GAP_RE3 _QA (0 items) -- mismatch in product SAMPLE is also related to the first and how we do the validations. The mismatch in the product in this case is indicated because we are unable to validate the label and baseline.
2. Select the Item Type from the left pane and change to the Attribute tab. 3. Drill down on the VCS_ARCHIVE_NAME or edit the attribute. 4. Under the Revision section of the Attribute, note the following: Stored per revision, default as specified (this is the default of the Migration utility) Stored per revision, default to previous revision (this will keep the value of which we migrated in) 5. Save the changes. Do this for each Item Type for this Product .
Some fields often cause questions or confusion when mapping Tracker data into TeamTrack when using the data import. For more information on migrating data from Tracker to TeamTrack, also see the Tracker Product News page on the Serena Support web site for other frequently asked questions, as well as a migration demonstration video.
If you are starting a Tracker to TeamTrack migration you will also want to check Tracker Product News page on the Serena support site for other frequently asked questions, as well as an migration demonstration video.
In the Baselines.log.html file, the following error may occur: AIWS "< prod >:< Item Spec>;<Rev>" /WORKSET="< Prod >:<Temp_Workset>" 2384-Error: The specified item revision is not in the project <Prod>:<Workset>
