My 20+ years of using Essbase I was told, and had no reason not to believe, only stored numbers. We obviously have lists and with Planning it appears we have text. If you aren’t familiar with how this works, the strings are stored in the Planning repository and the index is stored in Essbase. If you thought the same thing, you were as wrong as I was.
Read moreThere are benefits to moving to Hybrid, but there are also some challenges. The content of this post is not around the pros and cons, but the fact that you can upgrade your environment to use it. If you find it isn’t for you, you can “downgrade” back to BSO. The flexibility provides everybody the ability to try it.
Read moreMost of us know that there is a button in the calc rule editor that allows us the ability to select a smart list and the smart list entry. It will add something [[smartlist name.smartlist entry]]. If this is new to you, what it does is replace reference the smart list and replaces it with the numeric value that exists in Essbase. The beauty of this is that it is dynamic, so if the smart list is changed in any way, you don’t have to go into your rules and replace change the index values for the smart list entries to match. Guess what, there are more!
Read moreWith hybrid being used more and more there is a need to manage the storage methods of different levels of sparse dimensions. Whether it is a staggered hierarchy or not, getting the storage method from the source can sometimes be challenging. More often times than not, you may want to own it on the Planning side so you can change it at will and not have to go through the typical IT change order process that may take weeks, or even months, to go through the full development cycle.
Read more