Forum Discussion

Simonn97_PBI's avatar
Simonn97_PBI
Advocate I
1 year ago

Required properties are missing from object

Hi,

When I turned on the performance analyzer, I encountered a problem because no data could be refreshed. I then saved the file and tried to reopen it, but I received an error with the following message:

 

Error Message:
'pages/f9c803511e9a398c884a/visuals/f424378be848e9625e78/visual.json':
Required properties are missing from object: name. Path 'filterConfig.filters[2]', line 342, position 7.

 

I then found the line with the error and tried to fix it, but unfortunately it didn’t work, and I’m unable to open the file (it wasn’t shared in Power BI Service, so I can’t download it either).

The line with the error is at 342,7.


{
"field": {
"Column": {
"Expression": {
"SourceRef": {
"Entity": "fctCombinePNL"
}
},
"Property": "reporting_market_desc"
}
}
}
]
}
}


Thanks

6 Replies

  • Hi Simonn97_PBI - Here , error indicates that your Power BI file (PBIX) contains corrupted metadata, specifically in the JSON configuration for one of the visuals. The issue is related to a missing required property (name) in the visual configuration. Since the file cannot be opened in Power BI Desktop, you'll need to fix it manually by extracting and repairing the file.

     

    Backup Your File

    Make a copy of the corrupted .pbix file to ensure you don't lose any data during the repair process.
    Rename the File Extension

    Change the file extension from .pbix to .zip. Power BI files are internally structured like ZIP archives.
    Extract the File

    Extract the ZIP file using a tool like WinRAR, 7-Zip, or a similar application.
    Locate the Problematic File

    Inside the extracted folder, navigate to Report/Layout (or similar, depending on the version of Power BI). This file contains the JSON configuration for the report visuals.
    Edit the JSON File

    Open the Layout file (you might need a text editor like Notepad++ or VS Code).
    Navigate to line 342, position 7, as indicated in the error message.
    The issue seems to be with the filterConfig.filters[2]. The correct JSON structure for this filter should include a name property. Add the missing name field to the object.

    Avoid editing PBIX files directly when Power BI Desktop is open.
    Regularly save your work and maintain backups.
    Publish reports to Power BI Service as a backup method.

    • Simonn97_PBI's avatar
      Simonn97_PBI
      Advocate I

      Thanks for the response. Generally, I've carried out most of the steps you described, but I'm not sure where to add the 'Name' data in the .json file. I tried different places, but when I save the file again, it turns out to be corrupted


    • rajendraongole1's avatar
      rajendraongole1
      Super User

      Hi sigma_pbi - can you please check the corrected strucuture

       

      {
      "pages": [
      {
      "id": "f9c803511e9a398c884a",
      "visuals": [
      {
      "id": "f424378be848e9625e78",
      "visualType": "table",
      "visualJson": {
      "filterConfig": {
      "filters": [
      {
      "name": "reporting_market_desc_filter", // Add 'name' here
      "field": {
      "Column": {
      "Expression": {
      "SourceRef": {
      "Entity": "fctCombinePNL"
      }
      },
      "Property": "reporting_market_desc"
      }
      }
      }
      ]
      }
      }
      }
      ]
      }
      ]
      }

    • panna27's avatar
      panna27
      Regular Visitor

      Hi Rajen,

      Do you know why this corruption in the JSON file can occur? I am facing the same issue and followed your steps but I would like to avoid this happening in the future and don't know how.

      Thanks in advance!

  • rajendraongole1 - I've stumbled onto this issue myself more than once.  I've been able to revert back to a previous version of the file (using source control), but this time I'm not able to.  Seeing what appears to be the same issue as OP.

    I've been looking online for a while but cannot find reference to anything related to this other than this post.

     

    Are you able to share a sample of the correct JSON structure to fix this?