I’ve shown how easy it is to build an Essbase SaaS database from an existing outline .otl file. Read about my glorious experiences doing just that (and using LCM as well) here.
That’s all well and good but what if I want to do something other than migrating an outline? I thought at first that I’d have to create the smallest Essbase outline in the world ever and then import that, adding dimensions as required. Ugh. Regardless of the ugh, the ick, and the yuck, I wrote about just that approach.
I should have been more patient, because now Essbase SaaS (Have you noted that I call this product what it is – Essbase as a Service? You should.) can load from dimension files. Patience is a virtue but he who hesitates (or wants to write about something most ricky tick) is lost. I suppose that means that I am without virtue because I don’t hesitate to act before knowledge mysteriously comes my way. It was ever thus with Yr. Obt. Svt. But no matter, onwards.
I have a