Note: Nintex Apps data centers are located in West US and Australia (AUS). In-region processing of Nintex Apps data is only available in these regions.
Geochart
Geocharts display data in a geographic region using a type of thematic mapping called a choropleth map. This means areas on the map are shaded in relation to the data being displayed on the map.
Before you chart, think about why to chart.
The Accepted Data Format for Geocharts
The default maps used with the Geochart component require data to be formatted according to ISO codes: ISO 3166-1 alpha-2 (for countries) and ISO 3166-2 (for the principal subdivisions such as states, parishes, provinces, regions, territories) of any country. For counties in the United States, Geocharts require the County FIPS Code.
Important: For some countries, the 2-digit ISO-3166 listed codes do not cover all the country subdivisions. For additional options, see the Highcharts documentation on custom GeoJSON mapping.
Using the Geochart Component
Geochart gives you the ability to display groupings of regional data. If your company does business across the globe, you might want to visualize where you have the highest number of customers. Geocharts can display the total number of customer accounts in each country based on the data in a field that records the account's country.
Note: The content below assumes you have a Nintex Apps page and at least one working model with fields selected.
Important: Be sure to include fields that reference country, state/province, and/or country data. If geographic fields are not included in the model, the geochart will be unable to display regional data.
AAfter you add a Geochart component to the canvas, set it up:
- In the General tab, choose a Title and connect the geochart to a model. Then choose the map group and map type.
- In the Series tab, select the data that will be displayed on the geochart. If you want to use Buckets to color-code different ranges, do that here as well.
Then customize its appearance:
- Use the Display tab to adjust the layout of the geochart.
- The Conditions tab lets you control when (or if) the geochart is displayed.
Print or download the chart
Print or download the runtime chart (in PNG, JPEG, PDF, or SVG formats) by selecting options from the hamburger menu at the top of the chart.
Note: SVG vector images scale to massive sizes—useful if you want to make a poster of the chart.
Properties
Component properties
- Title and Subtitle: The title header that sits at the top of the chart; the subtitle sits below it. Both are optional. Title content can be added by:
- Typing in plain text
- Adding a merge variable for a field within the chart's model using the field picker
- Using global merge variables plus text, for example, {{Model.labelPlural}} by Close Date, which displays at the model name plus the text "by Close Date." Learn about merge syntax and the global merge variables that can be used in a Chart title/subtitle.
- Model: The model the chart pulls data from.
- Map Group: The specific group that the displayed map belongs to. Choose from:
- Global
- Africa
- Asia
- Europe
- North America
- Oceania
- South America
- Canadian Provinces
- US States
- Map type: The individual map to be displayed. (This list changes, depending upon the map group selected.)
A series is the collection of data pulled from a model to be used in the chart. Click
next to Series List to add a series.Note: You can create more than one series for a geochart.
-
Model: The model that is the source of the data. If you have only one model on your page, that model will be the Chart default. However, if you have multiple models, then the Chart default is the model selected as the default model under the General tab. If you choose a model from the picklist, then another option will display in the Properties section for you:
-
Aggregate function: The chart data is aggregated according to the function you select from this picklist: Average, Sum, Max, Min, and Count. You can also choose not to aggregate the data with "None."
-
Data field: The field in the model that will supply the data.
Note: The available fields are determined by the fields added to the model.
-
Country field: The field in the model that connects the data with a country.
Note: Nintex Apps's default maps require 2-digit ISO 3166-1 country codes. Country information that does not match this format will not be displayed and cannot be used to associate the data with the appropriate country.
-
State field: The field in the model that connects the data with a state or province.
Note: Nintex Apps's default maps require 2-digit ISO 3166-2 state/country subdivision codes. State/country subdivision information that does not match this format will not be displayed, and cannot be used to associate the data with the appropriate state or province.
Important: If you are unable to set series properties, make sure you have the appropriate geographic fields added to the model.
Are you drilling down from country data to state/province data? You need to have data selected for this property, or you won't see any data when you drill down.
-
County field: The field in the model that connects the data with a county.
- Label: The name of the bucket to be displayed in the legend below the map. For example, if you are dividing lead opportunities amounts into buckets of $10,000 to $100,000, $100,001 to $500,00, and $500,001 to $1M, you might have three separate buckets labeled:
- Between 10K and 100K
- Between 100K and 500K
- Between 500K and 1M
- From: The starting numerical range for a bucket.
- To: The ending numerical range for a bucket.
- Color: The color used on the map for all regions within the select range. You can use any HTML compatible color.
The Display tab properties let you customize Geochart layout.
This section lets you control the location and layout of the chart's legend.
Note: Some layout options cannot be combined. For example, you cannot choose Horizontal Alignment/Center and Vertical Alignment/Middle; this would put the legend in the middle of the chart. If you choose conflicting options, the options will adjust to the last choice you made.
- Layout:
- Geochart default: Layout follows the default settings for the chart.
- Horizontal: The legend is listed horizontally (along the x axis), with items sitting side by side ( default ).
- Vertical: The legend is listed vertically (along the y axis), with items stacked.
- Off: No legend is displayed.
- Horizontal alignment
- Geochart default: Horizontal alignment follows the default settings for the chart.
- Center: The legend is displayed directly above or below the chart, depending on the vertical alignment (default).
- Left: The legend is displayed to the left of the chart.
- Right: The legend is displayed to the right of the chart.
- Vertical Alignment:
- Geochart default: Vertical alignment follows the default settings for the chart.
- Bottom: The legend is displayed at the bottom of the chart (default).
- Middle: The legend is displayed in the middle of the chart.
- Top: The legend is displayed at the top of the chart.
This section lets you format the map's labels.
- Format: The display of the map labels.
- Map default: The full name of the region.
- Data value: Displays the actual data based on the aggregate function selected.
- Off: Turns off data label display.
- Short name: The standard abbreviation for the region.
- Text color: The color of the label text. Use the color picker to select a color or enter the hexadecimal code.
- Bold labels: Make labels display as bold text.
-
Style variant: Style variants are created and set in the Design System Studio. Some components have pre-defined variants for a specific aspect of a component's style. Also, Nintex Apps builders can style and customize elements to create their own themes within the DSS. These themes will dynamically populate as selectable values in the Style Variant dropdown menu.
Note:To refresh available style variant options, click
Refresh style variants.This is useful for when changes to the design system (like style variants or variable options) have been made in another browser window or by another user.
-
Margin: Sets a component's margin (the space around it) relative to other components on the page.
- To set margins for all sides, click border-all All.
- To set margins for each side individually, click border-separate Separate.
Margin values can be set to any configured spacing variable for the page's design system. Margin cannot be set an arbitrary value; it must use a design system variable.
-
Unique ID (optional): Nintex Apps automatically generates an alphanumeric ID for the component; if preferred, give it a practical name.
-
Before-render snippet: Run the selected snippet immediately before the geochart is displayed; used to create advanced display options.
-
Exporting:
- Geochart default: Nintex Apps defaults to client-side processing of the geochart in preparation for export.
- Server-side: The geochart object is sent to Highchart's export server for processing, with results returned to the browser for export.
Note: This option is recommended if you are using JavaScript with the Highcharts API to extend the chart's capabilities. Client-side processing may not have all of the same options as the full Highcharts API used by server-side processing.
-
Client-side: The chart is prepared for export in the browser.
-
Disabled: No chart export options are presented to the end user.
Standard display logic options are available to display or hide the component or feature.
Troubleshooting
Not getting any data when using the Salesforce fields Account.BillingCountry and Account.BillingState for Series > Country Field and Series > State field?
If you've been using the ISO 3166 2-digit coding format, linked Country Field and/or State Field will display correctly in standard Geocharts.
However, if using a different standard (like IANA) or full-text strings for countries/states, then the Geochart will not display the expected results. Nintex Apps requires 2 digit ISO codes for the Country and State fields.
If State and Country Picklists are enabled in your org, then try using Account.BillingCountryCode and Account.BillingStateCode instead. (You may need to "turn on" State and Country picklists in Salesforce.)
Note: Additionally, if end users have not been consistent when entering geographic names, it may be necessary to scrub the data to identify and correct erroneous entries. To change geographical data, follow Salesforce's documentation on Implementing State and Country Picklists. If you follow this path, then you need to be aware that you cannot simply rollback from this implementation! We recommend that you carefully weigh the pros and cons of this type of implementation.