This will be especially important with Power BI's Azure Maps visualization which currently only accepts latitude and longitude coordinates for location. Without this being available in Business Central, we can't really make use of it, especially since sales data can end up being many records, dynamically asigning latitude and longitude at the time of data refresh in Power BI is a non-starter due to API call limits.

I don't know if Kevin's use of "function" here means just adding dummy decimal fields, or if it means the ability to geocode a complete address to latitude-longitude, but I am in favor of the latter.

I recognize that on different documents, but probably especially on Sales documents, there are Sell-to and there are Ship-to addresses, so lat.-long. probably need to be created for both. If only one is created, then in the Sales & Receivables Setup, one would have to identify one or the other for the geocoding.

Please reconsider!