Financial roll over , table vs map

[Qlik1_User1]

Hi all

Please help

I am showing finical roll over data in table and map.

The data for France is coming in table but not in map same dim and measure.

Data

Fact:

client,Pol, cov, year, loc, yemo

A,1,10, 2022, Fra, 202201

A,2,20, 2022, Fra, 202201

A,3,30, 2023, Fra, 202301

A,4,40, 2023, Fra, 202301

B,30,300, 2023, Fra, 202301

B,40,400, 2023, Fra, 202301

User selected 

Client A, year = 2022,

Values in variable 

Vfrom = 202212

Vto = 202309

Map details

Dim - loc

Dim under location section - loc

Measure Sum({<year=, yemo={">=202212<=202309"}>}prem)

But it's not showing France in map..even though year is ignored and France yemo value is in range

[Greg_Taffer]

The issue where data appears in a Qlik Sense table but not on a map, despite using the same dimension and measure, is almost always due to geocoding failure—Qlik cannot map the spelling of "France" or its sub-regions to its internal geospatial database. 

Here are the specific reasons and solutions for why your France data is missing in the map:
 

1. Ambiguous Location Name (Spelling/Language)

Qlik maps require exact matches in its geocoding database. 

• The Problem: "France" might be spelled differently, have unexpected trailing spaces, or use special characters that Qlik does not automatically associate with the country shape.
• Solution: Create a calculated field in your load script or front-end dimension to ensure formatting: Capitalize(Trim(CountryField)). 

2. Location Not Identified as Geo Data 

Even if the data exists in the table, Qlik must recognize the field as a geographical field (Type: Country, City, etc.). 

• The Problem: The field is treated as a generic string.
• Solution: In the Data Manager, edit the field mapping and change the field type to "Geography" and set it to "Country" or "Administrative Area". 

3. Missing or Incorrect Sub-region Levels (Departments)

If you are displaying regional data (not just the whole country):

• The Problem: French Department names (e.g., "Côte d'Or") often fail because of accents or abbreviations (like Dept 21 vs Côte d'Or).
• Solution: Concatenate the country code to ensure it's not looking for that region in another country. Example: RegionName & ', ' & 'FR'. 

4. Incorrect Map Layer Configuration

• The Problem: You might be using an Area Layer, but the data is better suited for a Point Layer, or the Country level is incorrect.
• Solution:
  • Set the Map Layer location type to Country and Country Code to FR.
  • Alternatively, go to the layer properties, ensure Location Fields is set correctly, and define the Country field specifically to FR to narrow the search. 

5. Data Model Disconnection (Most Likely)

• The Problem: The table showing the data might be in a different table than the one containing the geo-coordinates/names, and they are not properly linked in the data model.
• Solution: Review the Data Model Viewer. Ensure the field used in the map layer is part of the same data island or properly linked via a key to the data containing the financial measures. 

Quick Fix Steps

1. Check Spelling: Ensure it is "France" and not "FR" or "france" (if that's what Qlik expects).
2. Add Country Code: Create a new field GeoCountry = 'France' to ensure standard spelling.
3. Use Location Field: In your map layer, explicitly select the field Country and set "Scope" to "France".
4. Check Data Load Editor: Use TAG FIELD [YourField] WITH $country; to explicitly tell Qlik what the field is. 

[rodrigo_martins]

I tried your sample and France shows correctly on the map:

A couple of things to check:

• Your expression uses prem, but your sample data doesn’t include it. I used cov to test - make sure the field exists.
• The set analysis looks fine, but try removing the yemo section from the Set Analysis just to check. Also, check for nulls or data type inconsistencies in yemo.
• Is the location scope set to auto on the map? (It worked in my test.)

With the sample provided, the issue is not reproducible, so there is likely something different in the actual data model or field formatting.