Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
7 years ago
Solved

Unable to Remove Errors

I have a table which contains time-series data. I have errors appear in some rows, however don't seem to be able to remove them. I have tried Remove Errors, Replace Errors and Replace Values. I've even tried modifying my Power Query code to use 'Table.RemoveRowsWithErrors', however nothing seems to work. 

 

Any ideas how I can remove these rows containing Error?

I am using the latest version of Power BI.

Need Help
  • Anonymous's avatar
    Anonymous
    7 years ago

    I have solved this by moving the Table.RemoveRowsWithErrors() function to an earlier point in my Power Query, where the errors appear as single cells in one column (rather than expanded out to an entire row).

7 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    7 years ago

    I have solved this by moving the Table.RemoveRowsWithErrors() function to an earlier point in my Power Query, where the errors appear as single cells in one column (rather than expanded out to an entire row).

    • Anonymous's avatar
      Anonymous
      Not applicable
      6 years ago

      Same for me. Tried remove, replace errors, identifying them with try, etc. The Table.RemoveRowsWithErrors() function needs to be immediately after Source. Any later and it will not work.

      • kagy100's avatar
        kagy100
        Advocate II
        5 years ago

        This works . . .Removing Errors immediately after Sources fixes the problem. Thank You.

  • adityavighne's avatar
    adityavighne
    Continued Contributor
    7 years ago

    Anonymous 

    Just filter the data in by "Error" in edit query and then load/refresh the report.

    • Anonymous's avatar
      Anonymous
      Not applicable
      7 years ago

      Unfortunately this still did not work.

      • 21818's avatar
        21818
        Frequent Visitor
        6 years ago

        Hi!

         

        I solved this by changing the API version during the data loading. I was using API version 14 and after changing this to v15 this error row was no longer there.

         

        Somehow it's strange as I using in the same file v14 for other locations with no issues. 

         

        Hope it helps.