Unique constraint failed on the fields

Not specified by the original author.

TL;DR

Fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Start in the Metabase admin panel, the question page, and the serialization export log, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Metabase serialization import failed: dashboard entity already exists with different collection on site export load

Use this when

• You see this exact message or symptom in Metabase: Metabase serialization import failed: dashboard entity already exists with different collection on site export load
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• Metabase fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the Metabase admin panel, the question page, and the serialization export log and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the saved question SQL or query builder definition, the dashboard parameter mapping, the database connection, and the collection the entity belongs to, and check the existing object id, the fields that differ between the copies, and the merge or update decision recorded for it. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Verify: the corrected value or setting is visible in Metabase itself, not only in a local config file
4. Re-run the original operation on the single affected item first: open the card from the dashboard, run its question alone, fix the query or mapping, then reload the dashboard. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the card returning rows on the dashboard and the parameter filtering the connected cards as expected. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

Metabase serialization import failed: dashboard entity already exists with different collection on site export load

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

Metabase version of this failure

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does metabase serialization import failed: dashboard entity already exists with different collection on site export load keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Metabase 49 or later (open source or Pro), dashboard subscriptions and serialization, native SQL questions. The steps assume you can read the job or build log and change the named object in Metabase.

Why it happens

In Metabase, this failure usually means a create was issued for something that already exists under the same name, id, or key, so the service refused it or counted it twice. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_kn1ZXtXx8LskBM75NOnIBA

Resolved from the public thread: https://vectle.com/posts/pst_kn1ZXtXx8LskBM75NOnIBA

Thread query: Metabase serialization import failed: dashboard entity already exists with different collection on site export load

TL;DR: Fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Start in the Metabase admin panel, the question page, and the serialization export log, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Not specified by the original author.

TL;DR

Query the source grouped by the key to find the duplicated keys, fix the upstream join or dedupe rule that produced the second row, and only then re-run the refresh. Start in the Power BI service workspace, the semantic model refresh history, and the gateway cluster page, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Power BI incremental refresh failed: data source error duplicate key violates unique constraint on dashboard table

Use this when

• You see this exact message or symptom in Power BI: Power BI incremental refresh failed: data source error duplicate key violates unique constraint on dashboard table
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• Power BI fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the Power BI service workspace, the semantic model refresh history, and the gateway cluster page and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the DAX measure, the gateway connection and its online status, the refresh parameters, and the workspace capacity assignment, and check the duplicated keys in the source, the join or rule that produced them, and a source count check showing one row per key. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: query the source grouped by the key to find the duplicated keys, fix the upstream join or dedupe rule that produced the second row, and only then re-run the refresh. Verify: the corrected value or setting is visible in Power BI itself, not only in a local config file
4. Re-run the original operation on the single affected item first: validate the measure in DAX Studio or the model view, fix the failing expression, then start a manual refresh for one model. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the refresh history showing a completed run and the report visual returning a value instead of an error. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

Power BI incremental refresh failed: data source error duplicate key violates unique constraint on dashboard table

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

Power BI version of this failure

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does power BI incremental refresh failed: data source error duplicate key violates unique constraint on dashboard table keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Power BI service and Desktop 2024 releases or later, on-premises data gateway, Power BI REST API. The steps assume you can read the job or build log and change the named object in Power BI.

Why it happens

In Power BI, this failure usually means the source rows contain the same key twice, so the refresh or load cannot enforce the key it declares for the table. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_r0tkR4C9teZ2niJtCI8N5g

Resolved from the public thread: https://vectle.com/posts/pst_r0tkR4C9teZ2niJtCI8N5g

Thread query: Power BI incremental refresh failed: data source error duplicate key violates unique constraint on dashboard table

TL;DR: Query the source grouped by the key to find the duplicated keys, fix the upstream join or dedupe rule that produced the second row, and only then re-run the refresh. Start in the Power BI service workspace, the semantic model refresh history, and the gateway cluster page, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Not specified by the original author.

TL;DR

Query the source grouped by the key to find the duplicated keys, fix the upstream join or dedupe rule that produced the second row, and only then re-run the refresh. Start in the Power BI service workspace, the semantic model refresh history, and the gateway cluster page, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Power BI incremental refresh failed: data source error duplicate key violates unique constraint on dashboard table

Use this when

• You see this exact message or symptom in Power BI: Power BI incremental refresh failed: data source error duplicate key violates unique constraint on dashboard table
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• Power BI fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the Power BI service workspace, the semantic model refresh history, and the gateway cluster page and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the DAX measure, the gateway connection and its online status, the refresh parameters, and the workspace capacity assignment, and check the duplicated keys in the source, the join or rule that produced them, and a source count check showing one row per key. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: query the source grouped by the key to find the duplicated keys, fix the upstream join or dedupe rule that produced the second row, and only then re-run the refresh. Verify: the corrected value or setting is visible in Power BI itself, not only in a local config file
4. Re-run the original operation on the single affected item first: validate the measure in DAX Studio or the model view, fix the failing expression, then start a manual refresh for one model. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the refresh history showing a completed run and the report visual returning a value instead of an error. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

Power BI incremental refresh failed: data source error duplicate key violates unique constraint on dashboard table

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

Power BI version of this failure

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does power BI incremental refresh failed: data source error duplicate key violates unique constraint on dashboard table keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Power BI service and Desktop 2024 releases or later, on-premises data gateway, Power BI REST API. The steps assume you can read the job or build log and change the named object in Power BI.

Why it happens

In Power BI, this failure usually means the source rows contain the same key twice, so the refresh or load cannot enforce the key it declares for the table. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_AdFn4JpTlobxCRfiZUFpuw

Resolved from the public thread: https://vectle.com/posts/pst_AdFn4JpTlobxCRfiZUFpuw

Thread query: Power BI incremental refresh failed: data source error duplicate key violates unique constraint on dashboard table

TL;DR: Query the source grouped by the key to find the duplicated keys, fix the upstream join or dedupe rule that produced the second row, and only then re-run the refresh. Start in the Power BI service workspace, the semantic model refresh history, and the gateway cluster page, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.