Incorrect Summary Row Whenever Filter Is Applied

Incorrect Summary Row Whenever Filter Is Applied

This article will address the following issue:

Data in the summary row for Unique fields is incorrect whenever a filter is applied in Looker Studio.



This bug only affects Unique fields.


Cause

This is an issue with Looker Studio and Google Sheets that has not yet been resolved by Google. 





    Still having issues?
    Send us a ticket and we will get back to you.
      • Related Articles

      • Looker Studio Summary Row Errors When Using Filters

        Issue When a Looker Studio query includes both a filter and a summary row, the summary row displays incorrect data or no data. Instead of showing totals, it may report the first result from the data source for each column. Cause This error occurs ...
      • Looker Studio: Grand Total Over a Date Range is Less Than Sum of Individual Rows Broken Out By Date

        This page will assist you with the following issue: When reporting individual values by date in Looker Studio, the sum of these individual values over a date range may be less than the grand total of the values over the same date range. For example, ...
      • Reach And/or Frequency Not Working in Pinterest Ads Report

        This article will address errors in Pinterest Ads reports that include Reach and Frequency. Reach or Frequency data may be incorrect when the report covers a time frame of more than 185 days (approximately 6 months). Cause Reach and Frequency are ...
      • Incorrect Inventory Numbers from Amazon Seller

        This article will assist with the following problem: Inventory numbers in an Amazon report are bloated or incorrect. Cause The most common cause of this problem is a missing marketplace dimension or filter. Even if you configure your account to ...
      • Instagram Insights Posts Data is Inflated

        This article will help to resolve the following problem: ​ An Instagram Insights report shows data for posts that does not align with the data shown in Instagram's own analytics. Cause Most of the time, our customers find this error in Google Sheets ...