This article provides a comprehensive guide to the Report Definition overview page in the Report Manager. It covers the various elements, settings, and functionalities available for creating and managing report definitions.

Our orientation begins at the top left, where the name entered on the Report Definition tile is displayed next to the back button. Your gaze then moves to the vertically aligned sub navigation options: Pages, Data, and Settings.

Status Select Box

A status select box is attached both on the report definition page and on the Report definition tile. You set the Report Definition in three statuses: 

• Edit
• Draft
• Published

To do this, you use the three statuses:

• Once the Report Definition has been ordered you can only set it to the status Draft.
• In the status Edit, you are working on the Report Definition which means that you are creating mapping elements such as DSE and you are doing the mapping
• You publish your Report Definition by setting the status to Published so that you use the Report Definition for the report order.
• The status draft allows you to prevent further orders of a published Report Definition. The ordered Report Definition is still generated before you can change the Report Definition by setting the status to Edit.

Subnavigation: Settings

Via the Settings subnavigation, you can get to the tabs. You will make the important setting for the mapping there (among other things):

• General settings (Wizard)
• Report Wizard
• Advanced settings

The title can be edited under each tab.

Information: Every change only takes effect when you save. If your report definition is set to Published, you cannot make any changes to the settings.

General settings

Settings	Description
Short description	You use the text box to write a short description for your report containing one hundred characters. By hovering over the information icon this message appears at the bottom left of the tile and on the corresponding tile on the selection page.
Report type	By means of a slide switch, you can set for which report type the report type is used.
File formats	You switch PPTX and PDF on and/or off as selectable file formats for the last step of the report order process.
Language	You select a language in order to translate the survey phrases of the report to be created.
File name	For the filename of the report, you can enter a placeholder in the text field in addition to an individual name. You click on the note about the report filename and a list of possible placeholders opens.

Report Wizard

Settings	Description
Unit selection	You specify the maximum number of subunits from which the virtual units are to consist. This setting only applies to the Ad hoc Report.
Comparison groups	You add comparison units that are activated via the on/off slide switch. The comparison group to be named can then be selected in the inspector. The minimum and maximum of the units to be allocated when ordering the report is also definied here. You can also activate the virtual comparison units by means of the slide switch. The comparison groups can be interchanged by dragging and dropping with the arrow cross or they can be deleted clicking on the delete icon. You add further comparison groups.
Filtering	Activation applies to the report order. You can use it to enable filtering for both virtual comparison units and globally for the entire report. It is filtered in addition to the filters set in the inspector under the sub-navigation fieldPages.

Advanced Settings

Settings	Description
Label for suppressed values	The selected label is set for the values suppressed on the basis of the anonymity criterion.
Label for nonexistent values	For values that are not available like the level-up units of the root unit, the label you have selected is set.
Number format	The setting is activated via the on/off slide switch. You specify the number of decimal places to round to. Separators, dots or commas, are set individually to match the language setting. For example, if you choose German as the language for your report, use the comma as the decimal separator and the dot as the thousand digit.

Subnavigation: Data

Dataspace entities and Collections are used as elements for the cell mapping. On the sub-navigation field Data, you select the appropriate tab for the element to be created at first. You click on the green button and the inspector opens.

For both DSEs and Collections, you do the following steps: 

1.  You assign a unique meta name
2. Selection of the type
   1. You create DSEs as a Simple unit or as a Unit relation.
   2. Collections are created as a Unit collection or as a Dimension collection.
3. You save.

After saving, the inspector will switch to edit mode.

Dataspace-Entity (DSE): Simple unit

The DSE type Simple unit offers you time savings. You shorten longer picker path that you need to determine the unit picker path by creating a DSE.

• If you do the mapping for a comparison unit of a configured comparison group, it is worthwhile to create a DSE. 
• Of course, you also use the other unit elements to create a DSE-type Simple unit: Fixed unit, Focus unit, Comparison unit, (Internal comparison and Configured comparisons).
• The DSE type Simple unit can be used as minuend and a subtrahend in the Unit relation, the second DSE type.

