Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
2 years ago

Unexpected parquet exception occurred. Class: 'ParquetStatusException'

Hi I am getting errors on my power bi desktop app and web published versions. Its connecting to Azure Data Warehouse through a dataset though even if I create a new report and connect direct to ware...
Dataflow
Need Help
blalonde's avatar
blalonde
Regular Visitor
2 years ago

I'm facing the same error but a different experience. Running through the Fabric tutorial here to create a data warehouse. The problem lies in creating the report visualization. Dragging SalesTotal from the FactSalesOrder table works fine. Dragging Category from the DimProduct table causes the error message. I've verified that data is in the table via the Warehouse explorer in Fabric as well as in OneLake via Azure Storage Explorer. I've also created a new workspace and went through the same steps only to run into the same issue.

 

Steps to repro:

Starting at Create tables and insert data:

  1. Create DimProduct table
  2. Insert sample data
  3. Run new query with GitHub MSFT Learning warehouse txt file SQL script
  4. Follow instructions to properly model data (make connections in the Model view)
  5. Go to Visualize your data section
  6. Follow instructions to create a New Report
  7. When dragging clicking category to add to view, the error will occur.

One thing I haven't tried was skipping steps 1 and 2 in the repro steps and just using the SQL Script as it contains code to drop and recreate that table with the original values (as well as some new ones). Though that shouldn't make a difference.

 

Update: After reviewing my model, I noticed that additional relationships were automatically created. (See image)

They link on the same keys but start in the opposite direction e.g., DimCustomer -> FactSalesOrder -- with Assume Referential Integrity turned on. I removed these relationships, went back to Power BI, clicked SalesTotal (ok), clicked Category (error again), went back to my Model view and those relationships had reappeared! What gives?!

  • jhaines's avatar
    jhaines
    Frequent Visitor
    2 years ago

    I encounted the same error doing the MS Fabric labs. I ended up:

    • deleting the whole data warehouse
    • create a new v2 data warehouse
    • skip entering data manually and just put in the SQL script to create the 4 tables with data.
    • I was then able to create the correct relationships

    However, I did continue to run into random errors (in the visual editor and when hiding columns). I hit refresh a couple times, deleted and readded things, and got things to work.

     

    Overall, it was very buggy. Hope it gets resolved soon because dropping a whole data warehouse in real life is more of an undertaking than during a lab.