Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • File Naming: 3D files must be imported to Magics with the MES Part ID (“Part #”) at the beginning of the file name.

  • Export Report: A Magics report needs to be exported and saved as a .CSV file.

  • UTF-8 Format: The CSV file needs to be exported in UTF-8 format.

  • Parts in First Column: The names of the 3D files must be written in the first column of the CSV.

  • Separate Lines for Copies: Each copy of a part in the build must be written to the CSV in a separate line (e.g., a part with a quantity of 5 needs 5 individual lines in the CSV).

  • No Empty Lines: The CSV file must not contain empty lines.

Example CSV File

An example CSV containing only the needed information is shown below. The following file represents a build containing part #437 with a total quantity of 5 (the number of lines are counted) and #438 with a total quantity of 3.

...

The important part of the part file name is the Part ID at the beginning of the string. The remaining name is not considered when matching csv content and parts in the MES.

Handling of Bad Content in CSV Files

The CSV import functionality of Magics has been enhanced to ensure successful import and matching of parts and quantities. Specifically, it now handles the following scenarios more effectively:

  • Empty lines in the CSV: These are now ignored during the import process, preventing any disruptions they might have caused.

  • Unknown parts in the CSV: The system now disregards any parts that it doesn't recognize, allowing the import process to continue smoothly with the known parts.

File Validation During the Import

...

Error

Potential Reasons

Solution

Part Not Found

The Part ID from the CSV file could not be matched with any part in the MES.

Check whether indicated Part ID is correct.

Quantity Issue

The specified quantity cannot be imported (e.g., overquantity cannot be applied)

Check whether the indicated part has a sequence in the first workflow step.

Parsing Error

  • Not a valid CSV file CSV file contains empty lines

  • First column not formatted as expected

  • Encoding errors

Check all the prerequisites listed under “Prerequisites for the Magics CSV” above.

Empty File

The CSV file is empty

Check that your CSV file exported correctly.

...