If you are using the latest geolocation feature in your existing salesforce apex classes & soql queries, then chances are you might hit this error "No such column GeoLocation__c. 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 name" as we did in our org..
there is a known issue which the salesforce team is reviewing currently
https://success.salesforce.com/issues_view?id=a1p30000000SpfnAAC
the workaround is to increase the version number of your apex class to something greater than 26 and try.. please note in certain cases, we might need to increase the version number of the class that has the geolocation field / soql and also the version number of the classes being referred inside the class with the geolocation / soql..
good luck.
there is a known issue which the salesforce team is reviewing currently
https://success.salesforce.com/issues_view?id=a1p30000000SpfnAAC
the workaround is to increase the version number of your apex class to something greater than 26 and try.. please note in certain cases, we might need to increase the version number of the class that has the geolocation field / soql and also the version number of the classes being referred inside the class with the geolocation / soql..
good luck.
No comments:
Post a Comment