Project

General

Profile

Actions

Bug #894

open

Boolean data type shows incorrect aggregation functions compared to Power BI

Added by Maryam Farooq 3 months ago. Updated 20 days ago.

Status:
Waiting for Regression
Priority:
High
Assignee:
Target version:
-
Start date:
01/29/2026
Due date:
% Done:

100%

Estimated time:
Spent time:

Description

Bug Description

When a Boolean data type field is used in Prism, the available aggregation options do not align with standard BI behavior or Power BI results.

In Power BI, Boolean fields support only Count and Count Distinct aggregation functions. However, in Prism, all aggregation functions (SUM, AVG, MIN, MAX, etc.) are displayed for Boolean data types, which leads to incorrect or misleading aggregation options for users.

This inconsistency can cause confusion and incorrect visualization or summary results when working with Boolean fields.

Actual Result

Prism displays all aggregation functions for Boolean data type fields.

Aggregation options such as SUM, AVG, MIN, MAX are selectable for Boolean fields.

Behavior does not match Power BI or expected BI standards.

Expected Result

For Boolean data type fields, Prism should display only valid aggregation functions, such as:

Count

Count Distinct

Aggregation function availability should match Power BI behavior and standard BI tool practices.

Invalid aggregation functions should be hidden or disabled for Boolean data types.


Files

Actions #1

Updated by ALi RAZA 3 months ago

  • Status changed from New to In Progress
Actions #2

Updated by ALi RAZA 3 months ago

  • Status changed from In Progress to Todo
Actions #3

Updated by ALi RAZA 3 months ago

  • % Done changed from 0 to 40
Actions #4

Updated by ALi RAZA 2 months ago

  • Status changed from Todo to In Progress
Actions #5

Updated by ALi RAZA 2 months ago

  • Status changed from In Progress to Resolved
  • % Done changed from 40 to 100

Boolean data type fields were showing all aggregation functions (SUM, AVG, MIN, MAX, etc.) which is incorrect behavior. Power BI only allows Count and Count Distinct for Boolean fields.

What We Fixed

Before (Wrong):

  • Boolean fields (TRUE/FALSE, Yes/No) were classified as Measures
  • All aggregation functions were available (SUM, AVG, MIN, MAX, COUNT, etc.)
  • Users could select invalid aggregations for Boolean data

After (Correct):

  • Boolean fields (TRUE/FALSE, Yes/No) are now classified as Dimensions
  • Only valid aggregation functions are available: Count, Count Distinct
  • Behavior now matches Power BI standards

How It Works Now
Field Type Classification Available Aggregations
TRUE/FALSE, Yes/No Dimension Count, Count Distinct
Numeric (0, 1, 100...) Measure SUM, AVG, MIN, MAX, COUNT
Text (Names) Dimension Count, Count Distinct

Result

  • Boolean fields now behave exactly like Power BI
  • Invalid aggregation options are no longer shown for Boolean data
  • Users will see correct and meaningful aggregation choices
  • No more confusion or misleading results when working with Boolean fields
Actions #6

Updated by ALi RAZA about 2 months ago

  • Status changed from Resolved to Ready For QA
Actions #7

Updated by ALi RAZA about 2 months ago

  • Status changed from Ready For QA to Resolved
Actions #8

Updated by Fareena Anayat about 1 month ago

  • Project changed from 16 to Prism Release 2
Actions #9

Updated by ALi RAZA about 1 month ago

  • Status changed from Resolved to Ready For QA
Actions #10

Updated by Fareena Anayat 20 days ago

  • Status changed from Ready For QA to Waiting for Regression
Actions

Also available in: Atom PDF