Apex Code Development You need to sign in to do that
Don't have an account?
rjk API2.0 query changes this weekend?
An application of ours broke because the query call is no longer working as expected. Specifically, the operators 'starts with' and 'contains' do not appear to be matching any values. When we do a 'starts with' query, we get nothing back, and when we do a negated 'starts with' query, we get everything back.
Has anyone else observed this behavior?
Has anyone else observed this behavior?
I also am seeing very strange issues using "contains", on XMLRPC v2.0 API.
Results from the report tab differ from the same query using the API and the operator "contains" , the results appear to be randomly omiting valid return values, the field I am filtering on is "Type".
In another case I see invalid values returned. Appears to be corrected by using "equals" , but much of my code uses 'contains'
can you post on the message board what your query is?
specifically, what entity are you querying, what fields are you querying for, and what is your filter criteria.
either the xml-rpc XML code is good, or just a brief description.
thanks!
don't have the xml handy, but the query is very simple
sfdc.query , table => opportunity , field => 'Opportunity Type', value => "CHM", operator => contains
gets lots more records today than last friday, many of which do not contain CHM