API - CrossDataset property on FilterGroup set to "SINGLE_DATASET"

Hello QuickSight Community,

I’ve come across an error while trying to download and re-upload a template from one account to another. After getting the template definition with describe_template_definition some of the FilterGroup items have the property CrossDataset: "SINGLE_DATASET" but contain visuals that don’t match the source dataset.

Exact error wording while trying to re-create the template using create_template:

FilterGroup has SINGLE_DATASET cross dataset type and contains a visual that does not match the source dataset

Example of FilterGroup failing:

{
    "FilterGroupId": "64f5e470-9bb3-46a1-a18e-3ac28d04a65f",
    "Filters": [
        {
            "CategoryFilter": {
                "FilterId": "5913d2e7-0145-4904-8767-4e3cf0e2ed6c",
                "Column": {
                    "DataSetIdentifier": "users",
                    "ColumnName": "group"
                },
                "Configuration": {
                    "CustomFilterConfiguration": {
                        "MatchOperator": "EQUALS",
                        "ParameterName": "group",
                        "NullOption": "NON_NULLS_ONLY"
                    }
                }
            }
        }
    ],
    "ScopeConfiguration": {
        "SelectedSheets": {
            "SheetVisualScopingConfigurations": [
                {
                    "SheetId": "febd3ef6-76da-43f5-876d-ed530ed7abd5",
                    "Scope": "ALL_VISUALS"
                }
            ]
        }
    },
    "Status": "ENABLED",
    "CrossDataset": "SINGLE_DATASET"
}

The workaround for this seems to be setting the CrossDataset: "ALL_DATASETS" property, but how does this affect the filter? Is this a bug or am I doing something wrong?

Thanks,
Adrian

Hi @Adrian_Vacaru, It will be best to raise a support ticket to debug this further. Here are the steps for opening a support ticket - Creating support cases and case management - AWS Support . 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.

Regards,
Karthik

1 Like