Remove Duplicate Additional Keys

When you migrate the semantic model from Data Modeler, Semantic Modeler imports any duplicate additional keys contained in the model's physical tables.

Duplicate additional keys can be:

• Listed as a join key and an additional key - For example, the Join Key field contains ORDER_KEY and the Additional Keys field contains four instances of ORDER_KEY. In this case, you delete all four instances of ORDER_KEY from the Additional Keys field.
• Listed more than once as an Additional Key, but not listed as a Join Key - For example, the Additional Key field contains three instances of ORDER_KEY. In this case, you delete two instances of ORDER_KEY and leave one instance of ORDER_KEY.

When you run Check Consistency, it flags duplicate additional keys as error 40112 "The object physical table name has duplicate additional keys".

It's best practice to remove all duplicate additional keys from the migrated model.

1. On the Home page, click Navigator and then click Semantic Models.
2. In the Semantic Models page, click a semantic model to open it.
3. Click Check Consistency to run check consistency on the semantic model.
4. In the Global tab, locate the first 40112 error in the error list. Click the error's physical table link.
5. In the physical table, click the General tab and scroll to Additional Keys.
6. Hover over a duplicate key and click Delete to delete the key. Repeat this step to remove all duplicate keys.
   Note that clicking the X next to the duplicate key doesn't delete it. You must click the Delete icon .
7. Click Check Consistency to re-run check consistency.
8. Locate each 40112 error in the error list and repeat the above steps for each.