5.16 sfContactTraceRecord Lambda updates fields in Salesforce that do not exist in the 5.16 Salesforce package

[reecegoslin]

The amazonconnectDisconnectReasonc field does not exist in the 5.16 version of the Salesforce managed package.

Reproduction Steps:

• Install 5.16 Salesforce managed package to Salesforce with CTR Import parameter
• Install 5.16 Salesforce lambda package from SAR
• Call with a flow that sets the postcallCTRImportEnabled attribute
• Check logs on sfContactTraceRecord lambda

Stack Trace Below:

[ERROR] Exception: INVALID_FIELD: No such column 'amazonconnect__DisconnectReason__c' on sobject of type amazonconnect__AC_ContactTraceRecord__c Traceback (most recent call last):   File "/var/task/sfContactTraceRecord.py", line 45, in lambda_handler     raise e   File "/var/task/sfContactTraceRecord.py", line 40, in lambda_handler     process_ctr_record(event['record'])   File "/var/task/sfContactTraceRecord.py", line 55, in process_ctr_record     create_ctr_record(record_obj)   File "/var/task/sfContactTraceRecord.py", line 141, in create_ctr_record     sf.update_by_external(objectnamespace + "AC_ContactTraceRecord__c", objectnamespace + 'ContactId__c', ctr['ContactId'], sf_request)   File "/var/task/salesforce.py", line 114, in update_by_external     self.makeRequest(self.request.patch, **{"url": url, "data": data})   File "/var/task/salesforce.py", line 183, in makeRequest     return requestMethod(**kwargs, headers=self.headers)   File "/var/task/salesforce.py", line 227, in patch     return __check_resp__(r)   File "/var/task/salesforce.py", line 253, in __check_resp__     raise Exception(msg)

[reecegoslin]

@yingdoli Is a Salesforce managed package with the Disconnect Reason field going be published to the AppExchange? The only workaround I've found here is altering the Cloudformation Template to point to a previous version of the sfContactTrace record lambda.

[ataraxg]

Commenting line 106 of the sfContactTraceRecord.py file is fixing the issue

[yiming-amzn]

Yes in Lambda version v5.16.2 we have commented out that line for a workaround, we are targeting to release v5.17 soon with that field exists on both lambda and CTI Adapter side.