http://www.sqlmag.com/authors/author/author/5777661/rsscomment/5777661en-USFri, 25 May 2012 08:57:26 GMTFri, 25 May 2012 08:57:26 GMThttp://www.sqlmag.com/article/reporting2/following-the-rules-with-reporting-services#commentsAnchorThu, 22 Mar 2007 01:52:22 GMT
Seems like there would be an easier way to do this. Why not just put an expression in the Visibility property and skip the extra code block altogether. For the parameter, use the level.ordinal field in the dataset as the value of the parameter, and then use something like this in the Visibility property... IIF(Parameters!Geography.Value <= Fields!RowLevel.Value, False, True) where Fields!RowLevel.Value would be the rowlevel of that row in the report. The only reason I can see for the extra work in this articles solution would be to try to isolate the code used in the visibility property so it can be used in other places and if modification needs to be done it can be done in one place. Still, in a report this is not really needed. Reports tend to be simple enough (even the complex ones) that it is not necessary.]]>RichardThu, 22 Mar 2007 01:52:22 GMThttp://www.sqlmag.com/article/reporting2/following-the-rules-with-reporting-services#commentsAnchorhttp://www.sqlmag.com/article/reporting2/following-the-rules-with-reporting-services#commentsAnchorThu, 22 Mar 2007 01:52:22 GMT
Seems like there would be an easier way to do this. Why not just put an expression in the Visibility property and skip the extra code block altogether. For the parameter, use the level.ordinal field in the dataset as the value of the parameter, and then use something like this in the Visibility property... IIF(Parameters!Geography.Value <= Fields!RowLevel.Value, False, True) where Fields!RowLevel.Value would be the rowlevel of that row in the report. The only reason I can see for the extra work in this articles solution would be to try to isolate the code used in the visibility property so it can be used in other places and if modification needs to be done it can be done in one place. Still, in a report this is not really needed. Reports tend to be simple enough (even the complex ones) that it is not necessary.]]>RichardThu, 22 Mar 2007 01:52:22 GMThttp://www.sqlmag.com/article/reporting2/following-the-rules-with-reporting-services#commentsAnchorhttp://www.sqlmag.com/article/quering/april-2002-mdx-puzzle-solution-revealed#commentsAnchorTue, 19 Apr 2005 15:26:09 GMT
"NULL" doesn’t seem to work for any MDX query I do.]]>Anonymous User Tue, 19 Apr 2005 15:26:09 GMThttp://www.sqlmag.com/article/quering/april-2002-mdx-puzzle-solution-revealed#commentsAnchor