Lat/Long

Here is a full demo that uses the essential snippet of code I posted previously:


Client Side Snapshot Fields ~ Add New Location
https://haversineconsulting.quickbase.com/db/bnxecizd3?a=nwr

Pastie Database
https://haversineconsulting.quickbase.com/db/bgcwm2m4g?a=dr&rid=673

I would like to explain the name I choose for the application.The application takes a address entered as a single text field and uses Google's Geocoding service to look up the latitude and longitude. You can think of the geocoding process as a function or formula that takes the address value and calculates the latidude and longitude. However, this function is calculated client side (in the browser) once and only once at the time of interacting with the form. If by some other mechanism the address value was changed (say through grid edit) the geocoding process is not reevaluated. This may or may not be an issue depending on your expectations and workflow.

Notes:

1) The example demonstrates two different ways of invoking the geocoding - automatic and manual. However, if you examine the code you will see there is only one difference in the code, namely what event is being responded to (change versus event):

  $("#_fid_6").on("change", function() {...});
  $("a.QBU_Button").on("click", function(event) {...});

The form may appear to operate differently in the two cases but from a coding perspective the code is just responding to two different events (change and click). There are LOTS of event script can respond to so this is a very accommodating way of responding to user behavior

Wiki on HTML Events
https://en.wikipedia.org/wiki/DOM_events#HTML_events

2) To preserve the integrity of the geocoding against accidental change of the latitude and longitude, the latitude and longitude fields were made readonly at the HTML form level:

  $("#_fid_7").attr("readonly", true);
  $("#_fid_8").attr("readonly", true); 
  $("#_fid_10").attr("readonly", true);
  $("#_fid_11").attr("readonly", true);

3) The general technique used in this example can be extended to an enormous number of problems and follows a simple three step process:

    a) Grab some field values out of the form in response to some event
    b) Calculate some quantities using script
    c) Paste the calculated quantities into some other fields on the form

Step b) above may involve a complex calculation or algorithm that can be implemented in the formula language or it may involve calls to web services such as Google's geocoding.

4) The dbid and apptoken parameters are in the code as boiler plate although they are not used. The key parameter for Google's Geocoding service is left blank as it is not needed for low volume usage. For high volume usage you will have to supply your own key.

5) When I initially answered this question I was intentionally used a new scripting feature called async / await. These advanced techniques will make you script solutions easier and very short. However, I am limited in the time I have to write up elaborate explanations to every question. Over time you should become comfortable taking the "essential code" of a solution and supplying the necessary boilerplate to form a complete solution.