Geomap not working as expected | Troubleshooting guideIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Geomap is not working properly or as expected. Map is not showing or taking forever to loadDrilling down on the geomap is breaking itGeomap doesn't highlight country or state on the mapGeomap showing an error that data can't be displayed on the map Facts<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } General Overview of the Mapping Tables: SYS_REPORT_MAP - the actual map, the JSON that plots out the map, holds the hc-keys, etc.SYS_REPORT_MAP_TYPE - sets up the levels of maps, 1 = World, 2 = Country, etcSYS_REPORT_MAP_SOURCE - A set of cascading association that defines how to group and drill down into a mapSYS_REPORT_MAP_CONDITION - conditional filtering of values to show on a mapSYS_REPORT_MAP_SOURCE_MAPPINGS - mapping values from the map_source to the hc-key value in the map JSONSYS_REPORT_MAP_SOURCE_MAPPING - Grouping of the different mapping levelsVIZ_MAP_SOURCE - Same as SYS_REPORT_MAP_SOURCE for the new Data Visualization / Platform Analytics product. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Any Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Troubleshooting steps: 1. Check map source tables for data sourcing issues, SYS_REPORT_MAP_SOURCE table (Old Reporting) or the VIZ_MAP_SOURCE table (New Data Visualization). This tells the geomap how to initially display, group, and drill down into the maps. The Table value should be the base table you want to map on, for example sys_user.The Field value details how the map groups the records and which value is used at every level on the map. The first record is a general association, this is normally a reference to 'location' which is the cmn_location table. The new VIS_MAP_SOURCE table has and empty field and uses "Location" as the Table because so many things were already referencing it like the example at the bottom of this section. The rest of the records NEED to map to a field that returns a String value and not a Reference field to another table. If it is a Reference you need to drill down and provide a field with a String value. ( location.country.name = "Canada" ) The Field values should "step down" with each Level, this tells the map how to drill down. 1 = Country, 2 = State, 3 = City.Here is an example from the OOTB source records for sys_user in the SYS_REPORT_MAP_SOURCE table NameTableFieldLevelParentUse These MappingsHow to use dataUser by locationuser [sys_user]location(empty)(empty)(empty) User by location (level 1)user [sys_user]location.countryLevel 1User by locationCountry mappingsUse mappingUser by location (level 2)user [sys_user]location.stateLevel 2User by location (level 1)Region and State mappingsUse mappingUser by location (level 3)user [sys_user]location.cityLevel 3User by location (level 2)(empty)Use Latitude and Longitude 2. Check the value coming from the column selected in Step 1 matches to the Key value of a record in the SYS_REPORT_MAP_SOURCE_MAPPINGS table. 3. Check the Value column of SYS_REPORT_MAP_SOURCE_MAPPINGS connects with the hc-key value found in the JSON of the actual map in SYS_REPORT_MAP. Example of a record for Step 2 & 3: KeyValueMapMap Source MappingFLus-flUnited States of AmericaRegion and state mappings 4. Check that you have data in all your records for the columns specified in Step 1. This step usually has the most work to do and you want to make sure that your source and mappings are setup correctly first. You will probably need to standardized values in the fields from Step 1. State = ('Florida', 'florida', 'fl', 'FL', etc) --- should be standardized to ---> 'Florida' Example Flow: You are mapping the sys_user table on the map of the United States of America. 1. Your map source table tells the report to get the value from the location.state field, so for each sys_user record it will walk through the location reference to get the state field. When it does, it finds the field has the 2 character name of the state (FL). 2. The mappings table needs to have a record that connects the the Key (FL) to the Value (us-fl) 3. The value from the mappings table (us-fl) is the hc-key found in the JSON that makes up the United States Map. It will highlight that whole area and display a total count in the center. 4. If another sys_user record's location had 'Florida' in the State field instead of 'FL', then the Mapping table would need to have a mappings record for BOTH 'FL' and 'Florida', OR the data would need to be standardized to be consistent.