Using the Field Change History feature, you can track and audit changes to specific field of a price list. By default, field tracking is not enabled. Administrators must configure which fields they want to track. Once field tracking is enabled for a field (for example, Effective Date), the system begins capturing the following changes:

Initial price list creation: When a price list is created, the Field Change History displays the initial field values with creation details. The New Value column shows the field's initial value in green, while the Previous Value remains empty. The Modified By and Modified Date columns display the user who created the price list and the creation time stamp.

Field updates: When tracked fields are modified, the Previous Value column displays the prior data in red, and the New Value column shows the updated data in green. The Modified By and Modified Date columns capture the user details and the time stamp of each change. The most recent changes appear at the top.

Along with the above information, you can filter, sort, export the data, and use the pagination feature.

Filter: The filter functionality includes all fields based on the criteria configured by the Admin via API, along with date range and user-based filters.

Export: Select the required data and export the same in CSV or Excel format.

Pagination: Use the pagination feature to view older modifications. Click on the column header to change the ascending/descending sort order for Field Name, Modified By, and Modified Date columns.

API: Administrators can enable or disable field tracking for a specific field in an object using the API. All fields, including standard and custom, are allowed for tracking.

The API is /api/audit/v1/field-history-tracking-config

Add: To enable any new field for the field change tracking, add the field in the existing JSON and call the PUT API.

Remove: To remove a field from field change tracking, you must delete the field change tracking of the object from the Delete API followed by PUT API to add only needed fields (by removing the non-needed field in the payload).