Dialer API Code

Platform API
1

I am having this error when uploading a contact list via API. i know this is a new Feature.

System.Net.WebException: The remote server returned an unexpected response: (400) Bad Request.
{"status":400,"code":"cannot.have.callable.time.column.with.automatic.time.zone.mapping","message":"An attempt was made to create an invalid ContactList. Details: CANNOT_HAVE_CALLABLE_TIME_COLUMN_WITH_AUTOMATIC_TIME_ZONE_MAPPING","messageWithParams":"An attempt was made to create an invalid {entity}. Details: {CANNOT_HAVE_CALLABLE_TIME_COLUMN_WITH_AUTOMATIC_TIME_ZONE_MAPPING}","messageParams":{"CANNOT_HAVE_CALLABLE_TIME_COLUMN_WITH_AUTOMATIC_TIME_ZONE_MAPPING":"CANNOT_HAVE_CALLABLE_TIME_COLUMN_WITH_AUTOMATIC_TIME_ZONE_MAPPING","entity":"ContactList"},"contextId":"55b9341f-8329-4f79-b182-e4fd668c25b6","details":[],"errors":[]}

1 Like
2

https://developer.mypurecloud.com/api/rest/v2/outbound/uploadcontactlists.html is the API we are using.

3

It would be helpful with this new feature, if "Automatic time zone mapping" is off, if not specified. From what it looks like, it is required information to send. Thank you!

4

Have you tried removing the callable time column or turning off automatic time zone mapping?

5

we have verified that the Automatic Time zone mapping is turned off in the campaign that we are referencing. i am not sure what you mean by removing the column as that is needed to dial regardless. Thank you.

6

I'm guessing at what you might be doing based on the error message you're getting since I don't have any insight into your configuration. If you can share more information, like the configuration of your campaign and the format of your call list that you're uploading, that would help with troubleshooting the issue.

7

There are 2 campaigns, one preview and one Predictive both with default settings. We are mapping Time Zones based of column correctly as well as Call Analysis is setup as default.

The customer used BizTalk to talk to the API above to create and update the Contact list via that API. it was working up until yesterday which was prompted for the thread. Do you know if there was any changes to the API with the Updates yesterday, the error code suggests that we are missing a field thus causing a malformed syntax.

8

I've been discussing this with the dev team and they have asked that you open a ticket with PureCloud Support for further investigation.

9

Will do and done. Thank you.

10

Our development team found the issue, the AutomaticTimeZone setting in the code was set to "true". We are making coding changes to change it to "false". This did bring up a question, as it appears the release on May 9 is when this feature went live. Can we code to a specific API version and upgrade only after we do thorough testing?

1 Like
11

There is only ever one version of the API, and it's the one that's live in production. There generally aren't supposed to be breaking changes like this. However, we are working on better processes to announce when there will be changes that may have an impact to customer apps. Keep an eye on the Announcements category for that information.

12

Thank you Tim, I appreciate your response!

13

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.