It's possible to import manufacturing process results into the Tascus database using a .csv file import.
Example .csv file here.
File Naming
.csv files should be named in the following format:
[PartNo]-[SerialNumber]-[Date].csv
e.g. PartNo = 1234 Serial No = 001 Date = 13/03/2023
1234-001-13032023.csv
Folder Structure
All .csv files should be uploaded into a single directory. Once Tascus has imported a .csv file into the database, it will either delete or move the .csv file to an 'Archived' folder.
File Contents
Tascus uses the Field Name to import values - rather than a fixed column position, so please ensure that any exported .csv files use a header column with Field Names formatted exactly as outlined below.
You don't have to include optional fields, or you can leave optional fields blank in the .csv file.
Field Name | Required / Optional | Acceptable Values |
|---|---|---|
StepName | Optional | Description of the type of check:
|
StepMeasurement | Required | Text description of the measurement - up to 255 characters |
StepResult | Optional | Text or numeric value of the result. e.g. '1.234' or 'Done' |
HighLimit | Optional | Text or numeric value which the StepResult is compared against |
LowLimit | Optional | Text or numeric value which the StepResult is compared against |
StepStatus | Required | Pass or Fail |
Units | Optional | Units of a numeric measurement |
StepRun | Optional | If the step is repeated multiple times e.g. a retest if there are failures, this records an integer of the number of runs. |
OperationName | Optional | The Tascus text (up to 50 characters) OperationName of the manufacturing process. |
OperationID | Optional | The Tascus OperationID (integer) of the manufacturing process. |
Date | Required | dd/mm/yyyy hh:mm:ss |
