Import codes

Bulk import the following codes into the Transtream database through the Administration App:

• Product data (Data > Products)
• Account codes (Data > Billing Codes)
• Company codes (Data > Billing Codes)
• Cost Centers (Data > Billing Codes)

Adding, removing or editing a code manually in the Administration App updates the database real-time.

Import file structure

Supported are the following file types:

• CSV
• TXT
• XML

CSV file structure

Top

Make sure your CSV file contains the following:

• The file extension is lowercase .csv, e.g. importFile.csv
• The file content is comma-delimited (,).
• Any field that includes comma (e.g. a Description field) as part of the content must be surrounded by the double quote character (“). Otherwise, the import process will read the comma as a delimiter rather than a character.
• The first row lists column headings that match database entity column names.
• Each data item corresponds to the column heading, and so it has the same column index as the heading.

ProductNumber,ProductName,ProductReference1,ProductReference2,ProductReference3
PN-001,SULPHURIC ACID,,,
PN-002,METHYL TRICHLOROACETATE,,,
				

TXT file structure

Top

Make sure your text file contains the following:

• The file extension is lowercase .txt, e.g. importFile.txt
• The file content is pipe-delimited (|).
• Any field that includes pipe (e.g. a Description field) as part of the content must be surrounded by the double quote character (“). Otherwise, the import process will read the pipe as a delimiter rather than a character.
• The first row lists column headings that match database entity column names.
• Each data item corresponds to the column heading, and so it has the same column index as the heading.

ProductNumber,ProductName,ProductReference1,ProductReference2,ProductReference3
PN-001|SULPHURIC ACID|||
PN-002|METHYL TRICHLOROACETATE
			

XML file structure

Top

Make sure your XML file contains the following:

• The file extension is lowercase .xml, e.g. importFile.xml.
• All records are surrounded by a top level xml node. This does not have to match the entity name in the database but should be meaningful, and correspod with what's been imported (e.g.

  <CompanyCodes>

  for company codes).
• Each record has a node name that matches the the underlying entity (singular), e.g. for the Products table the node name that describes the record should be called Product.
• Each column heading corresponds to the entity column heading, e.g. the Products.ProductNumber database column should have the xml node name ProductNumber.

<AccountCodes>
  <AccountCode>
    <Code>AC1</Code>
    <Description>[XML] Account Code 1</Description>
  </AccountCode>
  <AccountCode>
    <Code>AC2</Code>
    <Description>[XML] Account Code 2</Description>
  </AccountCode>
</AccountCodes>

Database column names and types

Below listed are column names and data type required for the correct file structure when importing codes into Transtream.

Products

Top

Supported entity column headings and data type for [dbo.Products]

Account Codes

Top

Supported entity column headings and data type for [dbo.Account Codes].

Company Codes

Top

Supported entity column headings and data type for [dbo.Company Codes].

Cost Centers

Top

Supported entity column headings and data type for [dbo.Cost Centers].

Related Content

• Product Codes gives an overview on configuring product codes in Administration App.