A n00b’s OneStream Journey No. 8 — Why Two Is Not Better Than One

Apologies and yet without apology

Apologies up front as the subject of this blog post is both n00bie-ish as well as somewhat advanced and awfully, awfully, awfully important. It’s super-duper important that you understand what follows because a common design requirement and an equally common design solution won’t and doesn’t take into account OneStream’s core storage model. I’ll be making references to Data Management jobs, Finance business rules, as well as Data Buffer processing which is all rather a lot for a n00b post. But all of that is exposition – the key thing for we n00bs is to understand that a design approach we all take for granted in other tools is a Bad Idea in OneStream. Happily, the solution is straightforward.

The 42 people who regularly read this blog probably know a fair bit – although logic demands that I ask why you lucky 42 read it if you already know it. Perhaps you enjoy irrelevant links to popular culture from a year that predates your time on this planet by at least 50 years. Ask your parents or better yet your grandparents to help with that sort of confusion; hopefully the balance of the post will make

…

A n00b’s OneStream Journey No. 5 — A Very Basic Sample

It’s Basic. It’s a Sample. It’s A Very Basic Sample.

Some people understand how to perform complex tasks or understand involved theory simply by reading some kind of supercalifragilisticexpialidocious documentation; I am not one of those people. Yes, I read the docs, yes, I think – insofar as I am able – quite a bit about what I’ve read, yes, I am capable of abstract thought (I hope, in an abstract way.), but at the end of the day, I learn best by doing. I’ve got to kick the tires, squeeze the apple (these are my favorite ones by a country mile), or employ whatever experiential learning metaphor you like best to truly understand.

Please try to put aside the irony of the above as the introduction to a blog post that attempts to explain how OneStream works as you, Gentle Reader, and Yr. Most Hmbl. & Obt. Svt. are about to go on a journey that illustrates our beloved CPM platform in as a practical manner as I can manage. In OneStream-land, I need to build a sample application.

But you say, (Do you? Do you? Really? Thought you did. Sad, but I’m glad you’re still here.),

…

A n00b’s OneStream Journey No. 4 — Deleting and reloading an application

Moving an application tither and yon

Moving applications across environments is part and parcel of practically any CPM vendor’s tools. It’s here in production and I want it to be there migrated back into development. Or the other way around. Or across servers. Or to a laptop (for we consultants). Whether your team does the moving, or your IT department does it, or your managed service provider does it, or if indeed your software vendor’s cloud team does it, the key bit is that someone does it. Also, it could be you who does the moving.

If you think this is hard, or requires many hours, or is fraught with the potential for error (erm, except for the self-harm Yr. Obt. Svt. inflicts upon himself as I stumbled through this), you’re wrong. It’s dead easy with OneStream.

Let’s do this in steps.

Step the first, extract the application for migration

Just a note – the process I’m going to illustrate below will be for metadata (dimensions, CubeViews, security, dashboards, etc.) only. There’s a separate step that extracts data and I’ll cover that in some later post.

Just another note – this is from an honest to goodness customer application and

…