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 Maps 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 LocalFlow Maps 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_record
Record Map
)500px
auto
normal
normal
fillHeight
and Height: 100% in order to make the map fill the remaining space of the screen.
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:
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, 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.
If you encounter any issues or need additional support, please consult our documentation or contact our support team.