Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Access Policy transformation
  6. Aggregator transformation
  7. B2B transformation
  8. Chunking transformation
  9. Cleanse transformation
  10. Data Masking transformation
  11. Data Services transformation
  12. Deduplicate transformation
  13. Expression transformation
  14. Filter transformation
  15. Hierarchy Builder transformation
  16. Hierarchy Parser transformation
  17. Hierarchy Processor transformation
  18. Input transformation
  19. Java transformation
  20. Java transformation API reference
  21. Joiner transformation
  22. Labeler transformation
  23. Lookup transformation
  24. Machine Learning transformation
  25. Mapplet transformation
  26. Normalizer transformation
  27. Output transformation
  28. Parse transformation
  29. Python transformation
  30. Rank transformation
  31. Router transformation
  32. Rule Specification transformation
  33. Sequence transformation
  34. Sorter transformation
  35. SQL transformation
  36. Structure Parser transformation
  37. Transaction Control transformation
  38. Union transformation
  39. Vector Embedding transformation
  40. Velocity transformation
  41. Verifier transformation
  42. Web Services transformation

Transformations

Transformations

Lookup object properties

Lookup object properties

When you configure a lookup, you select the lookup connection and lookup object. You also define the behavior when a lookup condition returns more than one match.
The following table describes the lookup object properties:
Property
Description
Connection
Name of the lookup connection.
Source Type
Source type. For database lookups, the source type can be single object, parameter, or query. For flat file lookups, the source type can be single object, file list, command, or parameter.
Use a local file for source metadata
Applies to single object source types with flat file connections.
When you enable this property,
Data Integration
generates field metadata from a local file that you provide. Use this metadata to configure the mapping. At run time,
Data Integration
uses the metadata in the local file.
Local File
Local file that
Data Integration
uses to generate lookup field metadata.
The file must use UTF-8 encoding. You can use any file type except the following types:

    .asp

    .aspx

    .bat

    .bin

    .bmp

    .cmd

    .dll

    .exe

    .gif

    .html

    .jar

    .jpeg

    .jpg

    .js

    .jsp

    .pdf

    .php

    .png

    .scr

    .sh

    .tif

    .tiff

    .vbs

    .zip

Selecting a local file overwrites any existing field metadata.
Lookup Object
If the source type is a single object, this property specifies the lookup file, table, or object.
If the source property is a file list, this property specifies the text file that contains the file list.
If the source type is a command, this property specifies the sample file from which
Data Integration
imports the return fields.
Parameter
If the source type is a parameter, this property specifies the parameter.
Define Query
If the source type is a query, displays the
Edit Custom Query
dialog box. Enter a valid custom query and click
OK
.
Multiple Matches
Behavior when the lookup condition returns multiple matches. You can return all rows, any row, the first row, the last row, or an error.
If you choose all rows and there are multiple matches, the Lookup transformation is an active transformation. If you choose any row, the first row, or the last row and there are multiple matches, the Lookup transformation is a passive transformation.
Formatting Options
File formatting options which are applicable if the lookup object is a flat file.
Opens the
Formatting Options
dialog box to define the format of the file. Configure the following file format options:
  • Delimiter. Delimiter character.
  • Other Delimiter. Enter up to 10 single-byte to use as row or column breaks.
    The first character used in a row delimiter can't also be used in the column delimiter. You also can't use ASCII characters 128-160 or multiple nonprintable characters.
  • Treat multiple characters as a single delimiter
    .
    Treats the specified set of delimiters as one delimiter. For example, a source file contains the following record: abc~def|ghi~|~|jkl|~mno. If you specify the delimiter as ( ~ | ), Data Integration reads the record as three columns separated by two delimiters: abc~def|ghi, NULL, jkl|~mno. If you disable this option, Data Integration reads the record as nine columns separated by eight delimiters: abc, def, ghi, NULL, NULL, NULL, jkl, NULL, mno.
  • Treat consecutive delimiters as one. Treats one or more consecutive column delimiters as one. The default is to treat consecutive delimiters as a null value.
  • Row Delimiter. Line break character. Select a line break character from the list. The default is line-feed, \012 LF (\n).
  • Choose the delimiter for header and data. If selected, the delimiter between the header and data row is either a new line or the same as the row delimiter. By default, the delimiter is the same as the row delimiter in the mapping canvas and a new line during run time.
  • Text Qualifier. Character to qualify text.
  • Escape character. Escape character.
  • Field labels. Determines if the task generates field labels or imports labels from the source file.
  • First data row. The first row of data. The task starts the read at the row number that you enter.
Use caution when updating the file formating options after you have updated the return field metadata. Changes to formating options can synchronize return fields with fields in the lookup object. For more information see, Lookup return fields.
Command
If the source type is a command, this property specifies the command that generates the file list.
For more information about file lists and commands, see File lists. For more information about parameters and file formats, see
Mappings
.

0 COMMENTS

We’d like to hear from you!