Page tree
Skip to end of metadata
Go to start of metadata

Table columns in the ADS map in a specific way to LDM elements. When you design the ADS output stage, use these table column naming standards. They ensure that any columns not in the LDM can be added using the Data Explorer. For more information about Data Explorer, see Set Up Data Explorer for a Project.

ADS column names that do not follow these standards cannot be added to the GoodData project with the Data Explorer.

ADS Table Column Mapping

Create ADS table column names with this format:



Here is how the ADS table column name maps to the LDM dataset element id:



Identifies the LDM <element_type>. Here are values and their mappings:

ADS <prefix_type>LDM element<element_type> abbreviation
cpconnection point (anchor)attr
ddate dimensiondate
rreference to another datasetlabel (from another dataset)

Optional, for labels only. The <element_name> of the attribute that the label applies to.

Uniquely identifies the LDM element. Can include underscores but cannot include spaces. May sometimes include the dataset name. See Conflict Resolution for Non-Unique LDM Elements.

This text also creates the LDM element title. When the title is generated, single underscores are replaced by spaces and all words are capitalized. Examples:

l__person_name__nickname generates element title Nickname
l__person_name__my_nickname generates element title My Nickname


The name of the ADS table.

Example of ADS to LDM mapping


Dataset Mapping

When an ADS table is mapped to a LDM, the table name is preceded by “dataset.” in the LDM dataset identifier. The last part of the dataset identifier and the ADS table name must match exactly.

Example: ADS table name person becomes LDM dataset dataset.person.

Each ADS output stage table must match only one LDM dataset. If multiple mapping occurs, data loading and ADS output stage diff generation both fail.

Conflict Resolution for Non-Unique LDM Elements

Typically, only the last section of an LDM element id is used to map ADS tables to LDM datasets. This is true when the second part of the LDM element id matches the ADS table that it maps to. For example, LDM fact:

fact.person.age in dataset dataset.person

becomes ADS column



However, if the ADS table and the LDM dataset do not match, the last two sections of the LDM element become part of the ADS column name. For example, this LDM fact:

fact.spouse.age in dataset dataset.person

becomes ADS column



Inclusion of LDM dataset name in the ADS column name provides conflict resolution when the last part of an LDM element id is not unique in a dataset. This duplication typically happens when LDM elements are moved between datasets and the LDM element id is not changed.

  • No labels