Previous Topic

Book Contents

Book Index

Next Topic

Subtab - Properties
  • Image Attribute

    Enables assignment of the selected business object attribute as attribute storing information that can be used as an image source in the 'Multiline catalog customizer' and for the 'Single Picture Control' in views.

    This property is available for String attributes only.

  • Color Attribute

    Applies to Integer type only. This attribute can save and hold a color value (i.e. the value of the attribute is a color). If selected here (Name: Color Attribute, Value: True) and added as an attribute in the View Customizer on the Group Layout Tab, then you can double-click the field on the final view to call a Color Picker where you can pick a color. Currently this feature is used for Styles only which are described in this topic in detail.

  • Read Only

    Select the check box for an attribute intended only for reading. As a result, the corresponding column will not get updated even if the value in the field is changed.

  • Ignore Calculation on DB

    If 'Ignore Calculation on DB' is set to true, then grouping according to a calculated persistent attribute is performed on the database, despite the fact that normally grouping according to a calculated attribute should be performed in the memory.

    Explanation: The preferred way of persistent attributes grouping is grouping on the database. Calculated attributes are usually transient and thus can only be grouped in the memory. A calculated persistent attribute (which is a rather non-standard yet possible scenario) can strictly technically be used for grouping on the database but the standard way of grouping according to any calculated attribute is grouping in the memory because this way we can be sure that correct, current values are used.
    'Ignore Calculation on DB' overrides this standard approach and enables database grouping according to a calculated attribute, thus trusting the calculated values stored in the database.

    The 'Ignore Calculation on DB' property should be used with care. The following example demonstrates why grouping according to a calculated attribute should be done in the memory even if the attribute is persistent:

    Example: An object type has persistent attributes 'Price', 'VAT' and a calculated attribute 'Price with VAT'. If, for some reason, the calculated attribute 'Price with VAT' is persistent, then the following inconsistency may occur:

    • Objects of this object type are created with VAT value current at the moment, their 'Price with VAT' values are calculated accordingly and saved.
    • VAT value changes. Objects are viewed with new 'Price with VAT' dynamically calculated but because they are not re-saved, the original 'Price with VAT' values still reside in the database. If grouping on the database is performed ('Ignore Calculation on DB' set to true) according to this attribute, it is based on incorrect data.
  • Bar Code Type

    Enables assignment of the selected business object attribute as attribute storing barcode information. This feature may be useful when a barcode reader is used for scanning the printed output. Read more about Barcodes in VM.

    See also: Assign Images to Specific Objects and Assign Images From Attachments.

See Also

Attributes Tab

Subtab - Styles

Subtab - Format

Subtab - Defaults

Subtab - Description

Deleting Object Type Attributes

Generating and Comparing DLL Scripts

Full Text Index (FTI)