Hello gooddata team. In our dashboards we put filt...
# gooddata-cloud
m
Hello gooddata team. In our dashboards we put filters in
yaml
files like below:
Copy code
filters:
  date_day:
    type: date_filter
    from: 2023-09-01
    to: 2023-11-01
  9c35e19e6515403cac971f335576cb0b:
    type: attribute_filter
    using: label/OPERATION_RESULT
  54cf63d564744ea4aac874689db9cd92:
    type: attribute_filter
    using: label/AGG_SUBSCRIPTIONS.PROCESSING_TYPE
  c6947b6408724fdb993d9c8a3b674042:
    type: attribute_filter
    using: label/PROVIDER
when i try to hide filters from iframe query parameters like
?hidefilters=filter1,filter2
or when i check inside iframe i dont see filter IDs. So far we assume keys in
yaml
files would be filter id eg:
54cf63d564744ea4aac874689db9cd92
my question is do we need to pass extra
id
field in filters?
f
Hi Mustafa, thanks for the question. I’ve also been having trouble using the
hidefilters
HTML Parameter to hide dashboard filters in GD Cloud. Please give me some time to check internally on this feature and how to use it and I’ll be back with an update soon!
m
Hey Francisco, my problem is also that i cannot see those IDs inside iframe. My question again here is should we pass and id attribute in
yaml
ot it's parent attribute is enough?
f
Hi Mustafa; I checked, and the ID necessary for hiding the filter is not actually present in the yaml; The syntax used on the
hidefilters
parameter is
<dataset>.<object_id>
. e.g.:
customer.customer_country
. That information can usually be found in the Data Model, by checking each dataset’s details. So there is no need to pass the ID attribute on the yaml, as using the object’s name on the parameter will suffice.