Skip to main content

Datasource Field options

Each Field in a Datasource Mapping has options that control how it appears and behaves. The options are the same across Datasource kinds, with two exceptions: U2 Datasource Fields have extra options, and Web Datasources have no Fields to edit.

Editing a Field​

  1. From the Datasource listing page, open the Datasource.
  2. Click Mappings in the left menu.
  3. Open the Mapping that contains the Field.
  4. Double-click the Field to open the Edit Field window.
The Edit Field window for an Integer Number Field, showing Name, Data Type, Column Type, Number Formatting with a sample, and a Security restricted toggle
The Edit Field window.

The available options depend on the Field's data type:

  • Name: the Field's name as it appears in the Mapping's column. This does not change the alias.

  • Description: an optional description of the data in the Field.

  • Data Type: the default data type for the Field in new Queries. It affects how the Field behaves as a Query output and how its values are stored in Elasticsearch:

    Data TypeWhat it is
    TextA string filterable by word. Searching World matches a value of Hello World.
    KeywordA string matched only in full. Searching World does not match Hello World, but Hello World does.
    Full TextNot filterable, groupable, or sortable. Use only for potentially long content like comments or email bodies.
    Decimal NumberExact numeric values with a set number of decimal places.
    Integer NumberValues between +/- 2^31, truncating decimals without rounding.
    DateA date and time with configurable display formatting.
    TimestampA date and time formatted only as YYYY-MM-DD HH:MM:SS (for example 2020-03-11 13:45:30).
    TimeA time of day in hours, minutes, and seconds.
    BooleanTrue or false.
    LocationAn object with lat and long properties, used to power the Google Maps visual when that feature is enabled.
    ObjectJSON objects.
    Immense Term errors

    If a Query runs and some rows fail to index with an "Immense Term" error, a Field is too large for its data type and should be Full Text.

  • Column Type: the specific SQL data type (not available on U2 Datasources).

  • Formatting: sets exactly how the data appears. Not all data types have formatting options.

  • Security: toggles whether the Field is restricted. See Mapping Sets and restricted Fields.

  • Field Set: adds the Field to a Field Set, or creates one. See Field Sets.

  • Codes: if the Field is a code in a code/description pairing, assign it a Code so descriptions show in Datasets and Ad Hoc Queries. Codes are set up under Administration.

Click Save when done.

U2 options​

U2 Datasource Fields share most options with other kinds, but have no Column Type (U2 uses different data types than SQL) and add some U2-specific options:

The U2 Field options: Multivalued, Subvalued, SB+ Field, and Use custom conversion code checkboxes
U2 Field options.
  • Multivalued: whether the Field holds multiple values within a single attribute of a record (an array or list, typically delimited by a special character).
    • Subvalued: whether a multivalued Field's values are further structured into subvalues.
  • SB+ Field: whether the Field uses SystemBuilder Plus (SB+), an application environment for multivalue databases.
  • Use custom conversion code: sets the conversion code that formats the Field's final output.
Also available through the REST API
Everything on this page is built on Informer's public REST API, the same one the product uses, so your scripts and integrations can do it too. Developer reference: Datasources.