Hi All,
I'm using the Python SDK RoutingApi to get the "Routing Activity Query".
But when using the method indicated in the API Explorer information (post_analytics_routing_activity_query) I am missing the "qualifier" and "secondaryQualifier" attributes that we get in the Web invocation.
The version of the PythonSDK is PureCloudPlatformClientV2-219.0.0
Does anyone know is this is working as expected?
Hello,
I just had a look at it and the issue is coming from missing information in the endpoint specification (I mean Swagger specification for this endpoint, coming from annotations in the Java code, that we use to automatically build the different Platform API SDKs).
The "RoutingActivityMetricValue" model/class that is leveraged in the API Response for POST /api/v2/analytics/routing/activity/query only has metric and count attributes defined in its annotations/swagger.
It is missing the definition of qualifier, secondaryQualifier, entityIds, .... attributes that are sent back by this API Endpoint for some of the data.
Unfortunately, with the Python SDK, only attributes listed in the Model/Class are extracted when deserializing from JSON to Python Object. The raw JSON (received in the response) is not kept.
So you are indeed receiving qualifier and secondaryQualifier in the API response - but the info is lost after deserialization.
Could you please open a ticket with Genesys Cloud Customer Care and report the issue?
We need to go through this process so Support can ask engineering to make the correct modifications if this was a miss, and notify you if/when the change is done.
You can reference this dev forum post in the case (so they see the mention of "RoutingActivityMetricValue" or can contact me if something is unclear).
Regards,
Hi Edgard,
Can you please drop the care ticket here? Our Care team will sometimes refer people back to the Developer Forum so if that happens we can help shepherd it to make sure it does not inadvertently get closed.
Thanks,
John Carnell
Director, Developer Engagement
An update on my previous message.
I just noticed that the needed change to the annotations to display these attributes in the Platform API specification (swagger) has been made yesterday. It hasn't gone to production yet. That's why it is not in the SDK yet. It may take a week or two before it is propagated to production and to the SDK. But it is not necessary to request this change via Customer Care (as it's done already - just not in production yet).
Regards,
Hi Guys,
As @John_Carnell said, I opened a Care Case a they sent me to the devoloper forum. The case number is 0003646308.
Thnaks @Jerome.Saint-Marc for all the information and I will wait then for the production deplyment
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.