Import

• The names no longer must match, as in earlier releases. The data maintained in the Field Relations (Import) (daxch0122s000) session is used to link table fields with ASCII fields.
• For inserts the full functionality is available, such as constants, conditions, and relations.
• Full functionality is also available for overwrite (inserting an already existing record), as long as the Condition field returns true.
• Full functionality is also available for deletes, however, note that only the key fields are assigned their values. For this reason, conditions, that are attached to non-key-fields and that have side effects, will most likely not work correctly.
• Note that relations based on Increment are meaningless for deletes.

Providing the full functionality for updates is extremely difficult:

• Relations for which the Based On field is defined as Default, Fixed Value, or Increment are ignored because these relations are not useful.
• Relations based on Field Value or Conv. Table can be used without any restrictions. However, these relations will only be applied on key-fields (old values) and changed fields (new values).
• Because the audit server only logs key-fields and changed fields for an update, the other fields are not known. As a result, many fields in the ASCII file will remain empty. If conditions are used, you cannot see whether all accessed fields have valid values. If not, you most likely must not run the condition. To ensure flexibility of conditions, even if you use audit, you can use the Condition field condition to guard conditions. It is assumed that this condition decides whether the condition (at field value level) can return a proper value. For this the function changed (<ascii_file>_<field>) can be used in your condition.
• Note that, by the introduction of parameters by condition, all accessed ASCII fields are known and, as a result, you can determine whether all ASCII fields have valid values. However, this knowledge has not been explored in the current version.
• You can access the former value of the ASCII field by means of not.curr(<ascii_file>_<field>) old.value = <ascii_file>_<field> not.curr(<ascii_file>_<field>) | restore new value! The former value of the tablefield is in the table field itself (first the condition is executed, and only on returning the value is assigned to the tablefield.

Regarding the logging of values that have not been changed, the behavior of the audit server can be adapted. By changing the audit profile, you can force the audit server to log values for one or more table fields even if the fields have not been changed in an update action. For more information, refer to the Audit Configuration Management topic in the LN Tools section in the Web Help.