Limitations Changed for Geolocation Fields (Generally Available)

Geolocation fields, formerly available only as a beta release, are now generally available. Now you can get the most out of geolocation thanks to fewer limitations and increased functionality, including improvements in Visual Workflow, workflow updates and approvals, Apex, search tools, and more.
Available in: All Editions

Spring ’15 includes the following changes to geolocation field limitations.
  • Geolocation fields are available in Visual Workflow and in formula-based criteria in workflow rules and approval processes, but cannot be used in filter-based criteria in workflow rules and approval processes.
  • Geolocation fields can be searched in SOQL and SOSL.
  • DISTANCE formulas are supported in:
    • Entry criteria for workflow rules and approval processes
    • Field update actions in workflow rules and approval processes
    • Custom validation rules
  • The only formula functions that you can use with compound fields are ISBLANK, ISCHANGED, and ISNULL. You can’t use BLANKVALUE, CASE, NULLVALUE, PRIORVALUE, or the equality and comparison operators with compound fields. The equality and comparison operators include = and == (equal), <> and != (not equal), < (less than), > (greater than), <= (less than or equal), >= (greater than or equal), && (AND), and || (OR).
  • Geolocation fields are now queryable in Apex. However, their locations are editable in Apex only as components of the compound field. Read and set geolocation field components by appending “__latitude__s” or “__longitude__s” to the field name, instead of the usual “__c.” For example:
    Double theLatitude = myObject__c.aLocation__latitude__s; 
    myObject__c.aLocation__longitude__s = theLongitude;

For a full list of limitations, see Geolocation Custom Field Overview.