You can add multiple documents and folders to Solid Edge SP using Add to Solid Edge SP. The documents that you select to add to the managed library are called direct documents. These direct documents may contain links to other documents or reference other documents, which are known as indirect documents. For example, when you add an assembly to a managed library, all the parts and subassemblies within the selected assembly are indirect documents, if you select only the assembly document to add to the library. Similarly, a part copy within a part document or a part referenced within a drawing document are also indirect documents.
You can import multiple unmanaged Solid Edge files into a SharePoint database without starting the Solid Edge application using Add to Solid Edge SP. Before running Add to Solid Edge SP, ensure that you are able to successfully create and save Solid Edge files. Then prepare your unmanaged files for the managed environment using the tips found in Preparing unmanaged documents for SharePoint.
The Add to Solid Edge SP program is made available to you when you install the Solid Edge Solid Edge SP Client. To run the application, from the Start menu, choose Programs→ Solid Edge ST6→Data Preparation→Add to Solid Edge SP. When you run the program, the Add to Solid Edge SP dialog box provides options for loading your files into the SharePoint database. Whether you are casually adding a few documents or folders, or performing a bulk import of a massive amount of data, you should start with a dry run to analyze your data and report any problems. The dry run gives you the opportunity to correct any problems found before continuing.
One of the options on the Add to Solid Edge SP dialog box is to perform a dry run of adding your unmanaged documents to SharePoint. The dry run builds a list of your files and performs a series of checks including a search for broken links, validation of file name length, and a check for duplicate file names. In the event duplicate document numbers are discovered, the dry run erases the document number of one of the parts in preparation for adding the documents to the managed environment. Log files are generated that contain errors or warnings occurring during the dry run. Any files with broken links are written to a log file and you are informed that broken links were found. You are then given the opportunity to open the log file and suspend Add to Solid Edge SP so you can repair the links, find alternate files of the same file name but that occur in different folders, or ignore the broken links. If you choose to find alternates, the links are not updated to point to the new file, but you are assisted with finding possible replacements in order to expedite fixing the broken links.
Caution:
If you choose to skip the dry run, the list of documents is built from your input, but broken links are ignored by further processing.
When you run Add to Solid Edge SP, log files are generated that contain errors or warnings occurring during the file upload transaction. The default location for log files is determined on the File Locations page of the Solid Edge Options dialog box.
You can use log files to monitor the success or failure of your documents loading into the SharePoint database. The log files you will interact with most often are grouped in the subfolder \Add to InsightXT that is created when you run Add to Solid Edge SP. Each file uses a naming convention consisting of a description, timestamp, and file extension. For example, AddToInsightXT_20120514131232.log. The timestamp is a 14 digit unique identifier using the format YYYYMMDDHHmmss where:
YYYY is the year. In the example, 2012.
MM is the month. In the example, 05 is May.
DD is the day. In the example, 14 is the 14th.
HH is the hour using a 24-hour clock beginning at midnight which is 00 and going through 23, which is 11:00pm. In the example, 13 is 1:00pm.
mm is the minute. In the example, 12 is 12 minutes past the hour.
ss is the seconds. In the example, 32 is 32 seconds past the minute.
|
Log File |
Description |
|
AddToInsightXT_<timestamp>.log |
Contains all Add to Solid Edge SP settings. The setting names are not localized for this development log file. |
|
ATIXTHistory_<timestamp>.xml |
Contains information regarding the blocks of data being added to the SharePoint database, the number of links within the block, and how long each block took to load. The history is only reset and cleared if you start a new Add to Solid Edge SP process. |
|
InsightXT User Log <unique id>.xml |
Contains a summary of actions taken by the Add to Solid Edge SP process to correct the data and load it into the database. These actions are logged as warnings with messages specific to why the corrective action was taken. If a file fails to load, an error is shown in the summary log with a message explaining why the file failed to load. The contents of this log file displays in the Summary dialog box when you are importing files using Add to Solid Edge SP. |
|
InsightXTLog_<timestamp>.xml |
Developer log that includes a timer so the total time for input is measured accurately. |
When you run Add to Solid Edge SP, files are generated as output of the process. All output files created from one input list have the same timestamp so it is easy to identify which output file is related to another. The default location for output files is determined on the File Locations page of the Solid Edge Options dialog box.
|
Output File |
Description |
|
BrokenLinkLog_<timestamp>.xml |
Contains information regarding the broken link and the parent document. |
|
Unordered_<timestamp>.CSV |
Lists input files after the completion of the scan for broken links. Double-clicking the file opens it in Microsoft Excel. Caution: This file cannot be used as input to the Add to Solid Edge SP process. |
|
Ordered_<timestamp>.CSV |
Contains an ordered list of your input files along with their reverse links. If a file has a reverse link, it is listed twice with two order numbers and also listed twice in the pass/fail log. The ordered list is generated by either the output from a dry run or as a result of the pass/fail log. Note: You can rename the Ordered_<timestamp>.csv file and use it as an input file to Add to Solid Edge SP however the format must match the expected input. You can only submit one .CSV file for processing at a time. |
|
SuccessFailureLog_<timestamp>.CSV |
Lists the documents you are importing and provides a summary of success or failure of the import process for each file. The log is written once per Add to Solid Edge SP session even if you elect to suspend or retry the upload process. Double-clicking the file opens it in Microsoft Excel. The order number in this file matches the order number from the Ordered_<timestamp>.CSV file so you can match up entries between the two files during troubleshooting. |
Note:
All log and output files persist from one Add to Solid Edge SP session to another. Work with your system administrator to develop a schedule to archive the contents of the folder you define as the default location for log files. The default location is defined on the File Locations page of the Solid Edge Options dialog box. Example: ...\Unigraphics Solutions\Solid Edge\Version 106\Log Files\Add to InsightXT.
When you use the Add to Solid Edge SP program, some requested actions may not complete, or they may complete with warnings. In either case, a notification dialog box is displayed. You cannot start a new import of files into the SharePoint database until the previous one is completed or canceled.
The options on the notification dialog box determine how you proceed. You can view the log generated by the process, view a summary, continue, cancel, suspend, or view help regarding the upload process.
View Log--Displays the Add to Solid Edge SP log file.
Summary--Displays the Solid Edge SP Information dialog box providing a quick summary of errors or warnings encountered during the Add to Solid Edge SP process.
Continue--Continues the Add to Solid Edge SP process and starts loading the files into the managed environment. This option is disabled if there are errors noted.
Cancel--Exits the Add to Solid Edge SP process so you can start over. Any processing is discarded and the queue is cleared of documents being loaded into Teamcenter. You are returned to the Add to Solid Edge SP dialog box.
Suspend--Interrupts processing and exits the Add to Solid Edge SP program, but leaves the import queue intact. Data already created in SharePoint is not deleted. When you later restart the Add to Solid Edge SP process using the Retry button, the files resume loading from this point.
Help--Displays help information regarding the dialog box.
If you previously suspended the transaction, the notification dialog box is displayed automatically when you next start the Add to Solid Edge SP program.
The Add to Solid Edge SP program compares the properties of a document with those existing in the SharePoint database. As a result, you can import files over files that already exist in the SharePoint database. Add to Solid Edge SP adds the import time to the original file, and on subsequent loads it checks to see if the modified date is after the import date. If the document being imported has not been modified since the last import, it is recognized as already being in the database and is not re-added to SharePoint on subsequent imports. However, if the unmanaged file is modified after its initial import into the database, on subsequent imports you are given the options to:
Check out the document and overwrite it.
Check out all files that exist and overwrite them.
Leave the file and use the file already in the database.
Leave all files and use the ones that already exist in the database.
Cancel the import process.
In the event the Add to Solid Edge SP comparison discovers an item number that already exists in the database, it compares the file being imported to all revisions, datasets, and files that comprise the dataset. If a match is found, you are given the opportunity to determine the action on the file being imported. If no match is found, the file is assigned a new item number and a record of the action will be placed in the log file.
Note:
During an overwrite condition, BOM precision is not changed.