Values for the 'pageBinding.name' property must be unique
Power BIA page's page.json can carry a pageBinding, which drillthrough and page tooltips use. Other pages can refer to it by name, so the name must be unique within the report. When two pages share a name, Power BI Desktop reports an error.
How the message appears
Copied exactly from each source. A name in square brackets replaced one from someone else's project.
Values for the 'pageBinding.name' property must be unique.
In general form, with the parts that change in brackets:
Values for the 'pageBinding.name' property must be unique.
The fix
Give the copied page a pageBinding.name no other page in the report uses. Search the other page.json files for the old name first, in case a drillthrough refers to it.
In pages/ReportSection89a9619c7025093ade1c/page.json:
"pageBinding": {
"name": "199d626bac9792829234","pageBinding": {
"name": "Pod6",The report's other page already uses 199d626bac9792829234.
From the SalesSense sample project by Rui Romano (MIT licence).
What causes it
A page folder was copied from another report
Microsoft lists this as a common PBIR error after copying a page folder. Since June 2024 Power BI Desktop names a new page binding with a GUID, so the clash comes from pages made before then.
Source: Power BI Desktop project report folder.
The Report Doctor finds this. It reports “Two pages share a page binding name”, with the file and line.
Check a project in your browser
The Power BI Report Doctor reads a PBIP folder or .zip and lists the file and line to fix. Nothing is uploaded.
Sources
- Microsoft Learn: Power BI Desktop project report folder. "External changes to PBIR files" and "Common PBIR errors". Read 2026-10-03.
Written by Vishnu Shankar.