Method Community

I am using PHP CURL to request data using MethodAPISelect_XMLV2.  I am making successful requests until I try using LIKE in the where clause.  For example, if I use

          strWhereClause=RefNumber = '123'

data is retrieved.

If, however, I use

          strWhereClause=RefNumber like '%123%'

no data is retrieved (and no errors either).

Is it possible to make MethodAPISelect_XMLV2 calls using LIKE in the where clause?  If so, why is the syntax I am using not working?

I think I have answered my own question.  When I hard code '%' into the where clause, I get no data.  If I include '%' as part of the search parameter typed into the form, I get data.

I am not sure why there is a difference in the results, but at least I can move forward.

Now I realize what is happening.  The '%' followed by numbers is being intrepreted as a URL encoded entity.  I need to URL encode the '%' with '%25'.  Now I am retreiving what I expected.

Good show.  And good clarification, Paul.  When using MethodAPI via POST, I pass the values on the right sides of '=' signs through the PHP function urlencode().

Slightly off-topic, don't forget to prefix quotes with slashes if comparing arbitrary strings.  I'm guessing that applies to .NET or any language.

Thanks viret576 for sharing.

To anyone else reading this, it does depend on what technology you are using whether you need to URL encode or not.  For example, if you are using .NET and adding a web reference, the URL encoding is automatically handled for you.   But if you are doing a raw HTTP Post (which the Method API supports), then you'd of course need to do URL encoding.

Paul