Property has not been defined and the schema does not allow additional properties
Power BIThe message, with the parts that change in brackets:
Property '[name]' has not been defined and the schema does not allow additional properties. Path '[path]', line [n], position [n].
Power BI Desktop, or a Fabric import, read a project file and found a property its schema for that file does not have. The message names the file, the property, and its line.
- Usually
- A newer release of Power BI Desktop saved the projectPower BI Desktop wrote a property its own schema does not define
- Fix
- Open the project in the same Power BI Desktop release as the person who saved it, or a later one.
It opens the Report Doctor with this message filled in. Nothing is uploaded.
How the message appears
Copied exactly from each source. A name in square brackets replaced one from someone else's project.
An error occurred while trying to open '[project path].pbip': Error while reading [project path].Dataset\.pbi\editorSettings.json. DatasetEditorSettings: Property 'shouldNotifyUserOfNameConflictResolution' has not been defined and the schema does not allow additional properties. Path 'shouldNotifyUserOfNameConflictResolution', line 5, position 45.
1 more report of this message
Error Code: Report_Import_FailedToImportReport. Error Message: Report Workload failed to import the report with report id <report-id>. 'bookmarks/<bookmark-id>.bookmark.json': Property 'preserveNewVisualVisibility' has not been defined and the schema does not allow additional properties. Path 'options.preserveNewVisualVisibility', line 8, position 34.
What causes it
A newer release of Power BI Desktop saved the project
In the quoted case a colleague opened a project from a shared repository. The reply marked as the solution says that
shouldNotifyUserOfNameConflictResolutionwas added in the September release of Power BI Desktop, and that an older release does not recognise it.Source: Unknown property in EditorSettings file - PBIP Dataset[1].
The Report Doctor can't detect this, because the file is under.pbi/, which the Report Doctor never reads, by design.Power BI Desktop wrote a property its own schema does not define
In a Microsoft schema issue, Power BI Desktop 2.158.1177.0 added
preserveNewVisualVisibilityto theoptionsof new bookmarks and still labelled the filebookmark/2.1.0. That schema does not define the property, and the Fabric import refused the report with the message quoted here. The issue says not every machine writes the property. Its author says removing that one line makes the file validate and import.Source: microsoft/json-schemas issue 656[2].
The Report Doctor finds this. It reports “Power BI Desktop refuses this file”, with the file and line.
The fix
Open the project in the same Power BI Desktop release as the person who saved it, or a later one. In the quoted case, deleting the line from the file also let it open. If a bookmark file carries preserveNewVisualVisibility, delete that line.
In .pbi/editorSettings.json:
{
"version": "1.0",
"parallelQueryLoading": true,
"relationshipImportEnabled": true,
"shouldNotifyUserOfNameConflictResolution": true
}Lines 4 and 5 change.
{
"version": "1.0",
"parallelQueryLoading": true,
"relationshipImportEnabled": true
}The Power BI Report Doctor knows the properties Power BI Desktop has been seen to refuse, and gives the file and line. It cannot see a newer release's cache under .pbi. Nothing is uploaded.
Other messages that stop a project opening, by the file that causes each: Power BI Desktop can't open a PBIP.
Worth knowing
- For files under
definition/, the Report Doctor reports a property the declared schema does not allow, with its line. - Power BI Desktop shows its own message for the same bookmark property when it opens the project. See An additional property was included.
Sources
- [1]Microsoft forum: Unknown property in EditorSettings file - PBIP Dataset. The original post, and the reply marked as the solution. Read 2026-10-03.
- [2]GitHub issue: microsoft/json-schemas issue 656. The issue description, "Actual result" and "Analysis". Read 2026-10-04.
Did this page help?
It tells us which pages to fix first.