The path is: Comparison unit → Configured comparison → [created comparison group] → Comparison unit x

Information: Depending on how many diagrams or table cells you fill with a constant unit path, it is worthwhile to create a DSE.

Dataspace-Entity (DSE): Unit relation

The DSE-type Unit relation fulfills the promise of a novel exploration of the data space. DSEs are constructed separately from the rigid organizational units that used to be the starting point of the data space query. To create a DSE of type Unit relation:

• You assign a label that is output in the report cells.
• For a minuend and subtrahend, you select the units you want to relate to each other.
  • The minuend must be taken from the current wave.
  • You use all unit elements for the subtrahend.
  • You use the following unit elements: Fixed unit, Focus unit, DSE, and Comparison units.
• You save.

While the DSE Simple unit is used to simplify work, you use the Unit relation to represent a difference value that correlates the selected units with each other. For example, you represent a trend by placing a focus unit from the current wave in relation to one from the historical wave or a focus unit in relation to the comparison unit.

• DSEs can become members of the Unit collections.

Collections: Selection of the collection members

Under the tab Members in the inspector of the sub-navigation field Data, you select up to fifty members for the dimension or the unit collection. You drag and drop them in the desired order. If you do not specify a sort order under the other tab Extras, the order of the members you have selected applies.

•  You compile the dimension collection from the question texts and the dimension items of the survey.
• You create the unit collection from the Fixed unit, Focus unit, Comparison unit, and Dataspace entity elements.
• You save.

Information

A collection is valid and can be saved if at least one member has been appointed.

Definition of the scale

You only define a scale for the dimension collection. You use the specification of the defined scale for the sort order and for the mapping. There they are available via the scale element:

• Under the tab Extras, you click on Choose Scale.

Then the inspector switches to edit mode and you select one for the entire collection from a number of possible scales.

A special feature must be pointed out at this point.

• Depending on which members make up the collection, you can choose from several scales.
• The items are completely different from each other, This makes it difficult to compare the members of a dimension collection.
• Consider how the mapping is to take place and the results in the report to be generated.

Information

Different descriptions of the question text and dimension specifications generate different scales despite identical content.

Sort Order

Under the tab Extras in the inspector, you define the sort order of the Dimension and the Unit collections. You click on Choose sort order and the inspector switches to the edit mode. The sort order for the two elements that can be used in the mapping is then defined on different paths. First, you learn about the sort order of the dimension collection:

• You choose one of the unit elements Fixed unit, Focus unit, Comparison unit, or Dataspace entities.
• You set Collection Member, placeholders for the members of the collection.
• To create both a dimension collection and a unit collection, you click on the mapping element Unit.

If you define a scale, you continue with Scale or one of the following result types:

• N
• Return
• Average
• Standard deviation
• Standard deviation (sample)
• Maximum Response Code
• Minimum Response Code
• Range
• Sum
• Median
• Modus
• Square Distribution
• First Quartile
• Third Quartile
• Interquartile Range
• Explicit missings
• Return rate

If you choose one of the result types, the sort order is immediately valid and is displayed as a path using Tiny-DSQ.

In the next step, if your selection is made for the scale element, select an element from the values of the defined scale listed in the inspector.

To convert the term into a valid term, you can use result types and scale properties as follows:

• Code
• Label
• N
• N as percent

You decide whether the result should be sorted in ascending or descending order:

• You save

Now you will learn the sort order for the unit collection. As it has already been mentioned, it starts by clicking on Unit.

• Then you set Collection Member, which is a placeholder for the member of the collection.
• After setting the dimension element, you select from the question texts or the dimension values.

You continue with Scale or with one of the following result types:

