Auditing is turned on for an object, such as the Project Object, but when I update an audited attribute and save, the New Value field on the Audit Tab is not populated, why?

Document ID : KB000023909
Last Modified Date : 25/07/2018
Show Technical Document Details


When a new custom value is added to a custom lookup attribute or a stock lookup attribute, and the value is changed on the application side, on Save the New Value field on the Audit tab is not updated, but instead it is blank.

Steps to Reproduce:

  1. Under Data Administration | Lookups, create a static lookup and add some values for it.
  2. Go to Objects and add this lookup to the Project object as an attribute.
  3. Under Project View on Create mode, add this attribute on the General section.
  4. Under Project View on Edit mode, add this attribute under Admin link.
  5. Publish the changes.
  6. Add lookup attribute to Audited Attributes on the Audit Trail Attributes for the Project Object.
  7. Go to Portfolio Management | Projects, and create a new project.
  8. Select a value for the custom lookup when creating the project.
  9. Verify on the Audit tab that the attribute displays with a value.
  10. Go to the lookup and add a new value.
  11. Go back to the Project, and change the current value for the newly created value.
  12. Check on Audit tab to verify the new value displays.

Expected Result: New value is displayed in the New Value field.
Actual Result: The New value field is blank.




  1. Access the object being audited.
  2. Click on Audit Trail.
  3. Remove the attribute from the Insert, Update and Delete attribute audit boxes.
  4. Click Save.
  5. Now re-add the lookup back for the audit conditions Insert, Update and Delete.

The following solution will only work for 'Dynamic Query Lookup' definitions. It will not work for Static Lookup Definitions.

If the workaround does not update the auditing to show the new lookup value, the trigger definition that is created when the attribute is selected for audit may not have been removed and recreated. Use the following steps, be sure to fully test in a NON-production environment first. Please contact CA Technical Support for assistance if you encounter this issue.

  1. Drop the audit definition from the Clarity Administration Audit Trail page (again)
  2. Go into the database and see if the function or part of the function is still in the database.
    TThe update trigger for the object table contains a reference to an audit function ODF_AUD_nnnnnnn_FCT function, where 'nnnnnnn' is the internal record id of the field for the custom defined attribute.
  3. If the function is still present in the database, then manually remove the function (ODF_AUD_nnnnnnn_FCT) from the database
  4. Recreate the audit definition from the Clarity Administration Audit Trail page