Description: If the customer tries to map custom field in UTC generic instance for call logs, not all custom fields will get updated even if added in the configuration passed in the call log payload.
Example: In one of the accounts, they were passing the below payload:
{
“SourceNumber”: “XXXXXXXXXX”, “DestinationNumber”: “XXXXXXXXXX“, “DisplayNumber”: “XXXXXXXXXX“, “StartTime”: “2023-11-02 11:41:52”, “EndTime”: “2023-11-02 11:42:45”, “CallDuration”: “00:00:53”, “Status”: “Answered”, “CallNotes”: “General Enquiry”, “CallerSource”: “General Enquiry”, “ResourceURL”: “XYZ”, “Direction”: “Outbound”, “CallSessionId”: “XXXXXXXXXX“, “AgentName”: “user@poonawalla.com”, “mx_Custom_9”: “answered”, “mx_Custom_10”: “”, “mx_Custom_11”: “”, “mx_Custom_12”: “General Enquiry”, “mx_Custom_13”: “00:00:38”, “mx_Custom_14”: “test call”, “mx_Custom_15”: “answered”
}
Here, custom fields 9 to 15 are passed, but the mx_Custom_9 and mx_Custom_15 were not posted in the outbound activity:
Reason: UTC Generic instance supports custom fields 10 to 14 only.
