Why is Aktion DataLink/400 creating documents containing incorrect Computed for Display fields?
There is currently a problem with the way the Notes document creation API handles Computed for Display fields. If all of the computed fields on the form are defined as Computed for Display, the API will incorrectly insert these fields into the new document, and the Computed for Display feature will not work. This can be easily prevented by also defining at least one Computed field on the form (even if it is a hidden field), if Computed for Display fields are going to be used. The API will create the fields properly if both Computed and Computed for Display fields are defined.