DAX Queries, Part 6

Before I start this post, I’d like to mention that Cathy Dumas of the dev team has started blogging on BISM topics here: http://blogs.msdn.com/b/cathyk/. There are some good posts up already, with more to come I’m sure.

Anyway, back to DAX queries. Just a quick post today about the ROW() function, which returns a table containing a single row of data. Here’s an example of its use inside a query:

evaluate(
row(
"Column 1"
, "Some text"
, "Column 2"
, countrows(dimdate)
)
)

image

It’s pretty simple: the parameters represent a series of column name/DAX expression pairs for your table, so in this example I’m defining a table with two columns and one row, with the first column returning the text “Some text” and the second column returning the result of the expression countrows(dimdate). I understand it is intended for use by client tools such as Crescent when they want to return a series of grand totals without any detail data.

5 thoughts on “DAX Queries, Part 6

  1. Hi chris ,

    I know that this is not right thread to post this ..But i want you to please clarify one issue ..
    i have a cube bulid using SSAS . But in each dimension of it i am getting a attribute called “unknown” .I dont have null values in those dimensions for SSAS to convert them to “unknown” ..
    When i had seen the dimension properties of that dimension there is a property called UNKNOWN MEMEBER.
    that property was set to true .If we change that to none UNKNOWN MEMBER issue would be solved , But what is confusing me really is , How that UNKNOWN members is getting generated when the dimension is not having null values for any of the attributes..?..

    Hope i am clear in explanation ..

    1. Hi Rajesh,

      The Unknown Member is created automatically, whether there are any missing key values or not. As you said you can hide it, so there’s no need to worry about it.

      Chris

Leave a Reply to RajeshCancel reply