DRM Pivots

So, after a bit of a break, it’s time to get back on the horse. Today, I thought we’d look at another DRM feature that has been around forever, but one, that I think gets lost during implementations. I am talking about the pivot feature, when using DRM exports.

Pivot_1

Recently, a requirement came up, where I had to do one-to-many data mappings. For instance, if I had to generate multiple records for the same node, as seen below; how would we go about it?

Map_2

We could create multiple properties to capture the second description, I suppose. But where would that end? Moreover, it would require multiple “save” actions from the user which might be painful as well. There are other ways to skin this cat, but here’s a simple one. It starts with the property setup. I am going to use a list group data type to explore this example.

LG_3

As the name suggests, we are able to make multiple selections, when using this type of property.

LG_4

LG_5

Our hierarchy, now looks like this.

Hier_6

All we have to do now, is set up our export. I’ve chosen to export only leaf nodes (a great option for setting up mapping table exports, BTW).

Leaf_7

On the columns, I’ve selected the node name and beer category properties.

Column_8

I’ve also made sure to select the pivot option, from the Column Options tab.

Column_9

If we now run our export, we get the right results.

Export_10

Bonus points…

Oh, and what happens if we change our property to be a boring string property? And, no longer a list?

String_11

I made some changes to the property values, to elaborate the point.

String_12

Let’s see how this affects the pivot operation.

Comma_13

As you can see, pivot operations are triggered by commas. So, be careful with setting the right data type, when setting up your property! Examples of these would be associated nodes, multiple node etc. That’s all for my first post of 2017.

About Vijay Kurian

Known as the Clem Fandango of EPM consulting, Vijay Kurian has been developing enterprise solutions for companies for the last 12 years (increment years if reading post-2015). Having worked with Essbase, Planning, DRM and other assorted technologies during that time, he’s made the frankly, average decision, to write about them. He hopes to contribute frequently to US Weekly, People and Sensible Chuckle magazines on improving reporting solutions, creating master data management systems and zzz…

Leave a Reply

Your email address will not be published. Required fields are marked *