Daquota Connector — Post Installation Guide

Thank you for installing Daquota Connector!

This package contains two main elements:

  1. Daquota Connector is a connected app that allows any Daquota application to be integrated with Salesforce as Canvas Apps using the Salesforce API.
  2. LocalFlow Maps is an application built with Daquata, that is embedded in this package as a proof of concept of the Daquota plaform. It will by default install a free version. Please contact us for the full version at support@localflow.fr.

Please follow these steps to complete the configuration:

1. Configure the Connected App "Daquota"

This step is required to allow users to access the Daquota application without manual authorization.

2. Open the LocalFlow Maps Demo Application

In the Salesforce App Launcher, search for LocalFlow Maps and open it.

This allows you to verify that the application is functional and correctly installed.

If you see the map in your LocalFlow Maps application, CONGRATULATIONS!!, you can now start using it. If not, please follow the remaining instructions or contact us for assistance at support@localflow.fr. Please read the remainder of this configuration guide for other configurations.
With this configuration, you will have access to the default map behaviour. However, in order to be able to modify the map behaviour and access advanced features such as zoning, you will need to assign you users the Daquota permission set. Please read the remainder of this configuration guide for additional configurations.

Additional configurations

Setup layers, conditional formatting and so on for your users

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.

Assign the Daquota permission set to users

This configuration is mandatory even for admins, in order to be able to modify, save, and share the map configuration with other users.
As an admin, try to modify and save the map configuration (configuration menu in LocalFlow). If you manage to do so, CONGRATULATIONS!!, your permission set configuration is working, and you shall do the same for other users who need to access the map with the modified configuration.

Add the LocalFlow Maps Tab to Other Applications (optional)

You can make the LocalFlow Maps tab accessible from other Salesforce applications:

Add the LocalFlow Maps Component to Record Pages (recommended)

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.

Steps:

Recommended Configuration (to show the record location on the map):

Tip: For typical use cases, it is convenient to create a new tab in your record layout and put the LocalFlow Maps component in it. In that case, choose Layout: fillHeight and Height: 100% in order to make the map fill the remaining space of the screen.

Reset automatically the geocoding information when an address changes (recommended)

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):

LocalFlow Map will then detect null coordinates and recalculate them when the user asks for geocoding the objects.

Add geo-data to objects (only when the geodata option is avalaible)

By default, LocalFlow Maps uses the address fields of the objects 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 geo-spacial data to your objects. This is useful for example to add geographic zones to standard objects such as Accounts, Contacts, etc. But is 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 Maps 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:

Dynamically update map state and config (optional)

In the daquota_maps_record application, maps 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.

Need Help?

If you encounter any issues or need additional support, please consult our documentation or contact our support team.