Skip to main content

Reference

 

OutSystems

Coherence Suggestion Warning

This warning is issued to notify you that there is an incoherence in the element definition and/or the way you are handling that element .

The Coherence Suggestion warning is issued in the following situations:

  • 'Input' is declared as non-mandatory but <attribute> is mandatory

    You have an Input widget that handles an attribute value and the Mandatory property of the widget and attribute do not match. This occurs when, for example, you have an Edit Record widget used to edit an entity record and one of the entity attributes is declared as mandatory while the corresponding Input widget has False explicitly typed in the Mandatory property expression.

    Either the Input widget Mandatory property should be explicitly True or an expression (evaluated only at runtime), or the attribute should be non-mandatory. Check which is more suitable for your module and fix the corresponding property.

  • 'InputPassword' is declared as non-mandatory but <attribute> is mandatory

    You have an Input Password widget that handles an attribute value and the Mandatory property of the widget and attribute do not match. This occurs when, for example, you have an Edit Record widget used to edit an entity record and one of the entity attributes is declared as mandatory while the corresponding Input Password widget has False explicitly typed in the Mandatory property expression.

    Either the Input Password widget Mandatory property should be explicitly True or an expression (evaluated only in runtime), or the attribute should be non-mandatory. Check which is more suitable for your module and fix the corresponding property.

  • 'Max. Length' of Input (<size>) and <attribute> 'Length' (<size>) values should match

    You have an Input widget that handles an attribute value and the length does not match with the size of that attribute. This occurs when, for example, you have and Edit Record widget used to edit an entity record and one of the entity attributes has a Length different from the Max. Length property of the corresponding Input widget.

    Either the Max. Length of the Input widget should be updated or the Length property of the attribute should be updated. Check which is more suitable for your module and fix the corresponding property.

  • 'Max. Length' of Input Password (<size>) and <attribute> 'Length' (<size>) values should match

    You have an Input Password widget that handles an attribute value and the length does not match the size of that attribute. This occurs when, for example, you have an Edit Record widget used to edit an entity record and one of the entity attributes has a Length different from the Max. Length property of the corresponding Input Password widget.

    Either the Max. Length of the Input Password widget or the Length property of the attribute should be updated. Check which is more suitable for your module and fix the corresponding property.

  • You should use an attribute from ‘<table | list records name>’ current record for the <input widget> ‘<input name>’ variable

    You have an input widget (Input, Input Password, Select, etc), inside a Table Records or List Records widget, that handles a variable that is not bound to the List runtime property of the list with records being displayed. In this situation, the attribute associated with this variable will have the same value in all the records and this value corresponds to the last value provided by the end-user.

    If you want to update a set of records correctly, in a Table Records widget or a List Records widget, the Variable property of the input widget should be obtained through the List runtime property. For example: TableRecords1.List.Current.Customer.Name

  • <query> 'Max. Records' should be set to '<number>' to match the number of records presented by <widget>

    You have a Table Records widget or List Records widget that presents a set of records different from the ones fetched by the associated query.

    Check the Max. Records property of your aggregate or SQL query and update this property with the value suggested in <number>, based on the properties of Table Records widget or the List Records widget: either the value of the LineCount property, if StartIndex is 0, or the value StartIndex + LineCount + 1, otherwise. In this situation, you have the guarantee that you are fetching as many records as you need to display.

  • 'Special Variable' will always be empty because 'Special List' is not specified

    You have a Combo Box widget that is not populated with generic values but the Special Variable property is set. This property is only necessary to gather the end-user input when generic values are displayed, i.e. the Special List property is set.

    Edit this Combo Box widget and delete the variable associated with the Special Variable property because this variable is ignored by Service Studio.

Double-click on the error line to take you directly to the property that is not coherent or might not be coherent in some circumstances.

  • Was this article helpful?