Error thrown when corrupted native dashboard filter metadata referencing obsolete filter ID

[john-bodley]

The dashboard native filters throws an unexpected error due to corrupted dashboard metadata.

How to reproduce the bug

Currently we're uncertain how the metadata becomes corrupted, though it likely occurs when people delete a filter. The issue surfaces when a the cascadeParentIds array references an ID which is not associated with any filters, e.g.

{
    "native_filter_configuration": [
        {
            "id": "NATIVE_FILTER-4vk933fy2",
            "cascadeParentIds": [
                "NATIVE_FILTER-Fvk_h6yN"
             ],
             ...
        }
    ]  
}

Removing the hanging NATIVE_FILTER-Fvk_h6yN reference remedies the issue.

Expected results

The cascadeParentIds array should only contain the IDs of currently defined filters.

Actual results

An error is thrown.

Screenshots

Environment

(please complete the following information):

• browser type and version: Chrome 114.0.5735.198
• superset version: master
• python version: 3.9
• node.js version: 16
• any feature flags active:

Checklist

Make sure to follow these steps before submitting your issue - thank you!

• I have checked the superset logs for python stacktraces and included it here as text if there are any.
• I have reproduced the issue with at least the latest released version of superset.
• I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Add any other context about the problem here.

[michael-s-molina]

Closed by #24749