This KPI still getting filter from Dashboard Date ...
# gooddata-cloud
k
This KPI still getting filter from Dashboard Date Range selector
SELECT  COUNT ({label/product_lookup.product_number} ) WITHOUT PF EXCEPT {label/admin_users.supplier_code},  {label/admin_users.adminuser_id}
k
Looking at your metric definition, the issue is that
WITHOUT PF EXCEPT
removes all parent filters except the ones you list. Since you're only excepting
supplier_code
and
adminuser_id
(attribute filters), the date filter from the dashboard is still being applied because it is not listed in the EXCEPT clause. To also ignore the dashboard date filter, you need to add the date label/attribute to your EXCEPT list. However, based on the MAQL documentation,
WITHOUT PF EXCEPT
will apply filters for any attribute you list and all attributes of coarser granularity in the hierarchy. [WITHOUT PF EXCEPT] If you want to exclude the date filter entirely, you should not include the date attribute in the EXCEPT clause. Your current metric already excludes it, which means the date filter should be ignored — unless the date filter is being applied through a different mechanism. If you want to completely ignore all parent filters (including the dashboard date filter), use
WITHOUT PARENT FILTER
with no exceptions:
Copy code
SELECT COUNT({label/product_lookup.product_number}) WITHOUT PARENT FILTER
[WITHOUT PARENT FILTER] If you want to keep only your two attribute filters and ignore the date filter, your current syntax should already do that — the date filter is not in the EXCEPT list, so it should be removed. If the date filter is still being applied, it may be coming from a metric-level WHERE clause or a visualization-level date filter rather than a parent filter. In that case,
WITHOUT PF
would not override it, as it only affects parent filters passed down from visualizations or dashboards. [Overriding Parent Filters] Could you check whether there is a date filter defined directly within the metric definition itself (a
WHERE
clause with a date condition)? That would explain why the date filtering persists despite using
WITHOUT PF EXCEPT
. 👍 0 button 👎 0 button â„šī¸ Tip: Mention @kapa.ai in the thread for follow-ups. 👀 Our Support team monitors all messages and will jump in if needed.