2

Automation: when using Additonal Adapters / Connections, include DW_SourceCode in primary key

As title says, if you consolidate multiple sources, you need DW_SourceCode in the PK should the PK field of a table be the same in 2 databases.

We see this in scenario's where companies want to consolidate multiple ERPs / sources but the ERP uses integers as PKs for companies / locations etc... This gives PK conflicts, which is solved by adding DW_SourceCode to the constraints.

Navision is less impacted if the DW_Account is unique between two databases, but we have had a conflict there already so we add DW_SourceCode to the PK.

So it would be great if the automation feature would take this into account and add the DW_SourceCode in the PK when Additional Sources are used.

2 comments

Please sign in to leave a comment.