Derived Attribute is the New Custom Group

By -
There’s always delicate balance, when developing a MicroStrategy Schema, on when to know to build an auxiliary object in MicroStrategy and when to push that work to the ETL/Database.


Most of us must have faced situation when there is need of virtual attribute and Database developers are busy to provide attributes in desired format directly in database or business requirements are different for one particular user or group.



In this situations we generally opt for Custom groups which impacts performance drastically.
Ø  Each Custom Group element is a separate filter and generally creates a separate pass of SQL.
Ø  Multiple Custom Groups on a report end up multiplying by each other in regards to the number of passes of SQL.  So if you have a Custom Group with 10 elements, and a 2nd Custom Group with 10 elements, that’s 100 passes of SQL times however many passes the Metrics on the report create.


With 10 version of MicroStrategy, we can create derived attribute to address requirements which can be accomplished with custom groups. Potential of powerful analytical engine is used in correct way.


Note: Derived attributes can’t be created if dataset contains custom group. I am not sure about the logical reasoning behind this but I think MicroStrategy don’t want to keep two swords in same scabbard J


Below are steps to create Derived attribute with if or Case condition.
http://www2.microstrategy.com/producthelp/10/WebUser/WebHelp/Lang_1033/Derived_attributes_HTML5.htm

1
1)    Select relevant dataset and click create attribute.























2.Determine the attribute form on which if condition needs to be applied.
3. If attribute form is missed or incorrect attribute form is used, you will get syntax error.
4. Use below syntax to create attribute with IF Condition
     If([<attribute name>]@[<attribute form>] <Condition>,”True Value”,”False Value”)


Example IF:


        Consider report with country, region, city and revenue
         You have below requirement.


Zone
Region
High
Central
Mid Atlantic
NorthEast
Low
Rest of the Regions




Attribute form for Region is ID




Output would be :
















  1. Use below syntax to create attribute with Case condition:
    Case (Condition1, ReturnValue1, Condition2,ReturnValue2,..., DefaultValue)
    For Example:

Zone
Region
High
Central
Mid Atlantic
NorthEast
Medium
South
Southeast
Southwest
Low
Rest of the Regions

Case (Region@IDin(4, 2, 1), "High", Region@IDin(5, 3, 7), "Medium", "Low")


Output:

        



Note: Apply simple can be also used  to achieve same but this option will involve access to developer and architect role
                                                                       


Comments

Post a Comment

Popular posts from this blog

The count distinct adventure - Part I

By -
Image
I've been working with several reporting and data analysis tools for a while now. Started with SSAS cubes, then Business Objects came along, later, MicroStrategy (MSTR) joined the team and then Tableau. They all have their own ways of managing count distinct (CD), but they yet have more in common. Manage simply means yielding the good results every time a user interacts with that CD measure. Us, the BI tech guys, we have a goal to facilitate easy data analysis to the users, especially that most of them work in non-IT domains and have different skill levels. Throughout time, CDs have proved to be a difficult thing to manage and if it wasn't the ease of implementation, it was the performance impact we soon discovered. It's been known that the difficulty lies in the nature of this non-additive measure. Basically, we cannot sum it as a standard revenue measure, but you always have to re-calculate it when the level of the aggregation changes. Have to admit that I like a goo...
Read more

The surrogate key strikes back

By -
If you ever participated in building a data warehouse or worked around data warehouses, you've probably came across the surrogate key (SK) notion. If you’re not familiar, then take a look at this article on the Kimball's group website. Surrogate keys are very common in data warehouses and they bring a lot of functionality, from design to performance enhancements. Now, one of the surrogate key's drawbacks is the difficulty to keep it in synch between all environments. As each environment can be linked to a different version of the source (e.g. UAT, live environments etc.), surrogate keys can get off for the same natural key and this can also have an effect in MicroStrategy. When building attributes you have to define its forms. The ID form should contain a unique key describing the attribute in order to provide correct joining, aggregation and attribute member list when applying filters. Indeed the surrogate key doesn’t have any business meaning, so this form w...
Read more

The count distinct adventure - Part II

By -
During the first part of the topic we introduced the challenge of count distinct and 2 solutions to address them, along with their advantages and disadvantages. The list of solutions continues in this final section and these, presented below, are also the solutions that we use across our projects where CDs are required. Solution 3 - Count Distinct derived metrics This functionality is probably the most known by the users and mostly used, as it offers flexibility and the necessary control without the intervention of the IT teams. Creating =derived metrics in reports, Vis and documents is a walk In the park, using the context menus. With the deployment of V10, things got even more flexible adding support for conditional derived metrics (IF and CASE) by using attributes directly. As you probably remember, or still use today, up until V10, building conditional derived metrics was a hustle, as only metrics could be used with IF and CASE statements. You would first create a MAX(<...
Read more