Forum Discussion
Solved
SharePoint Search API response schema changes
Hi, I've started noticing issues with search REST api results lately where there are some new properties returned in the schema and some null values. Ex: _api/search/query?querytext='Filename:B31...
- My take is this. You should only expect properties you ask for. These may or may not have values depending on the property. As such, you should not have a rigid schema to validate returned data.
DocumentSignature/CollapseStatus are by no means new ones. As for other props these can and will change as we make changes. And the schema contract is a weak one and you should only count on any public documented properties or those you have created yourself.
Hope this makes sense 🙂
I am facing the very same issue that results in failure of Json parsing. Is there any update from microsoft on this issue.