• N
• Return
• Average
• Standard deviation
• Standard deviation (Sample)
• Maximum Response Code
• Minimum Response Code
• Range
• Sum
• Median
• Modus
• Square Distribution
• First Quartile
• Third Quartile
• Interquartile Range
• Explicit missings
• Return rate

If you choose a result type, the sort order is immediately valid and is displayed as pth using Tiny-DSQ.

If your selection is made for the scale element, in the next step, you select an element from the specification of the defined scale.

To convert the term into a valid term, you can use result types and scale properties:

• Code
• Label
• N
• N as percent

You decide whether the result types are displayed in ascending or descending order.

You save.

Information

If you do not define a scale, the scale element is not available for either the sort sequence or the dimension mapping.

Tables

Once you have created DSEs and collections, they are listed in a table. The header lines contain the column headers, according to which the system sorts the columns:

• Metaname
• Type
• Size
• Created
• Modified
• Status

The table rows of the created DSEs and collections, which are highlighted by mouseover, display icons for editing, copying, and deleting. If you want to edit, you click on the pencil. You only correct the unit selection. Once a type has been defined, it cannot be edited. For copying, you assign a new and unique metaname in the modal, which is then used to create a new element, DSE resp. collections, with identical assignments, without switching to edit mode.

The validation status of each DSE or collection, which is also found in the inspector, can be seen in the column “Status”.

• Gray = undefined
• Red = invalid
• Green = valid

If DSEs and collections are deleted, the elements used in the mapping are not removed or discarded, but the status changes to “invalid”. The cell in question is bordered red in the mapping on the sub-navigation field Pages. This has the advantage that you don’t have to change the picker path, but instead, you create a new DSE or collection with an identical metaname to convert the newly created element back into a valid one. Of course, the element type can be changed. You do not have to ressemble all paths that use invalid DSEs or collections.

Subnavigation: Pages

You execute the button + New Page on the field Pages to create a new page in a Report Definition. A message will inform you about the success of the action. Your intention to delete a page requires a modal confirmation. This way, you won’t accidentally delete a page. After successfully adding a page, you use the selection box to select a master slide from either all libraries created or a special one. In this way, you can compile your report individually. In addition to that:

• You sort the page by drag & drop.
• You create a new page for each additional slide.
• You find more about it under the master slide:
  • File format and file name
  • Library
  • Mapping Status
• You have two icons that allow you to download files and copy the mapping from another page.
• You add conditions for each page of your report.
• In the lower part of the page, dedicate yourself to the cells and tables to create the mappings.

Information :The displayed chart, tables, and individual mapping cells are displayed in reverse order to the order displayed on the report page.

Create mapping

You click on Create mapping in one of the shape cells you want to start with and the inspector opens. There are two taps: Mapping and Filter. You do not set filters until you have created a mapping. The mapping starts by selecting a starting point for the picker path from up to four elements:

•  Unit
• Dimension
• Collections
  • Collections must first be created on the sub-navigation field Data under the tab Collections so that they can be used for the mapping.
• Text

You use these elements depending on your objectives. The paths on which you move from which starting element so that you fill the shape cells appropriately depends on the specifications of the report to be filled out.

Information

By clicking on tags below the cells, you can query the tagging performed with the Tagging Tool.

Layout of the Inspector I: Mapping

The inspector is one of the important controls in the Report Manager. You use it when creating DSEs and collections. You also use it for the mapping. Generally speaking, it can be said that the inspector is the control panel moving from the right into the display.

On the sub-navigation field Pages, the inspector moves in as soon as you click on Create mapping, and is used for the cartography. You define the paths that define how the shape cell is to be filled.

• On this sub-navigation field, the inspector has two tabs: Mapping and Filter.
• Under the two tabs, you will find information about which shape area you can map.
• Each path is validated by setting a green check mark.
• A red warning triangle indicates any pending validations.
• You have a search function under the tap Mapping that allows you to reduce the more extensive selection options of the picker elements to a clear number. Use the arrow keys to navigate either by scrolling through the list of results block by block of ten or by jumping directly to the end of the beginning.

