Data not reflecting in audit trail but field got updated

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.

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

Idea
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

    • 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 ...

    • 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 ...

    • How to push CFS Fields(non-Filetype) for Opportunity? | API

      Query: >> In Opportunity I am trying to insert fields within a field set. I tried replicating the solution for Leads section as provided in the API Docs page but getting error. Solution: To do that, please retrieve the schema names using the steps ...

    • Can Enabling "Allow non-lead email address(es) in the CC field" Setting Generate Unwanted Leads in LeadSquared?

      Query: The client wants to avoid the creation of junk or unwanted leads in LeadSquared when enabling the "Allow non-lead email address(es) in the CC field" setting. What steps can the client take to prevent this situation? Solution: To prevent this ...

    • Lead field is Going in a Queue

      Scenario: User has reported that even for single lead field creation request was going in queue and was getting processed after working hours. Root cause: When the system reaches the limit of 300 lead field, system marks tenant as is large, and it ...