Thank you for installing Daquota Connector!
This package contains two main elements:
Please follow these steps to complete the configuration:
This step is required to allow users to access the Daquota application without manual authorization.
In the Salesforce App Launcher, search for LocalFlow and open it.
This allows you to verify that the application is functional and correctly installed.
In the configuration tab of the application, as an administrator, you will have access to various configuration options to customize the map to your needs. All configurations will be instantly visible to all users once saved, so manage with care. By default, the map is configured to show some Salesforce standard objects on the map, but you can fully change it to fit your needs.
Note that you will not be able to save and share the map configuration with other users, unless you assign the Daquota permission set to them, as explained below.
You can make the Map tab accessible from other Salesforce applications:
You can add the LocalFlow Maps custom component to any Lightning record page. With the right configuration, it will show the record location on the map.
daquota_maps_recordRecord Map)500pxautonormalnormalfillHeight and Height: 100% in order to make the map fill the remaining space of the screen.
By default, once objects have been geocoded with an address field (for instance Account -> BillingAddress), the geolocation information is stored in the Latitude and Longitude fields of the address compound object, but they are not automatically reset when the user changes the address.
To do this, you can create a workflow rule on the address field (BillingAddress, ShippingAddress, etc.), that will reset the Latitude and Longitude fields when the address is changed.
Here is how to do this with a Salesforce Flow (no code):
BillingAddress, ShippingAddress, etc.)BillingAddress field):
BillingLatitude = nullBillingLongitude = nullLocalFlow will then detect null coordinates and recalculate them when the user asks for geocoding the objects.
By default, LocalFlow uses the address fields of the objects to geo-code them and display them on a map. However, you can also add geo-data to any object in order to attach any kind of geospatial data to your objects. This is useful for example to add geographic zones to standard objects such as Accounts, Contacts, etc. But it can also be used to add a list of places/locations to any object.
In order to use geo-data, you first need to create a geo-data feature layer in the LocalFlow application. This is done by clicking on the Features tab and then clicking on the Add feature layer button.
A feature layer is a list of standard GEOJSON features, which can be accessed with a URL. For instance, you can use some open data API to fetch states or regions for a country as GEOJSON and have them displayed on the map.
When creating a feature layer, you shall define the ID field, that will help the map to uniquely identify each feature. You should also define a label field that will be shown to the users. Any other feature field may be added to be shown in the map.
Once you have created a feature layer, you can add a custom GeoData field in your objects. This field will be used to store the IDs of the features of the feature layer. You can then use the GeoData field to display the features on the map, with 2 complementary ways:
GeoData field you want to visualize. This will show the features of the visible objects on the map.daquota_maps_record application, your users will be able to visualize and edit the GeoData attached to the record. You may have several geo-data fields for a given object. In that case, the application will be able to compare them visually.In the daquota_maps_record application, map state and config can be dynamically updated from Salesforce by using calculated fields. For example, if you have the MyAddress__c or MyGeoData__c fields in a Salesforce object, you can create the corresponding MyAddress_config__c or MyGeoData_config__c custom calculated fields in the same object (it works also with standard fields).
These fields will be automatically listened by the application and will make it refresh automatically in the two following scenarios:
At this point the only supported value for the calculated config fields is READONLY. When a config calculated field returns READONLY, it makes the map read-only and not editable for the corresponding field.
For services that require API keys, LocalFlow implements a secure Bring Your Own Key (BYOK) mechanism to manage API keys. Note that your API keys are stored encrypted in Salesforce and are not exposed to the end users.
In order to use the AI assistant to generate analysis and insights from your data, you need to provide a Gemini API key. Please follow these steps:
By default, LocalFlow comes with a free Leaflet (Open Street Map) configuration that does not require any API key. Also the default geo-coder is Nominatim, which is free too.
However, if you want to use Google Maps as the map provider or as the geo-coder, you need to provide a Google Maps API key. Please follow these steps:
Analyses may require access to external APIs for data enrichment or other purposes. Some common utility APIs are available by default. You can select more specific APIs in the configuration (DataSource tabs). Please contact us if you need to add a public or private data source.
If you encounter any issues or need additional support, please consult our documentation or contact our support team at support@localflow.fr.