Layout of the inspector II: DSEs and Collections

On the sub-navigation field Data, the inspector moves in as soon as you click on Add Dataspace Entity or Add Collection. On the sub-navigation field Data under the tab Dataspace Entity, the inspector is used to create unit elements for the mapping that are available on the sub-navigation field Pages.

• To do this, you create picker paths from the existing unit elements
• Each path is validated by setting a green check mark.
• A red warning triangle indicates any pending validations.
• If you want to create a DSE type Unit relation, the inspector expands and displays the unit elements on a separate panel.

On the sub-navigation field Data under the tab Collections, you use the inspector to create the two mapping elements dimension and unit collection. The inspector has two tabs for creating a dimension collection and creating a unit collection; Members and Extras. 

• Under the tab Members, you specify the members of the dimension or the unit collection.
• You can sort the members under this tab by dragging & dropping and deleting them. You find the corresponding icons, sorting arrows, and trashcan, by mouseover to the right of the selection field.
• Under the tab Extras, you select a scale and a sort order in the case of the dimension collection. In the case of the unit collection, you define only the sort order under this tab.
• The inspector is extended both for the selection of a scale (dimension collection only) and for defining a sort order (dimension collection and unit collection).

In the case of the scale selection, the available scales can be found on this further panel, while in the case of defining a sort order, the additional table is structured like the inspector in the mapping.

Information

If you want to delete a mapped element, you click on the defined cell, and in the inspector, you click on the X symbol of the first element. You can edit a mapping by simply clicking on the mapped cell.

The Text element

You use the mapping element Text to fill shape cells with self-written texts.  This element is not used for data space queries.

• You use this element to place individual labels in the report that you enter in the user-defined text field.
• The number of characters used depends on the cell size of the PowerPoint shape. If you use too many characters, it will be written beyond the cell boundary.

The path is: Text → [self-written text]

The Dimension element

You not only continue with the mapping element Dimension after you have picked a unit, for example, but you also start your picker path with this element. If you start with the dimension element, it is used to fill the shape cells with the question or dimension item text. The question texts of the survey and their dimension items are available to you for this purpose, if available.

The representation in the inspector is structured as follows:

• Question text of the first question of the survey
• Dimension item(s) of this question
• Question text of the second question of the survey
• Dimension item(s) of the question
• etc.

You pick the path:

Dimension → [question text] or Dimension → [dimension item]

You continue with:

• Label
• Scale

If you continue with Label, the term is immediately valid. If you continue with Scale, you extend the already entered picker path so that the scale specification for the question can be queried and selected for the report.

You pick:

Dimension → [question text/dimension item] → Scale → [scale item]

You end with:

• Code
• Label

The Unit element

The following sub-chapter deals with the mapping element Unit, which you will encounter when working on the sub-navigation field Pages and Data as well as during report ordering. After you have clicked on Unit, it breaks down into the elements Fixed unit, Focus unit, Comparison unit, and Dataspace entities.

Fixed unit

The Fixed unit is an unchangeable fixed point for your report. You take the required unit directly from the organizational structure.

• It allows you to set a static value that remains the same regardless of the focus unit selected.
• It is a good idea to select the root node for such a static higher-level value.

You pick:

Unit → Fixed unit → [org. structure unit]

You continue with unit properties, result types, or Dimension:

• Label
• N
• Return
• Return rate
• Metaname
• View_ID
• Level
• Response_anon
• Dimension

If you continue with unit properties or result types, the term is immediately valid.

To continue with Dimension, click here.

Focus unit

The mapping element Focus unit is used as a placeholder. This placeholder is filled with concrete units from the organizational structure in the first step of the report order. For each order type you have to select the Focus unit(s).

