Home
Projects
A project is a container for HCL Link artifacts.
Maps
Maps define input and output specifications and mapping rules for data transformation.
Card settings
Editing a card
Changing the type of an input card

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
    - Schema
    - Input card settings
    - Output card settings
    - Input and output card settings
    - Effects of modifying a schema
    - Changing a type that is used for a card
    - SyntaxCard
      The SyntaxCard setting defines the output card as a syntax card.
    - Editing a card
  - Map rules
  - Formulating map rules
  - Functional map basics
  - Map 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.

Changing the type of an input card

About this task

You can change the type of an input card.

Note that when you change the type of an input card, if an object within that card is referenced in a map rule, the object name might now be invalid.

If a map rule contains the name of an object on an input card:

Flower:ProgressReading:Input

The type of the input card is GrowthReport and it is changed to ProgressReading, which is a component of GrowthReport. The object names in the map rule are now incorrect. Flower is a component of ProgressReading, which is now the type of the card. After the type of the card has changed, the correct name for Flower is Flower:Input.

Not all modifications to an input type will affect map rules. For example, if you add a component to an input type, map rules are not affected. Also, if you delete an input component that is not referenced in a map rule, the map rules are not affected.