An additional property '[name]' was included in the [path] property
Power BIIn general form, with the parts that change in brackets:
An additional property '[name]' was included in the [path] property of [file].
Power BI Desktop opened the report and checked each file against its schema. A file has a property that schema does not define. The message names the property, where it is in the file, and the file. Desktop lists one line per file, under "Your report has issues that could not be resolved".
- Usually
- Power BI Desktop wrote a property its own schema does not define
- Fix
- Choose Close Desktop.
Check your project opens the Report Doctor with this message filled in. The text travels in the URL fragment, which browsers never send to a server.
How the message appears
Copied exactly from each source. A name in square brackets replaced one from someone else's project.
An additional property 'preserveNewVisualVisibility' was included in the /options property of eac6b45420a6c7c3b05e.bookmark.json.1 more report of this message
Your report has issues that could not be resolved We encountered some issues in the report definition but were unable to fix them. Please review and address these issues before opening the report. List of issues (2): An additional property 'preserveNewVisualVisibility' was included in the /options property of 29b8cb25f96bfc655538.bookmark.json. An additional property 'preserveNewVisualVisibility' was included in the /options property of 692475521609f23f77da.bookmark.json.
What causes it
Power BI Desktop wrote a property its own schema does not define
Power BI Desktop 2.159.883.0 writes
preserveNewVisualVisibilityinto theoptionsof each new bookmark, and still labels the filebookmark/2.1.0. That schema does not define the property. We saved two bookmarks, closed the project and opened it again, and Desktop showed this message for both files. A Microsoft schema issue reports the same property from Power BI Desktop 2.158.1177.0, where a Fabric import refused it. That issue says not every machine writes the property, and that removing the line makes the file validate.Source: Power BI Desktop 2.159.883.0, Studio fixture F9[2], microsoft/json-schemas issue 656[3].
The Report Doctor finds this. It reports “Power BI Desktop refuses this file”, with the file and line.
The fix
Choose Close Desktop. Open each file the message names and delete the preserveNewVisualVisibility line. Then open the project again.
In bookmarks/Bookmark7c19b7211ada7de10c30.bookmark.json:
"options": {
"targetVisualNames": [
"5acb1caf298449a8acb4"
],
"preserveNewVisualVisibility": true
},Lines 4 and 5 change.
"options": {
"targetVisualNames": [
"5acb1caf298449a8acb4"
]
},From the SalesSense sample project by Rui Romano (MIT licence).
The Power BI Report Doctor reads a PBIP folder or .zip and lists the file and line to fix. Nothing is uploaded. For the other messages a project can stop on, listed by the file that causes each, see Power BI Desktop can't open a PBIP.
Worth knowing
- The message names the file,
<id>.bookmark.json, not the name you gave the bookmark. The files are indefinition/bookmarks/. - "Copy details to clipboard" copies only the list of issues, one line per file.
- A Fabric import shows a different message for the same property. See Property has not been defined.
Sources
- [1]Desktop run: Power BI Desktop 2.159.883.0, Studio fixture F8b. Our run on Wide World Importers open data: a new bookmark added to the project as fixture F8b left it, saved, and opened again. Copied with "Copy details to clipboard". Seen 2026-10-23.
- [2]Desktop run: Power BI Desktop 2.159.883.0, Studio fixture F9. Our run on Wide World Importers open data: the dialog shown when the project opened after two bookmarks were saved. Typed from our screenshot. Seen 2026-10-21.
- [3]GitHub issue: microsoft/json-schemas issue 656. The issue description, "Actual result" and "Analysis". Read 2026-10-04.
Did this page help?
Your answer helps us know what to improve and what you find useful.