• You use this unit element to order a separate report for all selected units of the organizational structure.
• It is the ideal prerequisite for the report order type Standard Report because you use this mapping to order reports for all organizational units.

You pick:

Unit → Focus unit

You continue with unit properties, result types, or Dimension:

• Label
• N
• Return
• Return rate
• Metaname
• View_ID
• Level
• Response_anon
• Dimension

If you continue with unit properties or result types, the term is immediately valid.

To continue with Dimension, you click here.

Internal comparison unit

The unit element Comparison unit first branches into Internal comparisons and Configured comparisons. Under Internal comparisons, you will find the Level-Up comparison unit.

• The Level-up comparison unit refers exclusively to the Focus unit and forms a dynamic pair with it.
• You do not remove any unit manually in the organizational structure.
• The next-higher unit of the organizational structure is used as a comparison with the Focus unit.
• As long as no specific unit has been selected for the placeholder element Focus unit, the Level-up comparison unit is only abstractly available.
• You use this Comparison unit to compare the Focus unit with the next higher unit in the organizational structure.

You pick:

Unit → Comparison unit → Internal comparisons → Level-Up comparison unit

You continue with unit properties, result types, or dimensions:

• Label
• N
• Return
• Return rate
• Metaname
• View_ID
• Level
• Response_anon
• Dimension

If you continue with unit properties or result types, the term is immediately valid.

To continue with Dimension click here.

Configured comparisons

You use the element Configured comparisons to access all comparison groups that you create in the Report Wizard under Settings. The members of the comparison group are determined in the second step of ordering the report.

• The comparison units that form the members of the comparison groups do not have a name but are counted as placeholders from top to bottom.
• During the report ordering process, you ensure that the desired unit of the organizational structure is taken from the members selected in the mapping.
• The element Configured comparisons is useful if you want to make a comparison free of the organizational structure.

You pick

Unit → Comparison unit → Configured comparisons → [created Comparisons group] → Comparison unit x

You continue with unit properties, result types, or Dimension:

• Label
• N
• Return
• Return rate
• Metaname
• View_ID
• Level
• Response_anon
• Dimension

If you continue with unit properties or result types, the term is immediately valid.

To continue with Dimension click here.

Dataspace entities

Using the unit element Dataspace entities, you have the created DSEs Simple unit and Unit relation in the mapping. The DSE-type Simple unit is a work relief. You use it like the unit which is replaced by it. The DSE-type Unit relation is only presented here.

• It is particularly suitable for calculating the difference values of those units that are to be used as reference points in the report.
• If the Fixed unit and Level-up comparison unit form recurring values, it makes sense to make the difference in relation to the existing data material, the two units, visible by means of a DSE Unit relationship.

You pick:

Unit → Dataspace-Entities → [created Unit relation] 

You continue with unit properties, result types, or Dimension:

• Label
• N
• Return
• Return Rate
• Dimension

If you continue with unit properties or result types, the term is immediately valid.

To continue with Dimension you click here.

Collections

The use of Collections in the mapping depends on whether you fill a single shape cell with the collection or whether you use the collection in the Loop mode to fill the columns or rows of the selected table. First, you will learn about shape cell mapping. You map the Dimension and Unit collections created under the sub-navigation Data.

Dimension and Unit collections

If you select the element Collections, the dimension or unit collections you created are available. You click either on the created Dimenison collection or on the createdUnit collection. The meta names you have assigned are displayed.

• You fill a cell of the shape with a member of the dimension or unit collection.
• The members of the dimension or unit collection are subject to a sort order that you either define yourself or that you define in Sort order under the tab Extras on the sub-navigation field Data.
• Using the element Item, you can take a member from this sequence.
• If you do not define a sort order, the item x corresponds to the collection member set in place of the sequence.
• If you define a sort order, it is not possible to see which member of the collection is mapped. It is the member who, by virtue of its value, occupies that position x in the order of its members.
• The sequence is defined by the sort order.

You pick:

