Expression.Error: A primary key already exists on the given table type.

[Anonymous]

Hi,

The setup of my Power Query is this:
1) A single query to a SQL Server connection. The connection has a SQL statement that is query folded back to the SQL Server. This query is named BaseTable. The BaseTable is a high granular level table.
2) I have another eight queries that all reference the BaseTable query. Each of these eight queries aggreagate the BaseTable data differently. For discussion, we call each of the eight queries Ref1, Ref2, Ref3..... Ref8.
3) Once the referenced queries have all completed their different aggregations. I then use query Ref5 merge that with Ref1.
I then merge Ref5 (which now has Ref1 included) with Ref2.
I then merge Ref5 (which now has Ref1 and Ref2 included) with Ref3.
And so on until all reference queries have been merge together.

So that is my PQ setup.
To make PQ execute quicker, I would like place a key (Table.AddKey) in the right places. So I intend to do this by (and correct me if this isn't the best approach):
1) Not place a key on the BaseTable query.
2) Place a key (Primary Key) on the Ref5 query at the point of all Ref5 query's aggregations being completed, and before the next step of the merge with Ref1.
3) Place key (Foreign Key) as the last step of queries Ref1, Ref2, Ref3, Ref4, Ref6, Ref7, Ref8.

Are the keys (PK and FK) being added to the right tables at the right step/point?
When I attempt to add my first key, the Primary Key, to Ref5 (between the aggregation steps and merging with other queries) I get the below error. I haven't explicity created any keys at this point in the whole .pbix file. Any ideas on how a primary key already exists?

Am I getting this error due to all the Ref queries, the queries where I am looking to place a key in, are somehow implicity given a key due to being reference queries?

Strangely, I can set each key as a Foreign Key but I can't set a Primary Key on any table without receiving the above error message.

Can anyone shed any light on this?

Thanks.

[v-piga-msft]

Hi @Anonymous ,

For your scenario, please refer to this similar thread which has been solved firstly.

In addition, for your error messge, I will suggest that you could duplicate BaseTable query and do the calculation instead of referencing the BaseTable query directly.

@ImkeF  any other ideas?

Best Regards,

Cherry