Home
Projects
A project is a container for HCL Link artifacts.
Maps
Maps define input and output specifications and mapping rules for data transformation.
Troubleshooting
Trace files
Trace for general data
The trace file records map execution progress. You can enable the trace option from the map settings or from the adapter command line. You can trace the input data, the output data, or both.
Unknown data

Projects
A project is a container for HCL Link artifacts.
- Flows
  This documentation describes how Flows can be run from REST API, listeners, or they can be scheduled.
- Maps
  Maps define input and output specifications and mapping rules for data transformation.
  - Using Maps
  - Create maps to specify sources and targets
  - Maps and map source files
    Basic tasks involved in creating and managing maps.
  - Input and output cards
  - Card settings
  - Map rules
  - Formulating map rules
  - Functional map basics
  - Map settings
  - Configuring bursts
  - Building maps
  - Running a map
  - Managing invalid data
  - Map audit overview
  - Troubleshooting
    - Overview of debugging aids
    - Command Server window
    - Run results
    - Audit log
    - Customized validation settings
    - Map Debugger
    - Trace files
      - Trace for general data
        The trace file records map execution progress. You can enable the trace option from the map settings or from the adapter command line. You can trace the input data, the output data, or both.
        Creating a trace file
        You specify the name and location of the trace file in the map settings. If you ran a map and got a message that an input was invalid, turn on the input trace only. If you got a message that an output was invalid, turn on the output trace only. If you trace both input and output, the input messages are at the beginning of the file, followed by the output messages.
        Trace file contents
        When data is valid
        Group validation
        Valid card objects
        Invalid data
        Invalid card objects
        Finding the important messages
        Existence of data
        Validation for invalid objects
        Unknown data
        Negative messages not fatal
        Example of optional occurrences
      - Static file validation and tracing
        HCL Link validates a static input file in a compiled map only once, when the map loads, and produces a trace file only if the static file fails validation.
      - Trace for XML data
      - Trace for XML parser errors only
  - Error and warning messages
- Schemas
  Use the schema designer to define, modify, and view schemas. A schema describes the syntax, structure, and semantics of your data.
- Connections and Actions
  This documentation describes connections and actions.
- Files
  Files are used in various places within HCL Link. HCL Link allows files to be uploaded to the HCL Linkserver.

Unknown data

When input data is validated, additional data that does not validate as part of the input may also be found. This data is unknown data.

An example input is composed of Product(s) and Product is not defined with properties that allow its existence to be predetermined.

The second Product is invalid because the Quantity field is missing.

When the invalid Product is found, it is not known to exist. Therefore, it is assumed to be unknown data.

Sometimes a message about unknown data is not significant. You may get a message about unknown data because there are extra carriage returns or "junk" data at the end of an input file. You should read the trace file to determine whether all of the pertinent input data was found.