Part 3 of 3 - In this series of blogs we discuss the Consolidation and
dimensions that drive the power of the cube in OneStream. I first used
an Origin dimension with another product, but it was completely custom.
OneStream smartly has this prebuilt ...
Part 2 of 3 - In this series of blogs we discuss the Consolidation and
Dimensions that drive the power of the Cube in OneStream. Hey! Where is
my data?!?! You explained during the POC. Then it was covered during the
ABA training. As you discussed eli...
Have you ever wondered how the Calculate if No Data setting works? (I
did, and Keith Berry helped me out) “Calculate if No Data = False”
prevents the execution of rules on “OK,NA” (no data) entity. However,
the Calc Status gets changed from “OK,NA” t...
Part 1 of 3 - In this series of blogs we discuss the Consolidation and
dimensions that drive the power of the cube in OneStream I was in a
meeting with a large group of consultants years ago. Some were Budget
and Forecast guys, others were Consolidat...
I was asked today, 'Am I correct to think that Databuffers do not return
Null/Blank cells and therefore you don't need to check whether the
cellstatus is Not NoData?' The full data unit is in memory and Time is
part of that. The system needs it in me...
One option people do when creating a people planning application is to
not put names/titles and salary data all together. Meaning they might
just use employee id, or some other information. When that isn't an
option, you can create an application tha...
My first thought is if you used the member filter in the formula you
could call all base accounts under IncomeStatement. As an example
-api.Data.Calculate(formula, accountFilter, flowFilter, originFilter,
icFilter, ud1Filter, ud2Filter, ud3Filter, ud...
You can add Force Translations in the workflow, as part of the Run
Calculate step. And I like this option much better than having the
system try and guess based on where data is. The reason is that there
are times when no one will enter data and you ...