Known limitations of custom sets

This list provides known limitations of custom sets:

• Using a custom set as a column fails when the custom set was defined using a report containing custom groups.
• Custom sets cannot be used as a cluster group in the Visualizer Advanced Analytics feature.
• Custom sets cannot be used as filters on Designer reports.
• Using a custom set as a column fails when the custom set was defined using a report containing saved expressions in its filter.
• Custom set filters are not honored when exporting dashboards or dashlets, with deep linking, bookmarks or report notifications.
• Custom sets using average measures, which contain null values or are missing values, return unexpected results.
• Cannot use the benchmark Advanced Analytics function with reports using a custom set as a column.
• Cannot save a custom set in a private folder in Birst, if the report is in a private folder.
• Custom sets stop functioning if the report defining it is moved to a new report catalog folder.
• Cannot configure report level drilling using custom sets.
• Column selector does not support custom sets.
• Custom sets do not support drill across action on a dashboard.
• Custom sets cannot be applied as filters to a web page on a dashboard.
• Custom sets do not support conditional display.
• Custom sets cannot be used for filter groups or linked filters.
• Custom sets cannot be used as embedded filters on as dashboard.
• Deleting the report used to define a custom set renders the custom set unusable.
• If a dashboard prompt is created using a custom set and that custom set is later deleted, the dashboard prompt filter displays an error message each time it is rendered.
• Custom sets do not support visual filtering.