- Newest
- Most votes
- Most comments
I found that the report setup in Amazon Connect portal had automatically been set to "Agent" in the Metrics tab when it should have been Contact. I set it to contact, clicked "Apply" and then clicked "Save Report" (don't skip this) and it worked. BTW thanks for looking this over Clarence!
So I have managed to get the trigger to run. The prefix was the issue, I had wrongly put in the Bucket Name before the rest of the path. Now I am getting this error in the lambda function logs when it tries to push the report into Salesforce: INVALID_FIELD: No such column 'amazonconnect__Adherence__c' on sobject of type amazonconnect__AC_HistoricalQueueMetrics__c
I have looked and no such field exists in the SF object. I have unticked the field in the metric tab in the reports in the Amazon Connect portal and it is still included in the report columns. How can I remove this field from the sfIntervalQueue and sfIntervalAgent report?
Relevant content
- asked 22 days ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
have you try to schedule the report again? Best thing to do is delete the save report, recreate and reschedule specifying the proper prefix. Check in your S3 location for the CSV file to confirm. And you might need to either manually modified the already existing reports, or simply delete them in S3.