Hello!
I am currently building an automation to migrate my analysis from my test account to a production account using Cloud Formation stacks and I am getting a weird error/bug when creating my quicksight dataset in the production (new) account. In my original test account dashboard, I have created a hierarchy with geospatial data for Sweden with Country Code ‘SE’. I used the cli describe dataset for my test account dataset and get the right country code, ‘SE’, in the description json file. When trying to recreate my dataset in the production (new) QuickSight account and build the same hierarchy I get the error:
[#/ColumnGroups/0/GeoSpatialColumnGroup/CountryCode: SE is not a valid enum value]
while when I try with country code for US it works fine. See picture bellow where in the left is the dataset description of my original account and on the right is the Cfn created dataset with countryCode ‘US’.
I have tried several country codes for other European countries and get the same error. I am wondering if that not recognising other countries codes than US is a bug of if that they are not supported for hierarchies yet. Is this a CloudFormation problem or a QuickSight problem?
Hello @anasia, I am actually unsure what level of country codes are accepted by the geospatial datatype in QuickSight. Often, in scenarios like this, I always recommend to be as specific as possible. Would you be able to convert the values to country name instead of country code? I know that functionality works well in these datatypes and you would run into less errors like this.
GeospatialColumnGroup has specific attributes in the template json file as in the documentation: GeoSpatialColumnGroup - Amazon QuickSight I cannot use country name. Also when I use Sweden for my hierarchy manually in QuickSight it works and it appears with countrycode: ‘SE’ in the json file. So there is no actual problem to use ‘SE’ in a hierarchy there. The problem is when I try programmatically to create an analysis with CloudFormation functions that it doesn’t accept ‘SE’ as country code.
Hello @anasia, I see, you enter the full country name and the QuickSight dataset returns with the country codes when the hierarchy has been established, but when starting with the country codes the hierarchy fails.
I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS
Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf.
Hello @anasia, since we have not heard back from you with any remaining questions, I will archive this topic. If you still require assistance with this issue after filing a support ticket, please post a new question in the community and link to this topic. That will ensure you are at the top of the priority list for a response from one of our QuickSight experts. Thank you!