Collection → [Dimension collection] → Item x or Collection → [Unit collection] > Item x

In the case of the Dimension collection, you continue with either unit properties or Unit:

• Label
• Unit

Continue with Label, the term is immediately valid.

To continue with Unit click here.

In the case of the unit collection, you continue with either unit properties, result types, or Dimensions:

• Label
• N
• Return
• Return rate
• Metaname
• View_ID
• Level
• Response_anon
• Dimension

If you continue with result types or unit properties, the term is immediately valid.

To continue with Dimension click here.

How to use Collections in the Loop mode

The prerequisite for using this feature is the corresponding tag of the shape in the PowerPoint template. You activate the Loop mode using the on/off slide switch. All previous mappings in the table are deleted as soon as you switch the Loop mode on or off.

The Loop mode makes your work much easier since the table is no longer filled cell by cell, but column by column or row by row.

Only table-wise looping is possible, not page-by-page.

You click on Choose Collection.

• You select one of the collections created.
• You configure the start and end of the collection by using a numeric stepper to define the first and last member to be displayed in the report. You start with the umpteenth member and end with the nth member.

Depending on which tag has been set in the PowerPoint template, you can map either column or row by row.

You click on Create mapping and select the Collection member in the inspector.

• Depending on whether you select a dimension collection or a unit collection, you continue with different mapping elements.

In the case of the Dimension collection, you pick:

Collection member

You continue with:

• Label
• Units 

Continue with Label, the term is immediately valid.

In the case of the Unit collection, you pick:

Collection member

You continue with unit properties, result types, or Dimension:

• Label
• N
• Return
• Return rate
• Metaname
• View_ID
• Level
• Dimension

If you continue with unit properties or result types, the term is immediately valid.

To continue withDimensionclickhere.

Sort order and Loop mode

In the case of the Dimension collection, it is advisable to operate with a paradigmatic example to explain the use of the Loop mode and the Sort order in the mapping: Comparison of the Focus unit with the Level-up comparison unit. You define the Sort order for the Dimension collection on the sub-navigation field Data under the tab Extras using the following path, for example:

Unit>Focus unit>Collection member>Average

Another project parameter that you define is the ascending or descending sorting. You choose descending. You save them. For mapping on the sub-navigation field Pages, this means that the sorting in the background is effective and that the values of the Level-up comparison unit are sorted in relation to this sequence. After activating the Loop mode, you select the Dimension collection and use the following paths to compare the Focus unit with the next higher unit.

For the Focus unit, you pick:

Collection member → Units → Focus unit → Average

For the Level-up comparison unit, you select:

Collection member → Units → Comparison unit → Internal comparison → Level-up comparison unit → Average

Information: To avoid any irritation that may be caused by the fact that the mean values of the level-up comparison unit are not sorted in descending order, note: The values of the level-up comparison unit are set in relation to the sorting of the mean values of the focus unit. The level-up comparison unit values are output according to the order of the focus unit. The values that can be compared with each other are thus in a row.

In the case of th eUnit collection, however, this example cannot be retained. as the project parameters change. You define a sort order for the unit collection with the intention of sorting the members of this collection by result type in relation to a question or dimension item.

A possible picker path is:

Unit → Collection member → Dimension → [selected Dimension] → Average

A sample sorting is:(M) Collection member (D) I would recommend People Company to friends (R) Average

In this case, the sorting is also carried out in descending order. Then save your entries. On the sub-navigation field Pages, activate the Loop mode and select the created unit collection as a collection. In a column, click on Create mapping and map in the same way as the Sort order of the Unit collection.

You pick:

Collection member → Dimension → [selected Dimension] → Average

A sample mapping is:(D) I would recommend People Company to friends (R) Average

In a new column, select a dimension other than that selected in the sort order in the Inspector so that the values for the unit collection members are sorted according to the Sort order, but the values are output for this dimension.

You pick:

