Dashboard Creation from template API: Geographic mismatch

Question & Answer
,
1

Hi I’m using Python API operations to prove out Dashboard operations. I am doing the following simple test.

  1. Turn dashboard to template from dataset x
  2. recreate dashboard from template from dataset x

Point being this should be a straight forward recreation to say ok, I can make a dashboard from a template. However, upon creation I’m getting the following error:
‘COLUMN_GEOGRAPHIC_ROLE_MISMATCH’
When creating the dashboard from template, it is forcing any of my columns in the dataset with any geographic mention of say city, postcode, country to explicitly define that in the column.
The odd part is, I’m creating the column definition for the template from describe dataset x. This should be a 1:1 match right?

Is this a bug within Quicksight that forces geographic definitions? Looking for an explanation around this as we build and entire operations around template promotions and creations.

2

The error message you’re encountering, ‘COLUMN_GEOGRAPHIC_ROLE_MISMATCH’, suggests that there is a mismatch between the geographic role assigned to a column in the template and the corresponding column in the dataset. Quicksight requires explicit definition of geographic roles for certain columns to ensure proper visualization and mapping of geographic data.

When creating a dashboard from a template, Quicksight checks the column definitions in the template against the dataset columns. If a column in the dataset has a geographic mention (e.g., city, postcode, country), it should have an explicit geographic role defined in the template.

Here are a few things you can check to resolve the issue:

  1. Verify the column definitions in your template: Double-check that the column definitions in your template explicitly define the geographic roles for the relevant columns. Ensure that the geographic roles match the column types and contain the required geographic information.

  2. Check the dataset column definitions: Examine the column definitions of the dataset you’re using. Make sure that any columns with geographic mentions have the appropriate geographic roles assigned to them.

  3. Review the column properties: Ensure that the properties of the columns in both the template and dataset are consistent. Check for any discrepancies in data types, formats, or properties that could lead to the mismatch.

  4. Test with a smaller dataset: If possible, try creating a new template and dashboard with a smaller dataset that exhibits the issue. This can help isolate the problem and identify specific columns or configurations causing the error.

If you’ve verified that the column definitions in both the template and dataset are aligned correctly, and the error persists, it might be worth reaching out to the Quicksight support team for further assistance. They can provide more specific insights based on your dataset and template configurations.

1 Like