If I want to display the following data in a treemap diagram, I encounter a problem: The scaling in the Treemap object is obviously correct. But, in my opinion, the color coding is faulty (or at least not comprehensible/understandable for me).
Opportunity to define an entity as a dimension and as a tree entity In some particular cases, reporting requirements might put the developer in front of a dilemma: define information either as an entity or as an infocube. Below is an example that shows strong and weak points of both approaches. Let’s take the example where the
Hi, in BOARD you can create max. 999 Cubes, which is enogh in many projects. But we're facing the problem, that in some bigger Projects we're using a lot tec-Cubes and so it is sometimes hard to be within this limit.So it would be great, if this limits get extended in a future release. Examples for Tec-Cubes (mostly driven by new
Hi, Using the drill to screen action I'm able to set a selection for the target screen. As procedure action there's a "Apply selection to current screen" that allows to make the selection for the current screen. As a second step I can use the "Go to screen" action and go to the screen of my choice. The disadvantage of doing so is that,