Few things to clarify: 1) After the creation of dimension later on in the *. dim window by going to each attribute for which you want aggregations on ,(for example DimProduct) - do we need to go to properties of the attributes (by right click on "ProductKey" choose properties) - in the properties by editing the key column section do we have to give all the related keys from top to down ( for " ) and so on . {Please Answer } 2a) In the self reference DimEmployee table after creating a dimension in the **.dim window --for EmployeeKey properties section why did turn of "" , "" -- in the Parent-Child section "" for EmployeeKey 2b) for ParentEmployeeKey properties section why did u turn of "" , "" ' {Please Anser Why?} -- in the Parent-Child section "" for ParentEmployeeKey {Please Anser Why?} --in the Parent-Child section "" for ParentEmployeeKey {Please Answer Why?}
Thanks for the excellent video. I could not understand the error that comes at 12:50 - Could you please give me more details of it and how you fixed it ?
Keshav, there was an error at 12:45 to 12:47 of this video. Please explain why that came as this had come for me too. Instead of adding Calendar Year I added Fiscal Year but it worked for me this time. Why does that error come?
Each attribute contained within a hierarchy needs to have its key column(s) identify it distinctly. In this example, Month is in both hierarchies. Month by itself is not distinct - each value will appear against every year. By including year as an additional key column (be it Calendar or Fiscal Year) you identify it uniquely and aggregation now works correctly. This is how he fixed it and also why it fixed for you using Fiscal instead of Calendar Year.
It means this attribute does not appear as a selectable hierarchy by itself, it will only appear within user-created hierarchies. So, for example, if you set Month to not be visible, it will only appear as a level in the user-created Fiscal and Calendar hierarchies and not as its own hierarchy.
Nice job Keshav! Impressive!
Thank you so much. your videos have given me a new carrier.
Few things to clarify:
1) After the creation of dimension later on in the *. dim window by going to each attribute for which you want aggregations on ,(for example DimProduct)
- do we need to go to properties of the attributes (by right click on "ProductKey" choose properties)
- in the properties by editing the key column section do we have to give all the related keys from top to down
( for " ) and so on .
{Please Answer }
2a) In the self reference DimEmployee table after creating a dimension in the **.dim window
--for EmployeeKey properties section why did turn of "" , ""
-- in the Parent-Child section "" for EmployeeKey
2b) for ParentEmployeeKey properties section why did u turn of "" , "" '
{Please Anser Why?}
-- in the Parent-Child section "" for ParentEmployeeKey
{Please Anser Why?}
--in the Parent-Child section "" for ParentEmployeeKey
{Please Answer Why?}
Thanks really helped me :)
You're my boy Keshav
Thanks for the excellent video. I could not understand the error that comes at 12:50 - Could you please give me more details of it and how you fixed it ?
Super clear. Thanks a lot!!!
Keshav, there was an error at 12:45 to 12:47 of this video. Please explain why that came as this had come for me too. Instead of adding Calendar Year I added Fiscal Year but it worked for me this time. Why does that error come?
Each attribute contained within a hierarchy needs to have its key column(s) identify it distinctly. In this example, Month is in both hierarchies. Month by itself is not distinct - each value will appear against every year.
By including year as an additional key column (be it Calendar or Fiscal Year) you identify it uniquely and aggregation now works correctly. This is how he fixed it and also why it fixed for you using Fiscal instead of Calendar Year.
Helpful. Thank you.
Why did not u changed the Type to Time and also the type of Date attribute ? YTD , QTD,MTD would not work in that case ?
thanks for sharing
the forth video in SSAS series , Definitely has some problem , it takes hell lot of time to load , Keshav Could you please help !!!!!
I tried, not sure of the issue from ur end but it's working fine for me.
What was the use of attribute hierarchy visible =false
It means this attribute does not appear as a selectable hierarchy by itself, it will only appear within user-created hierarchies.
So, for example, if you set Month to not be visible, it will only appear as a level in the user-created Fiscal and Calendar hierarchies and not as its own hierarchy.