Updates w.r.t. Address and Location

• Re-adjusting the Address field
  
• Deprecating Address Line 1 and Address Line 2 subfields from the Added Location and Modified Location system fields
  
• Introducing display options for location data in reports
  

Re-adjusting the Address field

• Geo coordinates are not captured for addresses that users type in the field.
  
• Geo coordinates that are returned by our map service, lack the required accuracy.
  

• Capture geo coordinates - This will use the physical address typed by your user and immediately fetch its geo coordinates using the map service. This property will be auto-enabled for all address fields. Geo coordinates of existing addresses, if not already captured, will be captured when users edit those records.
  

• Adjust location on map - This will display the address's geo coordinates and allow users to adjust its location in a map. Adjusting the location will not affect the physical address data that the user entered — it will only update the data in the latitude and longitude subfields.
  

Deprecating Address Line 1 and Address Line 2 subfields from the Added Location and Modified Location system fields

Tackling the lack of required accuracy w.r.t. reverse geocoding address data, we're deprecating the Address Line 1 and Address Line 2 subfields from the Added Location and Modified Location system fields .

This change will not affect the existing data and workflows that refer to said subfields. However, Address Line 1 and Address Line 2 data (in the location fields) will not be captured after this update.

Introducing display options for location data in reports

In the report layout, the Display Option property will be introduced for the address, added location, and modified location fields. This'll enable you to define if the data in these fields is to be displayed as a Physical address or as Geo coordinates . 

When you choose to display geo coordinates, you'll get to select the format using which the coordinates are to be displayed: either the Decimal Notation or the Degree-Minute-Second DMS Notation .

Panel builder and Gauges in Pages

Panel builder

Gauge

Kanban Report customizations

• Ability to hide the EMPTY column, or show it with a custom label
  

• Ability to hide or show the Deleted Value Column : Imagine a kanban report based on a dropdown field, and that you delete one of its choices that's selected in records. Once a choice is deleted, the corresponding column in the kanban report is also deleted. To ensure that such records remain visible in the report, we're introducing the Deleted Value Column. This column will also show the records that contain "other" values that users enter in the dropdown field.
  

• Ability to filter the columns that the kanban report is to display. This can be done as follows:
  
• When the kanban report is based on a lookup field, you'll be able to use the lookup's filter criteria
  
• You'll be able to specify a custom criteria using the criteria builder
  
• You'll be able to manually select the values that are to be shown as columns
  

Ability to search and sort records using the subfields of Name and Address fields

• The address field is made of address line 1, address line 2, city/district, state/province, postal code, and country subfields. This order will be considered while applying sorting. For example, when you sort using the  City/District subfield, the records will first be sorted using city/district data, then the state/province, then the postal code, and then the country data.
  

• The name field is made of prefix, first name, last name, and suffix subfields. This order, and the name field's Display Option property in that report, are considered while applying sorting. For example:
  

• When you select the First Name subfield to sort with, records will first be sorted using the first name data, then the last name, and then the suffix data.
  

• When the name field's Display Option property in that report's layout is set as Last Name first and you select the Last Name subfield to sort with, records will first be sorted using the last name data, then the first name data, and then the suffix data.
  

Currency field formatting

• Default
  
• 1,234,567.89 
  
• 12,34,567.89 
  
• 1 234 567,89 
  
• 1.234.567,89
  
• 1'234'567.89