Data not reflecting in audit trail but field got updated
Hi Team,
You can get the issue where lead field is updated perfectly but in audit trail, there will be no audit logs present.

Reason
This will only happen in the case where lead will be updated via API.

Solution
Audit trail will only pick up the log if schema name is exact as in the lead field settings. PFB the example:-
In Lead field schema name is - mx_Risk_Category
In API schema name pushed is:- mx_risk_category
So in this case, field value will be updated but log will not be captured in audit trail. Kindly get this corrected by the customer spoc.
Related Articles
User Retrieve API Exception
Hi Team, This is to let you know that there is an exception in all user retrieve APIs that, if you retrieve users in the account then in response, you will not get any custom user fields which is of dropdown types. To get all those details you need ...
Data fetch issue | Activity based reports
Issue reported: The "Activities by User (Historical)" report does not fetch the complete data of all the activities selected using the "Activity Type(s)" dropdown. Solution/ Findings: This is the default behaviour of the system wherein: 1. If there ...
Export data from Grafana
You can check the API logs tenant-wise using the below URL: Grafana API Logs. The API logs will display the count of each API within the filtered time range. The responses and the count of each response will also be reflected. This data can be ...
Why some form field's data is not pushed to pre-validation Lapp?
Issue: On form submission, not all field values are pushed to pre-validation Lapp. Root cause: In the Dynamic form, under additional setting if the 'Post only modified fields' is enabled, then only the values modified after submiting the form will be ...
Get Tasks by Lead Id give data in ascending order
https://{host}/v2/LeadManagement.svc/RetrieveTaskByLeadId?accessKey=AccessKey&secretKey=SecretKey&leadId=LeadId The API RetrieveTaskByLeadId helps us retrieve task data in ascending order, sorted by the task's due date, not the created on date.