Skip to main content
Solved

Cube Conditional Formatting only applies to cell level when the 'Condition on' column is visible

  • January 22, 2026
  • 5 replies
  • 61 views
Mark Poorthuis
Apprentice
Forum|alt.badge.img

 TL/DR: I’m experiencing unexpected behavior regarding Conditional Formatting within the Universal Cube. Formating is applied to the entire row, is was expecting it to only apply to the cell.

 

The Setup: We use a Cube to visualize supply and demand per week.

  • Quantity < 0: Shortage so Red background.

  • No. of notes > 0: Yellow background on Quantity Value

The Issue: The formatting logic changes based on the visibility of the field used for the condition (No. of notes):

  • Field Visible: The formatting works perfectly. Only the specific cells (intersections) containing a note are highlighted in yellow.

  • Field Hidden: When I remove the No. of notes field from the Cube view (but keep it in the Cube definition), the entire row turns yellow if there is at least one note anywhere in that row.

Tried:

  • Setting No. of notes field width to 0 or -1.

  • Moving No. of notes from Value to Dimension

  • Toggling all 'Apply to' checkbox combinations.

  • Removing all other layout conditions to isolate the bug.

Environment:

  • Platform version: 2025.3

  • Universal GUI version: 2025.3.14.0.0

Is this a known limitation/bug, or is there a specific configuration to keep cell-level formatting while hiding the ‘Condition on’ value?

 

 

Best answer by Sebastiaan Meijerink

​@Mark Poorthuis, I’m sorry, I was thinking with the limitations of how it currently has to fetch the data in my mind. And must admit, I did not know that the windowGUI would be able to answer this question as it does. 

I looked into it, and Universal actually tries to add the field to the Pivot as if it were on it and then hides it, so if it is working when the field is on the Pivot as a value, there is something wrong in this strategy.

Since the Windows GUI does manage to resolve this, I think we should treat this as a bug for sure.

 

 

 

Enabling your low-code solutions

5 replies

S
Moderator
Forum|alt.badge.img+2

Hi Mark,

This is expected because the cells you are looking at are grouped aggregations. So your cell is not the same as a field in a table.

The ‘row’ you are looking at is always a form of an aggregation, and so are any fields you put the conditional layout on. 

Let's assume we are looking at the ‘row’ variety x, and we have multiple periods. 

This row is the outcome of a query that says;

groupBy variety, period, sum Quantity 

The data behind quantity is made up of multiple rows, so when you say make this yellow when No. of notes > 0, from what row should this no of notes come from? The pivot does not know this and will thus add this field as MAX when it is a dimension or as the aggregate of the value if it is a value. That means that this will be true as soon as 1 of the variety rows sum of no_of_notes is bigger than 0, it will be colored. 

Actually, adding that as a series or category, the pivot makes a whole different question, because it will become part of the grouping!

As a dimension;

groupBy variety, no_of_notes, period, sum Quantity 

Will give a Quantity per no_of_notes. And there will be a unique relationship between the 2.

But as soon as no_of_notes is not part of the grouping or the actual values, it will be aggregated on top of the grouping. There is just no other way to answer the question “color Quantity when  No. of notes > 0,” in the queries behind the pivot.

Sebastiaan

 

 

Mark Poorthuis
Apprentice
Forum|alt.badge.img

Thnx for your quick reply, excellent!

After reading your reply i kept staring at it… my brain isn't registering what you are trying to explain. After running it trough ChatGPT i understand what you mean but yeah, no, i'm not buying it.

I see 2 problems with your explanation:

  1. The windows GUI is doing exactly as expected, Universal isn't. So your message starting with ‘This is expected because...’ seems a bit odd. 

  2. If i drill down on the cells in the pivot table, only the ones i expect to have a yellow background have a value for [No. of notes]. So the cube knows exactly which cell ‘has a note’ and which cells don't

Is this 'cutting wood'? 🙂

I'm really hoping for this to be classified as bug / unexpected behavior or at least as an idea for the Universal GUI (and windows GUI parity).

 

Windows GUI:

Universal GUI
Drill down on cell that should be yellow (see last column)

Drill down on cell that shouldn't be yellow

Drill down on empty cell that shouldn't be yellow

 

Enabling your low-code solutions
Mark Poorthuis
Apprentice
Forum|alt.badge.img

I just now noticed one of my screenprints was missing in my original post… very strange, i'll add it here:

 

Yellow background working whenever the ‘Condition on’ column is visible:

 

Enabling your low-code solutions
S
Moderator
Forum|alt.badge.img+2

​@Mark Poorthuis, I’m sorry, I was thinking with the limitations of how it currently has to fetch the data in my mind. And must admit, I did not know that the windowGUI would be able to answer this question as it does. 

I looked into it, and Universal actually tries to add the field to the Pivot as if it were on it and then hides it, so if it is working when the field is on the Pivot as a value, there is something wrong in this strategy.

Since the Windows GUI does manage to resolve this, I think we should treat this as a bug for sure.

 

 

 

Mark Poorthuis
Apprentice
Forum|alt.badge.img
  • Mark PoorthuisApprentice
  • Author
  • Apprentice
  • January 23, 2026

Thnx for your reply and good to know we are on the same page! 

Do you want me to create a Bug in TCP?

Enabling your low-code solutions
Terms & ConditionsCookie settingsAccessibility statement