Comments on: Report Builder and Text-based Calculated Members https://prologika.com/report-builder-and-text-based-calculated-members/ Business Intelligence Consulting and Training in Atlanta Wed, 17 Feb 2016 11:48:01 +0000 hourly 1 https://wordpress.org/?v=6.9.1 By: tlachev https://prologika.com/report-builder-and-text-based-calculated-members/#comment-82 Sun, 11 Mar 2007 13:10:42 +0000 /CS/blogs/blog/archive/2007/03/09/report-builder-and-text-based-calculated-members.aspx#comment-82 Yes, it will be nice to have the same capability as the Report Designer, e.g. FormattedValue property. Conditional formatting is a must-have too.

]]> By: furmangg https://prologika.com/report-builder-and-text-based-calculated-members/#comment-81 Sat, 10 Mar 2007 18:51:16 +0000 /CS/blogs/blog/archive/2007/03/09/report-builder-and-text-based-calculated-members.aspx#comment-81 Well put, Teo. I’ve run into this issue before on a calculated member which has different format strings depending on what slice of the cube you look at it. That’s because the calc script uses the Format_String(this)=”#,#” syntax to customize the format string for different slices of the cube.

The only way I could figure out to tackle this is to do what you suggested… change the XML of the report model like you said… and then make the calculated measure spit out a string with the formatted value.

I think the ultimate solution to this problem is in having Report Builder support per-cell, not per-field calculated measures. If you agree, you might vote for:
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=225085

]]>