Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why is Aktion DataLink/400 creating documents containing incorrect Computed for Display fields?

April 26, 2017aktion computed containing creating datalink display documents Fields

0

Posted

Why is Aktion DataLink/400 creating documents containing incorrect Computed for Display fields?

1 Answer

0

Posted

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.