Tables

Tables are the core structured definitions and main semantic layer component within Knowledge Base.

A healthy connection is required to populate and edit the elements of this tab. See Connection section for more information.

For a summary overview of setting up this tab and for best practices, see Add Tables & Fields.

Key Components

The "Tables" tab is broken into actual "Tables (and Views)" and "Properties", "Fields", and "Details" for each Table.

Table Selection

You can add a table by selecting one from the dropdown of available tables/views. The available content is dictated by the connection configured for the Knowledge Base.

Table Definition

Each table has its subconstituents of properties.

Semantic Name

This is a more human-readable/plain representation of a target table.

Example:

Your source table might be na_cpg.inv_l_prod_v22 but its semantic name can simply be invoice_line.

Simple and intuitive namings work best. The quality of the semantic simplificiation / clean-up assists Lumi Workflows in more intuitive understanding of your data.

Description

This is a short summary of the table, what it's keyed on, what insights it relates to, and any other pertinent information.

It should NOT contain things like table relationships (covered in "Model" tab) or the fields or calculations within it (see further "Fields" and "Details" sections).

The best descriptions are concise and relevant to usage in a query.

Example:

Contains all invoice line items effective up to the August 31st 2024. Guaranteed unique on invoice_line_id but not invoice_line_key.

Fields

Fields follow a similar pattern of semantic name and description as with the table overall. These similarly provide context for Lumi Workflows to process.

The Data Type is represented as-is from the source system, it is unmodifiable (alike to the source name itself).

A unique option are Custom Fields, where you can define a query dynamically with the table if its definition does not exist at source. See associated section for more information.

Details

These are relevant points of information about a Table that give additional context about its limitations, how it can be used, etc.

Example:

Field Priority: Where any fields overlap or are similar with invoice_header, assume that the invoice_line property overrides the parent value.

Lumi AI offers many ways to define context for a Knowledge Base, whether its through the semantic names themselves, descriptions, Business Context tab, and more -- use judgement to determine where and when the context is relevant (i.e., always with the KB, only when a specific field is used, or any time the table is pertinent as a whole).