Hi Palash, sorry for the delay. I did start looking at this, but a number of other priorities have take precedence so I thought I should give you a quick update.

There are 2 issues here 1 is that Translations is not a single attribute. There is a whole hierarchy of elements under Translations and changing the code to accommodate flattening out intermediate structures like this would be quite difficult. The only work around I can think of at the moment would be to look at 2 queries, maybe via a linked server to get the name column source and translation information separately and then join them in your reporting layer.

The other information is the AttributeHiearchyDisplayFolder - this is an optional property and the current code builds the structure of the resultset based on the first object it finds, so if an optional property does not have a value in the first object it never generates a column for this. I will need to look at the code to see if I can fix this.

Thank You Dgosbell! I was looking for the DimensionName in cube and the SQL table behind the dimensions. Attribute name and the SQL column behind it, Display folder, visibility, translations and the same for all measures / measure groups. Please let me know once you fix this or if you come across a work around to get all of these in a single query.
My email id is palashaich@gmail.com

Regards,
Palash