Home
Projects
A project is a container for HCL Link artifacts.
Maps
Maps define input and output specifications and mapping rules for data transformation.
Map settings
Validation settings
Validation > Stop On Error

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
    - Map Audit settings
    - MapTrace settings
    - WorkSpace settings
    - Time Zone settings
    - Validation settings
      - Validation > Enabled
      - Validation > Stop On Error
      - Validation > RestrictionError
      - Validation > SizeError
      - Validation > Validate Presentation
      - Validation > Ignore Component Rules
        Use the Validate Component Rules map setting to run a map without validating component rules, for example, when your data does not conform exactly to a particular schema.
    - Retry settings
    - Warnings settings
  - Configuring bursts
  - Building maps
  - Running a map
  - Managing invalid data
  - Map audit overview
  - Troubleshooting
  - 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.

Validation > Stop On Error

Under certain circumstances, multiple errors are detected that occur during validation. The Stop On Error setting defines where to halt map execution. With either setting, if an error is found in the input, no output objects are built.

Value: Description
On: Only validate through the input card where the first error occurs. Stop executing the map after validating that input card, even if there are multiple input cards.
Off: Continue validating data until all errors are found. Even when validation finds data errors in a given input card, map execution continues with the next input card.