UDF created via API not visible in engagement (2014)
SYMPTOMS
Data for custom fields for an engagement has been added via the API and the entries in the tables (like UDFText, UDFNumber, ...) are in the database.
Yet, when checking the engagement in the user interface, the values for the custom fields are not displayed. The fields are shown as empty.
RESOLUTION
Please check the value in the column 'additionalid' in the UDF tables. For engagements, this must correspond to the billingOfficeId. In case this is not the correct ID, the user interface will not display the field values that are in the DB.