We have a running application that's been working fine using SDK v122.0.2. As part of some minor maintenance I updated it to v132.0.0 and immediately round that a call to RoutingAPI.GetRoutingQueues wasn't returning any queues.
By progressively rolling back the PureCloudPlatform.Client.V2 package I found that something changed in v127.0.0 that's preventing GetRoutingQueues from working. The documentation hasn't changed and there's nothing in the Release Notes that indicates there's a breaking change.
Have I missed an Announcement or is there something in the Release Notes that I',m missing?
The SDKs are generated from a swagger JSON file describing the API interface. The order of function parameters in then SDKs is based on the order in the JSON file. The order of the pageSize and pageNumber parameters in GetRoutingQueues swapped unexpectedly in v127.0.0 causing this breaking change.
In the future generation of SDKs we will alphabetically order the parameters to avoid issues like this but making that change now would cause too many breaking changes.
Currently, the only way of avoiding this issue is to use named arguments for SDK API calls.
Thanks for the prompt reply - that explains the issue. Unfortunate as this undocumented change is, it can be easily fixed using named arguments. In fact, it sounds like it might be wise to use named arguments for all the SDK API calls if there are future changes of this type planned.