Sage 100

v52 Standard - We're trying to use the SData Provider for Sage 100 and have a problem with query filtering. SData has kind of it's own query language.. a few sample queries may look like: BalanceForward gt 0 (in SQL it would be, BalanceForward > 0) CustomerName eq ""ABC"" (in SQL, CustomerName = 'ABC') These work fine, the SData provider parses the query and passes it through to the ProvideX/ODBC layer as something it understands and it works just fine.. However my problem is I can't filter on Date fields.. I should be able to do a search like: DateUpdated gt @2008-05-19@ But I get the error message ""Expected lexical element not found: )"" I know ProvideX expects dates in a certain format and I've tried every format combination I can think of with no luck.. DateUpdated gt {d'2006-04-07'} ""Unexpected char: '{'"" DateUpdated gt {d@2006-04-07@} ""Unexpected char: '{'"" DateUpdated gt @{d'2006-04-07'}@ - ""String was not recognized as a valid DateTime"" DateUpdated gt @'2008-05-19'@ - ""String was not recognized as a valid DateTime"" So this is my problem.. It seems the Sage 100 SData implementation doesn't know how to properly parse Date filters for ProvideX, either that or I'm using the wrong format. Sdata's query language is defined here if that's of any help: http://sage.github.io/SData-2.0/pages/core/0211/

I KNOW NOTHING - but have you tried without the dashes, like you have to do for VI? YYYYDDMM

I also know nothing, but their example on this page (http://sage.github.io/SData-2.0/pages/core/0212/) shows what you already have: where=date ge @2008-01-01@. Does it want parentheses around the filter?

Tried everything and nothing works. Thanks for your suggestions. Now trying to get someone at Sage to help. Oh boy. Something seemingly simple is turning into a major project.

Update. Sage 100 is not supported with SData 2.0. Sage 100 is only supported with SData 1.0. However, the date query feature is only supported in SData 2.0. So.... SData web service available for Sage 100 ACCOUNTING software doesn't have a date query feature. Isn't that special. No wonder everyone is getting fired.

If only that was the reason everyone was getting fired, instead of giving Kelly a shorter plane ride...

what are you trying to accomplish @DougHiggs there may be another way to handle it since sData is a dud.

We are creating a custom integration between Sage 100 and Sugar CRM.

Certipro has a JSON web service (called ELink). This may be an alternative.

Yes I would guess there are a couple of solutions already for Sage 100 and Sugar.