Forum Discussion

KateEC's avatar
KateEC
Frequent Visitor
8 years ago

Query Filter Not Showing Values

Hi All,

 

I am currently trying to filter my data in the query editor using the drop-down arrows on the column to filter out certain (text) values. However, when I do this, not all the options are showing in the filter. 

 

When I click on the drop-down arrow, all the values that are in the list are show and ticked (as in they are included in the column). But when I click on Text Filters and try to filter these using Equals/ Does Not Equal, it only shows me about 5/6 out of 7 of the values that are in the list. The values are all text-strings and are formatted as text if that helps.

 

I have also tried the "Load More" option to ensure that the correct values have been loaded for the filter.

 

This is meaning that I cannot get any further with my report as it is preventing me from using certain formulas for my calculated columns.

 

Does anyone know why this might be happening?! For the life of me, I cannot see why!

 

Thank you so much in advance! :) 

Need Help

3 Replies

Replies have been turned off for this discussion
  • v-juanli-msft's avatar
    v-juanli-msft
    Community Support
    8 years ago

    Hi KateEC

    It is werid as I test but can show all values in Text Filters.

    Please make sure these values are all in text format.

    Additional, a workaroud to filter text in Power BI is introduced as this article.

     

    Best Regards

    Maggie

    • KateEC's avatar
      KateEC
      Frequent Visitor
      8 years ago

      Hi - thanks so much for your help  v-juanli-msft :)

       

      I have checked and the values are formatted as text, but unfortunately it still isn't working :/

       

      The article is useful, but I was hoping to filter at data table level like in PowerPivot - this seems such a basic feature for Power BI to be missing!

       

      Oh well...! c'est la vie!

  • Anonymous's avatar
    Anonymous
    Not applicable
    7 years ago

    Hi KateEC 

     

    I had a very similar issue. It turned out to be caused by a calendar filter, which by default has a connection with an incorrect column. I solved the issue by creating a new table with a correct relationship.