You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The SearchQueryBase interface defines entities as an array of strings:
entities?: string[];
But the Search API seems to expect this to be an escaped string as described here.
I'm very new to consuming the Dynamics API so may well be missing something but I could not get the search() method to not throw an error without using an escaped string for entities.
The text was updated successfully, but these errors were encountered:
hi @membla,
Thank you for submitting this issue.
I will need to make some changes in the library to make it work with the search api 2.0, currently the library does not support it.
It looks like it's going to take me some time to implement it. They have quite a bit of changes in Search API 2.0 and I need to figure out what is the best way to implement those changes and not to break the legacy implementation.
You could use corresponding actions for now: such as searchquery.
DynamicsWebApi version
For example: v2.1.4
Describe the bug
The SearchQueryBase interface defines entities as an array of strings:
entities?: string[];
But the Search API seems to expect this to be an escaped string as described here.
I'm very new to consuming the Dynamics API so may well be missing something but I could not get the
search()
method to not throw an error without using an escaped string for entities.The text was updated successfully, but these errors were encountered: