Conditional Formatting using Calculated Column as Condition (SharePoint Designer 2010)

Question

I want to use conditional formatting to change the color of a row based on a Calculated Column. I know I could do this with a CEWP but I would prefer to do it in SPD 2010 because I am new to programming and another non-programmer may be tasked to maintain this later.

The calculated column has values from -1 through 5 and I want to grey out everything that is less than 1. The "type" of the calculated column is "Number" in Column Settings.

Condition for formatting:

Style to be applied:

I get no result. Same if I change the comparison to be IsNull or anything else. The conditional formatting works fine when I use other columns for the comparison. e.g. Condition for formatting is "Preferred Setting" (a choice column) equals "One-on-one" (one of the choices).

Is there anything special I can do to allow SPD to interpret my Calculated Column and use it for formatting?

Answer 1

Even though your calculated column has the correct type ("number") in SharePoint, you may need to explicitly cast the variable to type number. That's much easier than it sounds.

Do the following in SPD:

1. Setup your condition and style the way you want them
2. Go into Code view and look for <xsl:attribute name="style">
3. Change your condition from <xsl:if test="$thisNode/@_x0023__x0020_Available_x0020_to. = 0" to <xsl:if test="number($thisNode/@_x0023__x0020_Available_x0020_to) = 0" (wrapped the field name in "number()" and omitted the "." at end of field name)
4. Save and refresh

Thanks for updating your question. Hope my solution works for you!

Answer 2

I wanted to give an additional answer - since I had the exact same question as stated by the O.P. - but my problem turned out to be of a completely different nature...

Initially, my conditional formatting logic (an advanced expression) - at the point I made it depend on a calculated column, it seemed to stop working.

However, the actual culprit wasn't the calculated column, itself. The conditional logic didn't actuate because the calculated column had to first be added to the list of visible fields (which, I think is a lame requirement)