DT411 Data field

DI000213 DI

ID of the data item which is used for the data field

DI002060 Data item

Name of the data item which is used for the data field. This name is displayed in the modules as data field heading in case there is no entry in the DF heading parameter. If there is a deviating entry in the DF heading parameter, it will be used as data field heading in the modules.

DI000984 DT

Data table from which the data item of the data field stems

DI010200 DF heading

Here, you can define an individual heading for each data field of a data area. The entry defined here is displayed in the user view of the module instead of the name which is displayed in the data item. For buttons or context menu entries (DF behavior c... and m...), this entry is displayed instead of the module name of the module to be opened.

Notes

• If the data field heading for a particular field is not to be displayed in an area which is no form (Layout parameter = 0 or 1), you have to enter ASCII code 0160 to generate a non-breaking space. To do so, you have to press the ALT key while entering the 4 digits.
• In this field, variables(@D, @G and @(System variables) can be used, the values of which are read when the module is opened.
  • Use a double @ to make sure that the variable (e.g. @D) is not read but an @ sign is actually output in the field. E.g.: If the heading contains @@D15, @D15 is displayed as text in the heading in the module.

DI041088 DF Python ID

Identifier of a data field. It is used in connection with Python to identify the data field.

Notes

• Names must be usable as Python literals. They must not contain any special characters, umlauts, spaces, etc.
• The DF python ID must be uniquely defined in the data area.
• Individual Python IDs must start with an L and the license number.
  • Example: L011_request
• This value can also be preset on the data item in the DI Python ID data field.
  • In this case, the preset Python ID and the "DI:" entry are displayed.
    • If the Python ID in the DI is, e.g., "requested_start", "DI: requested_start" is written in the DF Python ID data field.
  • The preset value can be overwritten. If this value is deleted, the preset from the data item is displayed again.
• The Python IDs of default data fields cannot be changed.

DI000307 DF

ID of the data field

DI000203 Traffic light DI

Here, a traffic light DI is entered which serves to achieve a traffic light function (highlighting of a field depending on the stored values by the means of traffic lights).

Note

• The traffic light symbols overwrite the symbol stored in the Symbol ID data field.

DI027481 Action ID

Here, the ID of the objects which are addressed when carrying out an action is entered.

Details

• A listbox which offers frequently used macros as well as modules which were changed within the last 30 days for selection is implemented on this field.

Actions can be defined for data fields with the following DF behavior:

• c2, c4, c5
• d2, d4, d5
• e2, e4, e5
• f2, f4, f5
• g2, g4, g5
• m4, m5

DI010190 Action

Name of the module, menu item, or macro entered in the Action ID field which is addressed when an action is carried out

Details

• In the module, this name is used for buttons as well as in the context menu. It can be overwritten by making a deviating entry in the DF heading field.

DI000111 LBMOD

Here, the ID of the listbox module is stored if you have selected DF behavior = "li"/"le" for the data field.

Note

• A listbox which offers the modules that have been changed within the last 30 days for selection is implemented on the parameters. It may, e.g., serve as input help if new listbox modules have recently been created which are to be stored as a listbox.

DI009468 @L variable

• Number of the list variables to be referenced The program saves the data field values of marked records in the entered list variable.
  • In the target module, @L must be entered for a data field in Filter from
• Here, a menu item which is to be overwritten is entered for the Overwrite menu items action.

DI000288 Summarization type

Summarization type of the data fields

Values

• 0: No summarization (for DFs "Summarization type" from DI)
• 1: Sum
• 2: Maximum
• 3: Minimum
• 4: Average
• 5: never summarize, always calculate

Notes

• If no value is entered here, the value in the Summarization type parameter of the data item (DT412) applies to the target module.
  • If the value entered here deviates from that of the DI, the value of the DF overwrides the value of the DI.
  • Summarization type = 5 on a data item (DT412) prevents any summarization and does not allow deviating summarization types in the data field (DT411). For fields with relative values, e.g. percentage specifications, summarization does not make sense. The Never summarize, always calculate summarization type on the data item provides the customizer with a means to prohibit this effectively.
• If a summarization type is neither stored on the Summarization type parameter of the data field (DT411) nor on the parameter of the same name of the data item (DT412), the following default summarization type is used:
  • Alphanumeric: Maximum
  • Numeric: Sum
  • Date fields: Maximum
  • The values of the checkbox fields are not summarized, the checkboxes are always displayed as deactivated
• Due to the rounding of individual fields, an incorrect sum may be displayed since it is calculated from the exact values and displayed rounded afterwards due to formatting.

DI001706 Grid

Values

• For histogram data fields:
  • The grid specifies the scale graduations of the histogram scale.
  • Example: When Grid = 100, the y axis of the scale is divided into steps of hundreds (100, 200, 300, etc.).
• For time scale data fields (division of the x axis of the time scale):
  • 2: day
  • 3: week
  • 4: month
  • 5: quarter
  • 6: year:

Note

• The scale size can be customized via the Scale and Grid data fields.

DI040119 LB: Value transfer

This parameter determines which data field from the listbox is transferred.

Values

• : The data field is copied from the listbox.
• : The data field is not copied.

Notes

• You have to make sure that this parameter is used reasonably.
  • I.e., for listboxes on project ID fields, the LB: Value transfer parameter should be activated for the project ID, not for the name.
• If this parameter is not activated for any data field in a listbox, nothing from the list can be copied.
• The parameter can only be activated for one data field in the data area. If it is activated additionally for another data field, the activation will be deleted for the first data field.
• If this parameter is activated, the LB: partial string search field.

DI040815 LB: Partial string search

This parameter defines for the Listbox modules which data fields are considered in the partial string input.

Values

• : The data field is considered in the partial string search.
• : The data field is not considered in the partial string search.

Details

• If the LB: Value transfer parameter is activated for a data field, this parameter is activated automatically. However, it can be deactivated manually.
• In a listbox module you can also set multiple fields or no field at all for the substring search.

Example

• This way you cannot only input the table in the listbox of the DT data field in the Data Dictionary, but also the beginning of the table name in order to filter the LB contents.

Note

• If a listbox contains the value to be copied, a respective name, and an additional detailed description, it is recommended to only use value and name in the partial string search. Including the explanation in the body text will probably produce too many unwanted hits.

DI040118 Input only via listbox

If this parameter is activated, data field input is restricted to the values from the listbox.

Values

• : Data field input is restricted to values from the listbox.
• : Data field input is not restricted.

Note

• If a value which is not contained in the listbox is entered in a listbox data field manually or via Drag&Drop, the input is ignored and the field remains empty. The user must repeat the input or select a valid value from the listbox.

DI001995 Window

Specifies in which subwindow of a module the data field is displayed. The following partition description applies to PLANTA standard. In individual solutions, the data can be divided differently according to customer requirements.

Details

• Window 1: left-hand data window
  • Identifying data (e.g. IDs and names)
• Window 2: central data window
  • Other data (e.g. dates and durations)
• Window 3: right-hand data window
  • Scale fields and items displayed below a scale (e.g. bars).
• Window 9: hidden data window
  • Fields that are hidden when starting the module but can be unhidden by the user. They have the DF options checkbox activated.
  • Fields that are hidden in the module and cannot be unhidden by the user, but that are visible in the filter criteria. They have the Filter criteria checkbox activated and the DF options checkbox deactivated.
  • Fields that are completely invisible for users. They can neither be unhidden by the user, nor be viewed in the filter criteria. Both the DF options and Filter criteria checkboxes are deactivated.

Notes

• If a field in a data area is moved to an invisible window (window 9), the Filter criteria and DF options parameters will be deactivated automatically.
• If a field is to be displayed in window 1 (or window 2), you have to enter a value in the Width W2 (or Width W3) data field in the Other Module Parameters module.
  • When creating a new module in the Modules module, a width will be set for window 1 via the standard value in Width W1. It is therefore not necessary to specify a width explicitly.

DI000221 DF behavior

This parameter is used to define the data field behavior. Depending on the data item of the data field, the listbox on the DF behavior parameter only shows values which are possible for the data field which is currently edited.

{
    "TemplateDf": "template",
    "SampleDataDf": "sample_data",
    "StretchToFill": true
}

Note

• To open a method with data field behavior *5, it must have the following signature:

def my_method(self, applied_dfc, clicked_df):
    pass

DI002926 Mandatory

Here you can define whether a data field is a mandatory data field.

Values

• : The data field is a mandatory data field. When creating or changing a record, an entry must be made in this data field. Otherwise, the change cannot be saved.
• : The data field is not a mandatory data field.

Details

• The Mandatory function can be applied to all fields that do not accept an empty value or zero, since space or zero do not count as entry.
• Using it for checkbox fields is not reasonable since here a check only takes place for activated checkboxes.
• Key data fields (Idents) do not have to be set to Mandatory since they are automatically mandatory entries so that, according to the data base rules, the record becomes valid.
• The mandatory function has no effect on date data fields. It is possible to save even if such a data field is blank. However, it can be queried using another DI.

Note

• For mandatory data fields, an * is displayed automatically behind the heading.

DI000223 Default value

Here, you can enter the value with which the respective data field is filled by default during the creation of a record. Here, the data area must be set to Create = .

Details

• If the required data field is contained in a subordinate area which is set to Create = , but is to be filled with a default value when creating a parent data area, the data field must additionally be included in the creation area with its default value and possibly be set to Window = 9.

Special values

• @/@D/@G/@U: the value of a variable (e.g. today's date or resource) is entered.

DI000220 Sort order

Here, the number is entered/displayed which specifies in which order it is sorted by this field within the respective data area. A minus sign means sorting in descending order (e.g. -1): If no sort order is defined for any of the fields, the respective data area will be sorted by the DDI of the data area.

Details

• The sort criteria take effect when carrying out a search or when clicking on the Sort menu item.
• Sorting only takes effect within a data area.
• It must be specified consecutively.

DI001714 Filter from

Here you can set filter criteria by which the data of a module is filtered. Absolute values or variables can be entered.

Details

• The field can be preset by the customizer. In this case, the data is filtered when the module is opened.
• Or the user can fill the field himself/herself with the required value in the Filter Criteria module. In such a case, the data is filtered after clicking on the Filter or Filter additively button.

Notes

• For virtual data fields, the value in this field is marked red and bold.
• If no filter criteria have been preset, all data will be found when filtering.
• If you often filter on the same data field, it is advisable to set a respective index in the database.

DI001718 Filter to

For description, see Filter from

DI040816 Regular expression

In this field, regular expressions for filtering are stored.

Note

• Filters with regular expressions can only be used for alphanumeric fields.

DI056857 Use filter for

Values

• 0: everywhere
  • For structures, the filter is used at every level.
• 1: only at the top level
  • Filter only takes effect at the highest level (only usable for structures)
• 2: not at the top level
  • Filter does not take effect at the highest level (only usable for structures)

Example

• The IT-ST resource has child resources R48 and R9.
• In the Resource Structure module, only the IT-ST resource and the parent external resource are to be displayed (here R9).
• For this purpose, make the following settings in the data area:
  • Filter from = IT-ST and Use filter on = 1 for the Resource (Resource ID) data field.
  • Filter from = 1E and Use filter on = 2 for the Resource type data field.
• Result: After opening the module, only the IT-ST resource and child resource R9 are displayed.

DI056858 Filter deactivated

If this parameter is activated, all entries in the Filter from, Filter to, Regular expression, and Use filter on parameters of the respective data item are ignored when filtering. For clarity, these 4 fields are grayed out.

DI000234 Symbol ID

ID of the symbol which is to apply to the data field.

Notes

• The value defined here
  • overrides the possible symbol definition at data item level (Symbol ID in DT412) and at skill level (Input field symbol, Output field symbol and Hyperlink symbol in DT030).
  • is overridden if a traffic light is assigned to the data field.

The parameter can be edited in the following module by users with modification rights:

• Basic Data

Details

• For the data field heading, the symbol defined in the Hdg symbol ID parameter applies.

DI002031 Symbol

Preview of the data field symbol which is defined via the Symbol ID parameter

DI010197 Hdg symbol ID

ID of the symbol of the data field heading

Note

• If a symbol for the data field heading is entered at data field level, it overrides a possibly existing deviating heading symbol at skin level (Heading symbol in DT030).

DI010201 Hdg symbol

Preview of the data field symbol which is defined via the Hdg symbol ID parameter

DI029731 Effect ID

ID of the data field effect

Notes

• The effect affects the entire field content (font and background).

DI000258 Format ID

Here, the ID of a date or number or currency format for a data field is entered/displayed.

Note

• The format specified here overrides deviating formats for the corresponding data field which are possibly specified at other levels:
  • at skin level: the formats specified in the Date format, Currency format, or Number format parameters
  • at user level: the formats specified in the Date format, Currency format, or Number format parameters
  • on data item level: the format specified in the Format ID parameter

DI002076 Format

Here, a preview of the format which has been specified for the selected data field in the Format ID parameter is displayed.

DI003701 DF height

Here, the height of the data field in the selected data area is displayed/defined.

Values

• Specified in tenths of a millimeter.

The parameter can be edited in the following module by users with modification rights:

• Basic Data

DI003703 DF width

Here, the width of the data field in the selected data area is displayed/defined.

Values

• Specified in tenths of a millimeter.

The parameter can be edited in the following module by users with modification rights:

• Basic Data

Notes

• If the heading or the value of the data field cannot be displayed in the set width at the surface of the respective module, the data will be truncated and displayed with an ellipsis.
• If the cursor hovers over the truncated data, the complete data is displayed in a tooltip.

DI027098 Hdg height

Here, the height of the data field heading in the selected data area is displayed/defined.

Values

• Specified in tenths of a millimeter.

DI027099 Hdg width

Here, the width of the data field heading in the selected data area is displayed/defined.

Values

• Specified in tenths of a millimeter.

DI000232 Y Pos. H

Here, the Y position of the data field heading in the selected data area is displayed/defined.

Values

• Specified in tenths of a millimeter.

Notes

• This parameter only takes effect in data areas with Layout = 2 (form).
• Data field headings cannot be displayed in the module without the corresponding data fields.

DI000233 X pos. H

Here, the X position of the data field heading in the selected data area is displayed/defined.

Values

• Specified in tenths of a millimeter.

Notes

• This parameter only takes effect in data areas with Layout = 2 (form).
• Data field headings cannot be displayed in the module without the corresponding data fields.

DI000230 Y pos. F

Here, the Y position of the data field in the selected data area is displayed/defined.

Values

• Specified in tenths of a millimeter.

Notes

• This parameter only takes effect in data areas with Layout = 2 (form).
• Data fields can be displayed in the module without the corresponding data field headings.

DI000231 X pos. F

Here, the X position of the data field in the selected data area is displayed/defined.

Values

• Specified in tenths of a millimeter.

Notes

• This parameter only takes effect in data areas with Layout = 2 (form).
• Data fields can be displayed in the module without the corresponding data field headings.

DI022738 Alignment

Determines the alignment of the data field.

Values

• 0: no alignment
• 1: left aligned
• 2: centered
• 3: right aligned

Notes

• Checkboxes are always centered, regardless of the alignment.
• Number fields are right-aligned and text fields are left-aligned by default.

DI001992 Pos.

Automatically incrementing position number. When moving via Drag & Drop moving and creating a data field, the pos. is set automatically. In modules in which data fields are created, this field should be the first sorting criterion in window 9.

Note

• The position is the tab order of the data fields at the same time.

DI040869 Hotkey

The entered value defines a shortcut for activating the corresponding button.

Example:

• Value: A
• In the module, the respective button can be activated via the ALT + A key combination.

DI040918 Tooltip

Here you can store a fixed tooltip. It will be displayed when the cursor hovers over the corresponding field in the target module. 

The following variables can be used:

Example

Information

• The field is an I-text field, which means that the tooltip texts stored here can be translated in the translation modules.

DI003388 DF options

This parameter serves to determine whether data fields in the context menu for hiding/unhiding of data fields can be hidden/unhidden.

Values

• : The data field can be unhidden/hidden.
• : This data field cannot be unhidden/hidden.

Note

• If a field in a data area is moved to an invisible window (window 9), the DF options parameter is deactivated automatically.

DI059179 Bar modification mode: Create bar

Activating this checkbox enables the graphical creation of the bar. It is recommended to only set one date type to "create" (e.g. actual dates or requested dates).

DI059181 Bar modification mode: Edit dates: MI "Actual"

Activating this checkbox enables the

• graphical editing of dates of the respective bar with Edit → Task actual start and Edit → Task actual end.
• scrolling to actual dates via the View → Bar tracking menu items.

DI059180 Bar modification mode: Edit dates: MI "Requested"

Activating this checkbox enables the

• graphical editing of dates of the respective bar with Edit → Task requested start and Edit → Task requested end.
• scrolling to requested dates via the View → Bar tracking menu items.

DI059186 Bar modification: Link Bar

Activating this checkbox enables you to graphically link the bar, change the link type by right-clicking, and delete the link in the Gantt chart.

Requirements

• In the link area, a Linkage DI is available for the bar you wish to link.

DI059183 Bar modification: Edit Start

Activating this checkbox enables the graphical editing of the start dates

DI059184 Bar modification: Edit End

Activating this checkbox enables the graphical editing of the end dates

DI059268 Bar modification: Move

Activating this checkbox enables the graphical moving of the bar

DI059185 Bar modification: All modifiable

Activating this checkbox enables the graphical moving of the bar as well as the editing of the start and end dates

Note

• When activating this checkbox, the following checkboxes are activated automatically
  • Bar modification: Move
  • Bar modification: Edit Start
  • Bar modification: Edit End

DI051832 Bar link (DF Python ID)

By entering the DF Python ID of a bar, this data field becomes an auxiliary bar field. It is displayed at the position defined in the Docking point parameter. Note

• The auxiliary bar field must be located in the same field as the respective bar.

DI040921 Bar link (DF ID)

By entering the DF ID of a bar, this data field becomes an auxiliary bar field. It is displayed at the position defined in the Docking point parameter. Note

• The auxiliary bar field must be located in the same field as the respective bar.

DI040917 Dock point

This parameter serves to determine the position of the auxiliary bar field defined in the Bar link (DF Python ID) data field.

Values

• 0: starting point is bar start
• 1: starting point is bar end
• 2: starting point is bar center

Tip

• When you use "0” as a value for positioning an auxiliary field infront of the bar, the data field width and the X position of the field should be defined in addition (e.g. DF width = 200, X pos. F = -200), so that the field is not positioned at the bar itself.

DI026689 Multiline

This parameter controls whether line breaks are possible in the respective data field.

Values

• : By pressing enter, a line break is inserted. If the DF width is reached, an automatic line break occurs.
• : By pressing ENTER you navigate to the next input field. If the DF width is reached, the data is displayed truncated with an ellipsis. If the cursor hovers over the truncated data, the complete data is displayed in a tooltip.

DI027601 No. of lines

For data fields for which the Multiline parameter is activated you can use this parameter to define how many lines may be written in this data field.

Notes

• If the maximum number of lines is reached, no other manual line breaks or no other text can be entered, if this causes an automatic line break. In such a case, the The maximum amount of lines in the continuous text field has been reached. message is displayed.
• The corresponding data field is hidden by default but the user can unhide it if required.
• Values from 0 to 9999 can be entered.

DI001993 Filter criteria

This parameter defines whether the data field is displayed in the Filter Criteria.

Values

• : The data field exists as a filter criterion in the option form.
• : The data field does not exist as a filter criterion in the option form. However, an entry in the Filter from or Filter to takes effect regardless.

Notes

• If a field in a data area is moved to an invisible window (window 9), the Filter criteria parameter is deactivated automatically.
• Can be used for filter criteria which the user can neither see nor change.
• Can be used for data fields which cannot be searched for, e.g.: Date, histogram bars, projection values, summarized values.
• Especially in multi-user mode, large sequential search runs can cause computer overload. It is therefore recommended, especially where bulk data is involved, to limit the filter criteria which are visible to the user.

DI029687 DF output

Preview of the data field heading as it is displayed in the module.

DI003102 DF type

The field is automatically filled with the value from the (DF type) field of DT412.

DI040844 Incarnation DI

The field is automatically filled with the value from the (Incarnation DI) field of DT412.

DI040843 Fetch exit DI

The field is automatically filled with the value from the (Fetch exit DI) field of DT412.

DI040845 DI class

Here, the class of the hyperlink is displayed.

DI041524 Listbox module

Here, the title of the listbox module stored in the LBMOD data field is displayed.

DI041308 DBOLE value

Here, the ID of the OLE object is displayed which is used on the data field. The field is automatically filled as soon as an OLE entry has been made in the Default value field. For more information, please refer to the Embed OLEs section of Module Workflow Level 1.

DI040904 IronPython script

On this parameter you can store IronPython scripts that are carried out on the client. This allows you to customize a sort of value range on the part of the client.

Notes

• In order to run !IronPython scripts on the client, the DF behavior must be set to py.

DI040968 Data field configuration

On this parameter you can store configuration parameters for data fields.

Usage

• For IronPython and Python scripts, e.g. for changing person/resource IDs
• For storing the IDs of the tooltip modules
• For the parameter settings of the date listboxes (calendar listboxes) with calendar control function
• For client specific data field configuration

  • Parameters that are used on the part of the client can be declared.

    #START DF client config. chart_usage=True #END

    CODE

• For configuring the Adaptive Card data fields

• For configuring the context menu button
• For storing a tooltip module
  • To store a tooltip module you can also use the data item configuration if the tooltip module is to be displayed in all modules in which the respective data item is used. If deviating tooltip modules are entered in both parameters, the entry in the data field configuration overrides the entry in the data item configuration.

{
   "Tooltip": {
      "Module": "xxxxxx"
   }
}

DI056920 Print text

Here, an individual print output text or variables for print output objects can be defined for a print area.

Possible variables:

• @mod_name - module name
• @cur_column - current column
• @cur_row - current row
• @cur_page_h - current page (horizontal counting)
  • 1,2,3
  • 4,5,6
• @cur_page_v - current page (vertical counting)
  • 1,3,5
  • 2,4,6
• @total_pages - page number
• @date_time(F) - time specific for the print preview
• @date_time(h:mm:ss) - time specification
• @date_time(dd.MM.yy HH:mm:ss) - time for the print preview
  • In these variables, only standard format strings can be used. For further information, please see here.

DI041307 DBOLE

Preview of the OLE object which was assigned to the data field.

DI000106 Structure summarization

Summarizes data fields in data areas with Structure display = along the structure (e.g. planned load along the project structure)

DI062619 Active

Marks the data field as active or inactive, depending on whether the respective data item is active or inactive.

Note

• If you try to assign an inactive data item to a data area as a data field, a message indicating this is displayed.

DI066279 Active chart variant

Defines which chart variant is to be displayed if there are multiple chart configurations for a data field.

The parameter can be edited in the following module by users with modification rights:

• Chart Variants