Don’t do it, the manual bit
In our last exciting installment, Yr. Obt. Svt. took you on a trip through the most basic of dimension building processes, to wit, building a dimension by hand.
That’s all well and good but it doesn’t really reflect true application development and administration as doing just about anything by hand (sawing wood, cutting the lawn, filling out that 1040A, casting a budget, etc.) is painful for anything other than one-offs, a small scope, or something that hardly ever changes. Repetitive actions should be automated else we revert to paper ledgers and spreadsheets, fountain pens (actually, I use one), and green eyeshades. Instead, I daresay and hope you’ll do most of your loading from batch.
But how oh how oh how does your average geek load a dimension?
One way might be to take an existing dimension, extract it to a file (in OneStream XF aka XF that’s an XML file whose format I’ll cover in the next post – see how I’m stringing you along?) and then use that file to load said dimension in again to this application or to another. Hint: this sentence just described how to migrate dimensionality