2

The describe call is returning a bunch of fields on Account such as BillingLatitude, BillingLongitude, PhotoUrl, etc that result in the following error when included in SOQL queries:

No such column 'BillingLongitude' on entity 'Account'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.

The describe code is in PKG1 while the query is in PKG2. The 2 packages are installed in a client org and don't seem to mix well with each other. Any ideas why?

Improve this question

1 Answer 1

Reset to default
1

Check the API versions of each. If they don't match, you'll get errors on fields that don't exist in the corresponding API version. The most famous incident of this was the LastViewedDate Known Issue. Do not rely on dynamic SOQL strings working between API versions, or you'll be be in for some unpleasant surprises.

Improve this answer
1
  • I can tell right away that's the reason. Thank you.
    – Mossi
    Commented Apr 10, 2015 at 20:34

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .