All posts by: Cameron Lackpour

There are many paths to enlightenment, or at least more than one to the current month

Well. I’ll be a…something or other OneStream never ceases to amaze me. Or perhaps my ignorance never ceases to amaze me (and so, so, so many others). I had zero, zip, zilch idea that the subject of this post was possible. Genius, or at least something close to that....
Continue Reading →

Exporting to Import, Part 6, Out, damned data!  Out, I say!

We are – finally – at the end of the hey-gang-let’s-have-fun-and-load-data-in-OneStream saga. Never let it be said that Yr. Obt. Svt. cannot take the thinnest of gruel and milk it for all its worth and more as it’s been almost three months of this folderol. But fear not, for we have, hopefully for all concerned, come to an end of this series on data loading. With that happy thought, let us turn to the subject of not loading data but getting rid of it....
Continue Reading →

Exporting to Import, Part 5, What If This Was In a Table?

Different technologies seem to have different data format predilections. In my Previous Technology Life, a relational data source was the default: secure, curated, managed, fast, flexible – I could go on and on but you get the idea. Whether extracted by IT in a data stage environment or brought together with some (at least if I wrote it) mildly-not-totally-garbage-but-probably-so SQL, relational data sources were (and still are) the standard for companies, cf. Microsoft SQL Server, Oracle, IBM DB2, MySQL, etc. So why doesn’t that seem to be the case with OneStream? Dunno, as the first word in CPM is Corporate....
Continue Reading →

Exporting to Import, Part 4, Comment or No Good Deed Goes Unpunished

Yes, a rant as well as a brief departure from the ongoing and super-duper exciting (ahem) series on data loading . It’s going to feel great – for me; it may also be instructive – for you. Seriously, read this and ponder if this post doesn’t reflect your practice. If it doesn’t, it really should. And oh yes, this one is dedicated to my objectively younger taller and most definitely smarter and subjectively better looking brother, Celvin Kattookaran. He writes great code, but there is one itsy witsy bit that he misses…...
Continue Reading →

Exporting to Import, Part 3 or just how does the Level 2 Data Unit work?

Loading data into a Cube results in that data in the Cube. Loading additional data into said Cube (think of a new data point although the nuances of this get tricky as we shall see) results in the old data being retained and the new data as well. Data gets loaded; it sticks around. New data gets loaded; the old data sticks around and so does the new. Easy peasy, isn’t it? Except it isn’t because it doesn’t, not always....
Continue Reading →

Exporting to Import, Part 2

The last thrilling post on this subject ended with a Data Management Export Sequence data source. We must now map its fields to the super-duper AVBS application’s equally super-duper Sample cube. This is just a configuration exercise with no code needed....
Continue Reading →

Exporting to Import, Part 1

Moving cube data across scenarios (or entities or time or whatever) can be done via a Data Management Copy Data step or simple api.Data.Calculate statements or api.Data.ConvertDataBufferExtendedMembers. But what happens when there’s a need to perform a data movement and there’s a requirement for complex data transformation?...
Continue Reading →

Useless? Probably. Hilarious? Absolutely. Emojis, yes, emojis, in OneStream

There are times in every geek’s life (mine) where he must face the various vagaries and vicissitudes of life with unflinching good humor lest he lose what few precious marbles he has left. This is one of those times. OneStream’s role in performance management is serious. How could it be anything but unless financial consolidations and multiyear plans are the stuff of jokes? They are not. But life is not all a dire dirge for there are moments of rare joy that illuminate what otherwise might be a life of drab, dreary corporate existence. I live for them. I hope you...
Continue Reading →

Off with their C#Local heads

Little – or big – things can have an impact. Sometimes they are a (gasp) Ferrari 308 in a ditch, sometimes they are data where data should never, ever, ever be. Double gasp....
Continue Reading →

Dynamic? Stored? Why not both?

Dynamic formulas are, by their very name, not stored. So what, you might say (I fear that many say that when I write but such is the way of the world), dynamic members are for reporting, stored calculations whether in a Business Rule or a formula, are for allocations and other calculations that are, well, stored. There are times, however, where the calculated results in a dynamic formula are needed in a stored calculation. Unfortunately, referring to a dynamic calculation within a Finance Business Rule (I believe this is true for the elventy million other kinds of rules as well, but...
Continue Reading →
123