Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
8 years ago

AutoSave leading to File contains corrupt data?

I had this now 3 times in a row, with different source files. When I edit a source file in a SharePoint library and AutoSave is on, upon refreshing the Power BI I get an error: File contains corrupte...
General Comment
v-chuncz-msft's avatar
v-chuncz-msft
Community Support
8 years ago

Anonymous,

 

To get a better explanation for this issue, you may create a support ticket.

Anonymous's avatar
Anonymous
Not applicable
8 years ago

I made some progress with my investigation and here my findings:
When I get the "File contains corrupted data" error when refreshing a report, I first check if the file opens (from the SharePoint library) in Auto-Save mode. If yes I switch Auto-Save off. If it isn't or if switching it off doesn't make a change, I use the File, Check for Issues, Inspect Document option and remove everything. This fixes it in most of the cases, but I had one case so far where it didn't.

 

When checking the query steps, I found this one

= Table.SelectRows(#"Filtered Rows", each [Attributes]?[Hidden]? <> true)

 

Which was added automatically. What is causing this step to be added between "Filtered Rows" and "Invoke Custom Function" when combining binaries? I removed that step and refreshed the query - file no longer contains corrupted data!

  • Anonymous's avatar
    Anonymous
    Not applicable
    8 years ago

    Now the error is back, with the same file, which had NOT been modified since in the SharePoint library where it resides.
    It's not in Auto-Save mode.
    The inspector does not find any metadata, hidden XLM data, etc. that could be removed.
    The "Filter hidden files" step is not present in the query.

    This is frustrating. How do I troubleshoot this? The file is definitely ok (well, I assume so because it worked fine last time and the file hasn't been modified since then). Thanks for any pointers!