Multiple Environments – Consolidations
For those of you with Knowledge Base access, click the above link for a quick background…for those without, the problem: “Attribute element filter returns unexpected results after changing the warehouse database and the lookup tables in the new warehouse are populated differently in MicroStrategy Desktop” – as defined by the Technical Note.
What does this mean? This means that if the lookup table IDs in your Dev Database and your Production Database differ, you can’t simply duplicate your production environment and link it to your Dev…and if you don’t have the Object Manager add-on, this means maintaining multiple environments, and making sure they never cross wires. This is a pain. If you’re defining your filters based on Descriptions, or your Dev ID matches your production ID, then no problem…FOR FILTERS.
My filters are defined on Codes and Descriptions, hooray! But…guess what…this rule doesn’t hold true for Consolidations. It seems (now someone correct me if I’m wrong) that Consolidations always use ID’s to do their magic. So, when the production environment was duplicated on to our Development warehouse (so that we could true things up), check out what happened to the consolidation.
So, you’ll notice, what the consolidation says the attribute says it is, isn’t what it really is. Whatever that ID is in your Production Environment lookup table, it doesn’t jive with the Development Environment lookup table…any number of things could have made the difference. The solution? Well, own Object Manager…otherwise, it seems according to the Knowledge Base and tech support…suck it up and start fixing your stuff manually.
Now if only you could buy Object Manager without having to buy the entire Administrator package.
Recent Comments