Display folders are an often used tool in Analysis Services to help end users navigate through a cube or dimension they could find what they need to build a report. Imagine you develop a cube that has dozens of measures. For an end user to find what they need they would be forced to dig through every measure. If an end user gets lost while trying browsing the cube they are a lot less likely to continue using it.
This is where display folders come in handy. They make it easy for end users to find what they need and I’ve learned a few tricks with them that make it even easier for user to find what they need.
Whether it is a measure, calculation or attribute you can view the properties and give the object a display folder as shown below.
When the user browses the cube now there will be a folder that makes it easy to find measures when organized properly.
Now most people that have developed Analysis Services cubes already know about display folders but the little piece I have to add here is how to nest folders and how one item can be in multiple folders.
To put a measure or an attribute in a nested folder you provide a folder name like this:
Folder1\Folder2
To put a measure or an attribute in multiple folders you provide a folder name like this:
Folder1;Folder2
I hope this helps make life easier for you and your end users so they can find what they want faster when building reports off your cube.
Hi This article is more useful but i am not able to find the display folder property to an attribute. I can see that only for a measure?
Am i missing something here? Please suggest.
Yes this is something that’s only available for Measures and not in Dimension Attributes.
That’s incorrect. The very first line item you see when you open the Properties for an attribute defined in a dimension is this following text… .
This is where you would be applying the help found in the article above.
marko
The text got truncated. The field is called AttributeHierarchyDisplayFolder.
This post is from 2011 using SQL Server 2008 R2, it’s possible the property name has changed in newer versions of the tool.
it has not 🙂