Forum Discussion
Desktop work, but error in WorkSpace: File contains corrupted data [...]
Hi L_trainee I think your next steps will help pinpoint the issue. Converting the files to CSV and inspecting them with a notebook can reveal hidden inconsistencies like invalid characters or formatting issues. Creating a separate query for these files will allow you to test their compatibility with Power BI Service independently. If merging works after isolating the issue, it confirms the problem lies in file structure or formatting.
Hi L_trainee It might be caused by subtle data or formatting issues in Excel files that Power BI Service handles more strictly than Desktop. Check files added after April 17th for hidden inconsistencies like merged cells or date anomalies. Test these files individually to find the problematic ones.
Hey Akash_Varuna , thank you for your answer!
That's the thing: I already identified problematic files, but I can't seems to find any difference while comparing them manualy to previous data.
At this point I'm afraid of excel shenanigans with the data (especially dates fields).
My next steps will be:
- Save the files as .csv and open them with a notebook-style software for manual comparison.
- Create a different query just for these files (and merge it with the previous ones) and see if this somehow solve the issue?
Any advice to compare the two data types?
Hi L_trainee I think your next steps will help pinpoint the issue. Converting the files to CSV and inspecting them with a notebook can reveal hidden inconsistencies like invalid characters or formatting issues. Creating a separate query for these files will allow you to test their compatibility with Power BI Service independently. If merging works after isolating the issue, it confirms the problem lies in file structure or formatting.