After creating a column in a logical table, automatic

mapping does not occur for attributes referencing

columns with the same name in MicroStrategy 9.x
Started 07-01-2005 by

JaimeP
Modified 07-01-2005 by

JaimeP
Article Options
Labels:
Architect

Engine

Logical Views
0Likes
SYMPTOM:
After defining a logical table and editing the attribute(s) that already reference the column(s) used
in the logical table, the logical table is not listed as an available source table for the attribute form
referencing the column.
A logical table is defined as follows with Year_ID, which is used in the Year attribute as shown in
the image below:

As shown below, the logical table is not listed as a source table for the ID attribute form when
modifying the Year attribute:

CAUSE:
This issue may occur if the column object created in the Logical Table is not identical in all
aspects, including Object ID, with the column objects used for the other tables containing the
same column.
ACTION:
Complete the following steps in the Logical Table Editor:
1.

Remove the current column object associated with the column in the Logical Table SQL
as shown in the image below:

2.

In the left-hand pane of the editor where the tables are listed, expand one of the tables
presently used as a source table for the attribute form in question as shown below:

3.

Drag and drop the column object into the lower right-hand pane where the objects are
defined for the Logical Table as shown in the image below:

4.

Save and close.

5.

The logical table should now be listed as an available source table in the attribute.

How to create logical tables without creating

duplicate columns objects in MicroStrategy Desktop
9.x
Started 09-30-2007 by

Alma MdelC
Modified 09-30-2007 by

Alma MdelC
Article Options
Labels:
Architect

Developer
0Likes
When creating a logical table, there are two ways how the user can define the column objects.
The user can choose to click on the 'Add' button and will add a new entry in the columns list or
the user can drag and drop from the list of existing columns at the left of the window.

If the user drags and drops the column from the list of existing columns, MicroStrategy
will use the same column object, if it already exists, and will map the reference to that object. If
there is an existing attribute form or metric that is mapped to this column, the automatic mapping
will also map them to this new Table.
If the customer chooses to use the 'Add' button, MicroStrategy will create a new column
object even if the user specifes the same data type and precision of the existing one. This new
columns will have its own mapping of objects since it is treated as a completely new object.
If the column is created using the 'Add' button and also Automatic mapping is turned on, the
attributes won't make reference to the existing column since a new column object is created. A
similar behavior is reported in the following MicroStrategy Knowledge Base technical note:

TN12000 (TN5300-800-0666): After creating a column in a logical table, automatic mapping does
not occur for attributes referencing columns with the same name in MicroStrategy 9.x

This key is already associated with an element of

this collection error message appears when trying
to save a group form in the Attribute Editor in
MicroStrategy Desktop 9.x.
Started 05-11-2010 by

JennaK
Modified 01-29-2015 by

ekanamala
Article Options
Labels:
Architect

Developer
1Like
SYMPTOM:
When creating or editing an attribute with a grouped form mapped to a logical table, the following
error message is displayed:

'This key is already associated with an element of this collection'.

STEP TO REPRODUCE:
Follow the steps below to reproduce this issue in the MicroStrategy Tutorial project 9.x.
1.

Create a logical table defined as LU_DIST_CTR_LV using the columns from the
LU_DIST_CTR table using the Add button as shown in the image below:

1.

Create a new attribute with two expressions in the ID form. One expression should be
pointing to the physical table while the other one points to the newly created logical table as
shown in the following image:

2.

Create a second attribute form and attempt to group the forms. The following warning is
displayed:

The category selected for this form is already being used by another
form in the current attribute. The only way to have multiple forms
using the same form category is by creating a form group. Do you wish
to create a form group?

3.

Clicking on the "Yes" button causes the following error message to appear:

Unexpected error

This key is already associated with an element of this collection

CAUSE:
The column object created in the logical table was defined by typing the expression instead of
mapping it to an existing column.
ACTION:
Define the column objects in the logical table by dragging existing columns from the physical
source table from instead of using the 'Add' button as shown in the image below.

By following this procedure, users will notice that the attribute can be defined using only one
expression because the columns are not duplicated. Attribute forms can be then grouped
correctly as shown in the image below:

For more information about Logical Tables (Logical View), please refer to the following Technical
Notes:

TN: 12000 (TN5300-800-0666): After creating a column in a logical table, automatic

mapping does not occur for attributes referencing columns with the same name in
MicroStrategy 9.x
TN: 16858 (TN5700-8X-2746): How to create logical tables without creating duplicate columns
objects in MicroStrategy Desktop 9.x