Import
The CSV detail log file typically contains one line of detail data for each configuration data worksheet row processed by the import operation. However, when importing a configuration data row related to channel definitions, the DSU writes multiple lines to the CSV detail log file for that row. This is because importing the configuration data for channel definitions involves importing data into multiple database tables. Configuration data worksheet rows that require a database update action also cause the DSU to write multiple lines to the CSV detail file.
Table 1 shows the detail data logged
for each DSU import operation.
| Value | Description |
|---|---|
| Worksheet Name | The name of the configuration data worksheet used for the import operation |
| Row Number | The row number in the configuration data worksheet that contains the data that was being imported |
| Database Table Name | The name of the database table into which the configuration data was imported |
| Action | The database action that was used for this row
of configuration data. The values are:
|
| Change History | If the DSU performs a database update
operation for this row of configuration data, two lines of change
history data are also written to the detail log. The first additional
line logs the original, or before, values from the table. The second
line logs the updated, or after values.
Note: Before and
after values cannot be determined for the Endpoint_Sub_Services database
table
|
The CSV detail log file for the import operation has the following
naming convention: YYYYMMDD_HHmmss_SSS_inRulesFileName_Detail.csv where:
- YYYY
- is the year
- MM
- is the month
- DD
- is the day
- HH
- is the hour
- mm
- are minutes
- ss
- are seconds
- SSS
- are milliseconds
- inRulesFileName
- is the name, without the file extension, of the configuration data workbook specified in the inRulesFileName property