I want to set a default value in SPR which cannot be removed @dosu

[srijani-smsrc]

I want to set a default value in SPR which cannot be removed . not pre-filtered data. sei a value which has the be in the filter

@dosu

[dosubot[bot]]

You can make a filter in Superset always have a default value that cannot be removed by configuring the filter's settings. In the filter configuration (for native filters or Select filters), set the default value using the defaultDataMask property, and make the filter mandatory by setting enableEmptyFilter to false (or clearable to false in the config). This disables the option for users to clear the filter value in the UI, so the default value will always be present and cannot be removed see source see source.

In the UI, look for the "Filter value is required" option when configuring your filter. When enabled, users must select a value and cannot clear it. If you set a default value, it will always be present in the filter and cannot be removed see source.

This approach enforces the filter value in the UI, not just in the query logic. Let me know if you need a step-by-step guide for a specific filter type!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[dosubot[bot]]

Here are the steps:

1. In your dashboard or report, open the filter configuration (for the filter you want to make mandatory).
2. Set the default value you want in the "Default Value" field.
3. Enable the option labeled "Filter value is required" (this may appear as a toggle or checkbox). This ensures the filter cannot be cleared or left empty by users.
4. Save the filter configuration.

With these settings, the default value will always be present in the filter and users will not be able to remove it in the UI. This works for native filters and Select filters in Superset. The enforcement is handled in the UI, so the filter value is always required and cannot be cleared by users.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[srijani-smsrc]

what code level changes do i need to do

You can make a filter in Superset always have a default value that cannot be removed by configuring the filter's settings. In the filter configuration (for native filters or Select filters), set the default value using the defaultDataMask property, and make the filter mandatory by setting enableEmptyFilter to false (or clearable to false in the config). This disables the option for users to clear the filter value in the UI, so the default value will always be present and cannot be removed see source see source.

i want this in dashboard

@dosu

[dosubot[bot]]

To make a dashboard filter in Superset always have a default value that cannot be removed, you need to set the default value using the defaultDataMask property and make the filter mandatory by setting enableEmptyFilter to false (or clearable to false in the config). This is handled in the frontend code:

• For native filters, update the filter configuration in the dashboard's filter modal (see superset-frontend/src/dashboard/components/nativeFilters/FiltersConfigModal/FiltersConfigForm/FiltersConfigForm.tsx). Make sure the filter's config includes a valid defaultDataMask and that controlValues.enableEmptyFilter is set to false. This enforces the default value and prevents users from clearing it in the UI. The form will validate that a default value is present if the filter is required cite.

• For Select filters, set enableEmptyFilter: false in the filter's control panel config (see superset-frontend/src/filters/components/Select/controlPanel.ts). This is exposed as the "Filter value is required" checkbox in the UI. When this is set, users cannot clear the filter value cite.

• If you are migrating or programmatically creating dashboard filters, ensure the backend config (see superset/migrations/shared/native_filters.py) sets defaultDataMask and controlValues.enableEmptyFilter appropriately for each filter cite.

In summary: set the default value in defaultDataMask, and set enableEmptyFilter: false (or clearable: false) in the filter config. This will make the filter mandatory and prevent users from removing the default value in the dashboard.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[srijani-smsrc]

what is the difference between native filter and select filter @dosu

[dosubot[bot]]

A native filter in Superset is the dashboard-level filtering framework that lets you add and manage different types of filters—like select filters, range filters, and time filters—across your dashboard. A select filter is one specific type of native filter, implemented as a dropdown (using Ant Design components), where users can pick one or more values from a list. Select filters are managed within the native filter system and are not standalone; they're just one of several filter types you can configure in the dashboard filter modal. The select filter type has customizable options like default value, multi-select, and whether the filter can be cleared or must always have a value set (source).

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}