Limitations

The limitations:

1. Only missing table columns are handled in a fault-tolerant way. Missing tables are not.
2. Fault-tolerant handling is not used in these situations:
   1. When a column is part of index 1.
   2. When a column linked to an identifying attribute of component.
   3. When a column is used in component implementation relationship.
   4. When a column is used in component implementation table relationship (join of a non-root table).
   5. For customized fields (see Customizations in LN Business Interfaces).
3. Attribute implementations must use a domain that exists in all application versions for which the BII is used. If not only the column does not exist in some versions, but also the domain of that column does not exist, the attribute implementation must use another domain. It is no problem to use a non-existing domain in the table artifact, as long as the attribute implementations use a domain that exists in all application versions for which the BII is used.

   Note that this will result in a warning when generating the implementation

   (LN constraint: Attribute implementation MyObject.MyAttributeImplementation should not have a data type specified, because it is mapped directly to a table column

   As long as you ensure the used data types (domains) in attribute implementation and column are compatible you can ignore this warning.
4. Function server implementations are not taken into account. Note that they can have issues that are comparable to tables: in new releases new form fields can be added.
5. The solution does not cover filter hooks.