We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Search API currently does not work with sort. The sort options in the request are ignored.
I found this when trying to search on contact with a sort by lastmodifieddate.
body = { "sorts": [ { "propertyName": "lastmodifieddate", "direction": "ASCENDING" } ], "limit": 100, } api_response = api_client.crm.contacts.search_api.do_search( body: body ) api_response.results.map { |r| r.properties['lastmodifieddate'] }
After some debugging in the gem code, I discovered that the sort param is being converted to a string before it is sent to HubSpot
My local fix was to update Hubspot::Crm::Contacts::PublicObjectSearchRequest#openapi_types to have
Hubspot::Crm::Contacts::PublicObjectSearchRequest#openapi_types
:'sorts' => :'Array<Object>'
instead of
:'sorts' => :'Array<String>'
The text was updated successfully, but these errors were encountered:
We've run into this too! Thanks @jamoore5. Hubspot any luck on a long term fix?
Sorry, something went wrong.
Thanks for sharing @jamoore5! I'm running into this issue as well. @alzheltkovskiy-hubspot any plans for a fix?
Hi everyone. We have identified this issue, and we are going to fix it as soon as we can.
alzheltkovskiy-hubspot
No branches or pull requests
Search API currently does not work with sort. The sort options in the request are ignored.
I found this when trying to search on contact with a sort by lastmodifieddate.
After some debugging in the gem code, I discovered that the sort param is being converted to a string before it is sent to HubSpot
My local fix was to update
Hubspot::Crm::Contacts::PublicObjectSearchRequest#openapi_types
to haveinstead of
The text was updated successfully, but these errors were encountered: