This project has moved and is read-only. For the latest updates, please go here.

Create a New Map

Once you have installed the Chart Map solution, you will find a new entity in the Settings area called Chart Map Config. For a new installation, you should see 4 records that were automatically created as part of the installation. These can be modified or removed if desired. I recommend using these records as references for creating your own map configurations.

Note: Each Map Config record relates to exactly one Chart. When you create the new configuration, a new Chart will be generated, and when you delete a configuration the associated Chart will also be deleted.

Start by clicking on the New button, and fill in the fields appropriately.

General Fields

  • Chart Name - The name of the chart that will appear to the users. This name should be unique.
  • Map Type - Choose between Standard or Heat Map.
  • Chart Description - A long description of the chart. This will not be shown to users.
  • Entity Type - The logical name of the entity which the chart applies to.
  • Language - The display language and region to be used on the map.
  • Show All Records - (3.0 Only) This setting controls whether all records in the view will be displayed on the map at once, or if the map will be limited to records in the current page of the view. Note that even if this is set to Yes, there is still a hard limit of 5000 records per map. When this setting is on, it is recommended to also enable Location Caching.
  • Enable Location Caching - Enabling this setting causes the Latitude and Longitude that are discovered for each record to be saved on the record, so that they do not need to be geocoded each time the map is opened. If this is enabled, then the Latitude and Longitude address fields become mandatory.
  • Default Latitude - Default Longitude - Default Zoom - These settings control the default center location and zoom level before any points are rendered. After points are rendered the map will autoscroll and zoom for best fit of all points. However, these settings still play an important role, as they can affect the quality of the search results. An accurate address match is more likely, if it is located within the default map area.

Important Note: In order for caching to work, the end users must have write permission to the entities being displayed in the map. If they don't have this permission, there will not be any errors, the caching will simply not happen.

Note: The Chart Name, Chart Description, and Entity Type can only be set when the chart is created. If these are set incorrectly, you will need to delete the configuration and recreate it with the correct settings. All other fields can be modified at any time.

Address Fields

All address fields must match the logical name of a field on the entity entered in the Entity Type field above.
It is possible to use address values from parent records. This is entered in the following format: "lookupfieldname.parentrecordfieldname". For example: "parentaccountid.address1_line1"
All fields used must be a Text field, OptionSet, or Lookup field. If a text field is entered, then its value is taken directly. If an OptionSet or Lookup are used, then the text value is taken as the value. This is useful if your CRM is using a dropdown field for Country or State. Or a lookup for things such as PostalCode or City.
  • Name Field - The name or title field of the entity. This will be displayed as the header link in the infoboxes. It is not used as part of the location search.
  • Address Field - Typically corresponds to the address1_line1 field for most entities
  • All other address fields - Their purpose should be self-descriptive

Note: When the map is loaded by the user, each record that contains a Latitude and Longitude value will use those saved values for the pin placement. Any record that does not contain those values, the map will perform a lookup using the Bing Map API to find the coordinates. Also, if GeoLocation Caching is enabled, then the discovered coordinates will be saved to the Latitude and Longitude attributes. It will not overwrite existing values, it will only perform an update if those values are blank.

Pin Settings (applies to Standard Map Type only)

  • Enable Clustering - With this option enabled, this will cause pins that are tightly grouped together to be merged into a single pin. The clustered pin will display the number of records that are clustered into it.
  • Cluster Radius - This setting is only applicable if Clustering is enabled. The default value is 30. This represents the distance in pixels that two pins must be from each other before they become clustered.
  • Pin Size - This can be set to Standard or Micro. It only affects the display size of the pins.
  • Cluster Title - This is the actual title that will be displayed in the Infobox header for all pin clusters on this map.

Heat Map Settings (applies to Heap Map Type only)

  • Heat Intensity Based On - This can be set to "Record Count" or "Numeric Field Value". This controls how the heat intensity is calculated. Record Count will increase intensity based on the number of records in the same location. Numeric Field Value will increase intensity based on cumulative value of any numeric type field of all records in the same location.
  • Intensity - This is a fixed intensity value between 0.0 and 1.0. This value is only applicable if "Record Count" is selected above.
  • Numeric Field - This is the logical name of any Whole Number, Decimal, Float, or Money field on the selected entity. The value of this field will be used to calculate the intensity of each heat spot. This field is only applicable if "Numeric Field Value" is selected above.
  • Weight Range - Only applicable when "Numeric Field Value" is selected. This can be set to either "Fixed" or "Calculated". A fixed range will cause the heat intensity to represent specific numeric values, regardless of the data being displayed in the view. Selecting "Calculated" will cause the range to be automatically calculated based on the records currently in the view. Selecting Fixed is useful to be able to compare multiple datasets on an even basis, or to be able to see trends of the same dataset over time. Selecting Calculated is useful if the values can vary greatly between datasets, and there is no need to directly compare information between datasets.
  • Weight Calculation - This can be set to "Full Range" or "Standard Deviation". This field only applies if "Calculated" is selected above. Full Range will set the intensity range based on the full set of values in the view. The disadvantage to selecting Full Range is if there are some extremely high or extremely low outlier values, that will cause a lack of granularity in the heat spots. Eg: If there are 100 values that range from 100 to 1000, and one value that is over 1,000,000, the heat map will only display a single red dot and the 100 smaller values will lack enough intensity to be displayed. Selecting "Standard Deviation" will limit the affect of such outlier values. In the previous example the single value of 1,000,000 would be an outlier. The calculated range would be from 100 to 1000, and the single 1,000,000 value would be assigned the maximum intensity of 1000. This would allow full granularity in the display of the "standard" values.
  • # Deviations - This is the number of Standard Deviations that a value must be away from the standard in order to not be included in the range calculation.
  • Minimum Value - The minimum value for Fixed Range intensity. This should be set to the minimum expected value in the data that will be mapped. Alternatively it can be set to the minimum value that is desired to be displayed. Any records with a value below the minimum fixed value, will not be displayed on the map. Only applicable if Weight Range is set to Fixed.
  • Maximum Value - The maximum value for Fixed Range intensity. Any records with a value greater than this maximum value, will be assigned intensity based on this value instead of their actual value. Only applicable if Weight Range is set to Fixed.
  • Radius - The radius of each heat spot, in either pixels or meters.
  • Radius Units - This can be set to Pixels, or Meters. The primary difference is that when Pixels are selected, the heat spot size will NOT scale with the zoom level of the map. Selecting meters will cause the heat spot size to scale with the zoom level. Selecting Meters can cause the heat spots to become too small to see when the map is zoomed out too far. Selecting Pixels can cause the heat spots to become too large when zoomed in too far.
  • Colour Stop # - These values represent the colour that will represent the intensity of each heat spot, with 1 being the lowest. It is possible to add custom colours to the dropdown.

Last edited Mar 10, 2015 at 5:17 PM by wedge905, version 14