Framework:Dimensions: Difference between revisions

From CoPlanner 10
Jump to navigationJump to search
Created page with 'Dimensions have a level structure. They are used to distribute aggregating data and break them down to any level. thumb|center|Framework, Dimensions …'
 
No edit summary
Line 38: Line 38:


[[Category:Framework|Dimensions]][[Category:Framework Objects|Dimensions]]
[[Category:Framework|Dimensions]][[Category:Framework Objects|Dimensions]]
[[de:Framework:Dimensionen]]

Revision as of 10:53, 3 May 2010

Dimensions have a level structure. They are used to distribute aggregating data and break them down to any level.

Error creating thumbnail: File missing
Framework, Dimensions

Dimension designer

Like with tables, the so-called dimension designer is available to process the dimension.

Error creating thumbnail: File missing
Framework, Dimension designer

The setting options and the functions of the individual tabs correspond to those of a table.

The “Options” tab offers the following additional setting options:

Available for distribution

With this option, you define whether this dimension is available to the data wizard for the distribution of the data from a sum element to its subordinated elements.

Default distribution

This option is used exclusively for dimensions. It controls a possible automatic distribution of the datasets when input to nodes. The following settings can be made:

  • K or empty (default setting): no distribution – values input to empty nodes remain there.
  • Lx (x=1-n or 0 for all levels): Level – continuous aliquot distribution to the next n levels (respectively to the lowest level at L0).
  • Ex (x=1-n or 0 for all levels): Element – aliquot distribution to level n (respectively to the lowest level at L0)
  • Sx (x=1-n or 0 for all levels): Structure – currently like Lx

Dimension name multilingual

This option permits the saving of dimension element names in various languages. Simply log in with another than the default language (ex works: German) and give the dimension element a name in this language. The input is saved as a translation in CoPlanner’s multi-lingualism tables, the name of the original element remains untouched.

Macro,…

In this combination list field, you can select a macro which is executed directly after a saving procedure.