Collection member → Dimension → [another selected Dimension] → Average

Unit collection	I would recommend people Company to friends	Senior leaders are sufficiently visible at people Company
Focus unit	3,5	2,5
Fixed unit	2,5	3,7
Level-up	2,0	3,0

The sample mapping is:(D) Senior leaders are sufficiently visible at People Company (R) Average

The following can be said for the sample report: The Focus units are sorted in descending order according to the average value of the question “I would recommend People Company to friends“. In the second column the averages of the question “Senior leaders are sufficiently visible at People Company“ are output for each Focus unit of the Unit collection.Information: Both the dimension and unit collections are iterated either via the row or the column. If you use Rows as the value for the loop mode tag, the values are filled row by row into the cells (one below the other). If you useColumnsas as the value for the Loop mode tag, the values column by column are set next to each other.

Continuation with Dimension

In addition to the mapping elements for result types and unit properties, with which the path is immediately valid, the element Dimension allows you to continue the picker path. You take the direction of the question text and the dimension value to continue your path. To refer the selected unit to the question texts or existing dimension values of your survey, proceed as follows.

You pick:

Unit → [unit element] → Dimension → [question/dimension item]

You continue with result types or Scale:

• N
• Return
• Average
• Standard deviation
• Standard deviation (sample)
• Maximum Response Code
• Minimum Response Code
• Range
• Sum
• Median
• Modus
• Square Distribution
• First Quartile
• Third Quartile
• Interquartile Range
• Explicit missings
• Return rate
• Scale

Continue with result types, the term is immediately valid.

To continue with Scale, you click here.

Continuation with Scale

The path does not have to end after you have decided on a question or a dimension item. The elementScaleprovides you with a continuation option so that you move on the path which you have already continued with Dimension. Therefore you pick an item x of the scale property or a result type.

By means of this branching, your results achieve accuracy, because you not only take the questions into account, as is possible with the continuation by question or dimensional expression, but also evaluate the answer page in a differentiated way.

You pick:

Unit → [Unit element] → Dimension → [Question text/Dimension item] → Scale → [Scale item]

You continue with scale properties and result types:

• Code
• Label
• N
• N as percent

If you continue with a scale property or a result type, the term is immediately valid.

Another branching is not possible.

Continuation with Unit

Both as a starting element for cell mapping and in Loop mode, the path for the Dimension collection requires a continuation with Unit.  To do this, select the desired element from Fixed unit, Focus unit, Comparison unit and Dataspace Entities.

You pick for the cell mapping:

Collection → [Dimension collection] → Item x → Units → [Unit element]

You select a Dimension collection in the Loop mode. In the new column, you select:

Collection member>Units> [Unit element]

You continue with the result types or Scale:

• N
• Return
• Average
• Standard deviation
• Standard deviation (Sample)
• Maximum Response Code
• Minimum Response Code
• Range
• Sum
• Median
• Modus
• Square Distribution
• First Quartile
• Third Quartile
• Interquartile Range
• Explicit missings
• Return rate
• Scale

If you continue with a result type, the term is immediately valid.

Information: To be able to map the scale element at this point, you must define a scale for the dimension collection in the sub-navigation field Data under the tab Extras.

Filter

You use filters in the Report Manager in various places. A first opportunity to use the feature is offered during mapping. They provide each cell of the mappable shapes with a filter. When you order reports, you also set up filters. The second step in the order process is not only to define the members of the Comparison group but also to set up a filter for each member of the group. Virtual comparison units also receive a filter. A global one that applies to the entire report is encountered in the third ordering step.

Available filters

The following filters are preset and can be used for mapping filtering, global filtering, and filtering virtual comparison units:

• Tester
• Language
• Disposition code
• Gender

The filter selection for the conditional report uses unit properties as filters to determine units:

• Label
• Metaname
• View_ID
• Level
• Response_anon

Mapping filters

Each filter variable has inherent branches that you use for further specifications.

