SData-2.0 icon indicating copy to clipboard operation
SData-2.0 copied to clipboard

commodities feed error is no data returned

Open asterix187 opened this issue 9 years ago • 1 comments

Hi, we have found a weird issue with Sage 50 sData when a where clause is used against the commodities sData feed and no data is returned. For example if the following url is used for a system with no updated commodities it errors : http://localhost:5493/sdata/accounts50/gcrm/-/commodities?select=%27uuid%27&precedence=0&where=updated%20gt%20@2016-08-08T09:00:00@

commodities not working

Whereas is the updated date is set back a month to before a commodities is changed then it doesnt error : http://localhost:5493/sdata/accounts50/gcrm/-/commodities?select=%27uuid%27&precedence=0&where=updated%20gt%20@2016-07-08T09:00:00@

commodities working

It also writes multiple entries to the windows event log indicating an issue with the sData service.

asterix187 avatar Aug 08 '16 09:08 asterix187

Looks like its not just commodities. It happens on a number of other feeds too. It's definitely incorrect behaviour - the Sdata specification states:

If the query executes successfully but does not select any resources, it MUST return a success code: 200 with an empty feed (or 304 if caching applies). This is not an error and it would be incorrect to return a 404 status in this case.

I'll raise it as a bug with the Accounts team

darroncockram avatar Aug 08 '16 10:08 darroncockram