I work with MSTR for a while (on a daily basis), already went through a few courses, symposiums and etc... and this video is the most easy-to-learn/full-of-examples tutorial I saw about level metrics so far... congrats!
Thank you so much! I'm glad you found the tutorial helpful. If you think of any other topics I should cover, please let me know. I'm always open to new ideas and feedback. :)
Hi James, Thanks a lot for this video, Level metrics is little tricky,and Hard to understand but your video made it easy to understand. A request if possible can you make a video on leave metrics for derived metrics Thank you.
Hi James Very happy bv to see your videos ....I am trying to learn MicroStrategy developer tool for changes please help us with u r informative videos.
If you are asking me how to resolve, the issue could be a relationship that is not defined within your attribute. That is the first place I would check. So for example, if you have a time hierarchy and you are trying to aggregate data that exists at the day level up to month, you will need to define in month that it has a one to many relationship with day so the SQL engine knows how to query the attribute. Make sense?
Hai thanks for video..can u please differentiate between automatic and manual in creating a attribute. which is the better way . Can u give me an example. And what's the difference in creating an attribute in architect view and simply creating with attribute editor
Hi James this is ok but could you please explain in detail it seems 16 minutes is not sufficient so if you extend this session to up 1 hr or beyond that also fine .Appreciate your trainings and dedication on this .
yes all attributes on report template and in report objects. In fact you can add attributes to the report objects but leave off the grid to force the sql to calculate at a certain level.
I have one question.I was creating attributes and when i used to add attributes in a report without forming a parent child relationship,I would get cross join.Today,when i removed the parent child relationship and tried to execute the report, i did not have any issue at all.Please help why is this happening.
It depends if the attribute is already on the fact table. If the attribute can be found on the fact tables then you dont need a relationship but if mstr has to join to another table to get the attribute then you need a relationship. This is the simple rule of thumb answer.
I work with MSTR for a while (on a daily basis), already went through a few courses, symposiums and etc... and this video is the most easy-to-learn/full-of-examples tutorial I saw about level metrics so far... congrats!
Thank you so much! I'm glad you found the tutorial helpful. If you think of any other topics I should cover, please let me know. I'm always open to new ideas and feedback. :)
This is the simplest way someone has explained level metrics! thanks!
Great Job, Oliver. As always... I learn more from your videos than anybook. and simple and more affective
Pls upload more microstrategy videos . schema objects and public objects
Absolute filtering is not clear enough we have a Region attribute in the metric so why does it work on the call center attribute.
This is really great and helpful!! Thank you so much James ❤️🥳
Hi James,
Thanks a lot for this video, Level metrics is little tricky,and Hard to understand but your video made it easy to understand. A request if possible can you make a video on leave metrics for derived metrics
Thank you.
Thank you for the kind words and new idea!
Hi James
Very happy bv to see your videos ....I am trying to learn MicroStrategy developer tool for changes please help us with u r informative videos.
I'm glad you find the videos helpful. If you have suggestions for new videos you would like to see let me know.
James Oliver can you please make one video on cross join in MicroStrategy
Question: How to resolve cross join in MicroStrategy ?
If you are asking me how to resolve, the issue could be a relationship that is not defined within your attribute. That is the first place I would check. So for example, if you have a time hierarchy and you are trying to aggregate data that exists at the day level up to month, you will need to define in month that it has a one to many relationship with day so the SQL engine knows how to query the attribute. Make sense?
James Oliver Thank you I got the answer
Great topics and detailed explanations!!!!
Hai thanks for video..can u please differentiate between automatic and manual in creating a attribute. which is the better way . Can u give me an example. And what's the difference in creating an attribute in architect view and simply creating with attribute editor
So the Filter "Ignoring" and "Absolute" are the same? "Absolute" ist also ignoring the Report Filter.
thank you
I have one important question,If other than Report level is selected why is it going for cross join?
Hi James this is ok but could you please explain in detail it seems 16 minutes is not sufficient so if you extend this session to up 1 hr or beyond that also fine .Appreciate your trainings and dedication on this .
I agree this subject could use more time and another video!
In Report Level,All the attributes will be used with group by?Is that right?
yes all attributes on report template and in report objects. In fact you can add attributes to the report objects but leave off the grid to force the sql to calculate at a certain level.
@@JamesOliver Alright.
My query is going for Cross Join If I include attribute instead of report level in the level metrics.Why is it this kind of behavior?
@@wwewwf324 Cross joins can usually indicate missing or incorrect relationship
@@JamesOliver SQL query is incorrect but report is correct.
I have one question.I was creating attributes and when i used to add attributes in a report without forming a parent child relationship,I would get cross join.Today,when i removed the parent child relationship and tried to execute the report, i did not have any issue at all.Please help why is this happening.
It depends if the attribute is already on the fact table. If the attribute can be found on the fact tables then you dont need a relationship but if mstr has to join to another table to get the attribute then you need a relationship. This is the simple rule of thumb answer.