These are connected by the non-exclusive OR, which is not represented by an element. For example, if you choose the filter variable gender, you select the options: Not available, male, female. In contrast, the different filter variables are linked by the logical AND, which is also not represented by an element. The following syntax is hidden behind the filter elements in the mapping, which are only apparently placed side by side without connections: Gender–maleORGender–femaleORGender–not availableANDDispositioncode–Not yet invitedORDispositioncode–ActiveANDTester–No tester. Just as the filter variables cannot be linked to each other with OR, you cannot combine the specifications with an AND.

Tiny DSQ

Tiny DSQ enables a clearer representation of the data space queries stored in the shape cells. However, their location is not limited to mapping. Tiny DSQ is also used for creating DSEs and collections. Noteworthy for deciphering the abbreviated picker paths are the letter icons and the color scheme. This is based on the syntax and allows you to recognize dependencies between the elements. The property icon is colored according to the element whose properties are queried.

Meaning	Icon	Color
Unit	U	green
Dimension	D	orange
Scale item	S	black
Collection member	M	gray
Result type	R	black
Collection	C	green
Property	P	alternating
Text	T	black

Page conditions

Page conditions determine the conditions under which a page is included in the report or not. You click on Add and the inspector opens. To define a Page Condition, you proceed as follows:

• You select a DSQ, as you also create it for the mapping, which is composed of unit elements, unit properties, Dimensions, Scale, and result types.

You select a relational operator:

• = (equal to)
• != (not equal to)
• > (greater)
• >= (greater than or equal to)
• < (less)
• <= (less than or equal to)

You enter a reference value.

• Words and numbers act as reference values.
• If you select “Metaname“ or “Label“ as the Unit property or “Label“ as the scale property, you can use the relational operators = or != to enter the label or meta name of the desired unit in the reference value field. In this way, you can deactivate page by deactivating it for a specific unit.
• You save.

The presented procedure can be illustrated on a possible page condition: You only want to release a page of the report for units that are assigned to the first or second level. After the inspector has opened, you set the Page Condition:

You pick a DSQ path:

Unit → Focus unit → Level

• As the relational operator, you choose < (less).
• As the reference value, you enter 3.
• Then you click on Save.
• The following is shown as Tiny DSQ.

(U) Focus unit (P) < 3

For all units whose level within the organizational structure is greater than 3, the page with the condition is deactivated. Only units that belong to the first and second levels receive a report containing this page:

• You edit a page condition by clicking on the Tiny DSQ.
• If a page condition is no valid, the Report Definition can not be published.
• You delete a page condition by clicking on the corresponding icon: the trashcan.
• If you want to copy or import or export a Report Definition that contains page conditions, you can only do this if the conditions are also available within the new report definition.

Copying mappings

In the Report Manager, it is possible to transfer previously defined mappings of a page to a new page, so that you do not have to map each cell again. On the sub-navigation field Pages, you click on the icon “Copy mapping from another page“. The inspector opens so that you select an existing Report Definition. The prerequisites for successful copying are:

• The source and target foil must be identical.
• The report definitions must match in such a way that the mapping to be copied can also be created manually within the scope of the report definition in which the copy is to be inserted. Both have to use the same EFS project.

Information: Collections and Dataspace entities must be created again so that the copied Report Definition has no invalid mappings and so that the Report Definition can be published.

FAQ

What is the difference between a Simple unit and a Unit relation DSE?

A Simple unit DSE is used to simplify mapping by shortening longer picker paths, while a Unit relation DSE is used to represent a difference value that correlates selected units with each other.

How do I activate Loop mode for mapping?

To activate Loop mode, use the on/off slide switch when mapping a table. Note that activating Loop mode will delete any previous mappings in the table.

Can I use filters in multiple places within a report definition?

Yes, filters can be used in various places, including cell mapping, global filtering for the entire report, and filtering for virtual comparison units.