Why am I writing this?
Well, sometime it helped and we now have allocation tables in administration links. Although I'm sure my post didn't have any impact, some deem hope remains
I'm going to repost this into Communities and into Insight. And, maybe, we can create some noise by voting for these enchancements in Insight aka registering those enchancements again (they get piled up together, as I've found out).
Some those two echs are:
1) Easy as: "Add the ability to import Calculation Options and Weighting while importing a dlist"
If you've ever done some external dimension management, you know that:
- you have to use unique names to keep dlist IID the same when names (but not unique codes) of items change
- you can import formulas as calculation text, just put item names in curly brackets )
- if you use Update\Remove obsolete it always deletes all Calc Options and Weighting from dlist. That means that you cannot update any cacluation dimensions, such as Accounts.
So you manage all simlple dimensions by updating them (with Remove Obsolete selected) and unique names, and you manage all dimensions with weighting by manually changing them.
Shouldn't be like that.
2) Even simpler: Add a Contributor macro for importing translations
It seems weird to have a single table with translations for Cognos BI and then to manually (or semi-automatically by text import) copy it into Contirbutor application. Shouldn't be hard, ability to import translation text is already there, just need a macro step
3) And another one (maybe no one will notice): Import deployment packages as a macro step too
Automating dev-prod. backup-restore -- all those things that should be automagical
So, if these things annoy you as well -- drop me a line, and I'll send you Cognos Insight ench numbers to vote for.
Hi,
I want to vote for at least the 1st and the 2nd
thanks!