We were trying to make sure that filters for each child workspace filtered by what was available for that child. For example in the photo we added the filter. However, when we add these filters on the child it shows all possibilities and not just those ones for the child. Any advice? In the photo below, the workspace should just have Chat, Email, Store, Voice, SMS, No Value. None of the others

Hi Doug, thank you for ask this. First to all I would like to be sure you followed this Documentation about how to set the Workspace Data Filter (WDF)? There you can follow the instruction using the UI or API. If you need to set up many workspaces, I would recommend follow the UI instructions. Please, note that after create the WDF you still need to explicitly assign this filter to a specific dataset. You have to 'enable' it on the Parent workspace.

Yew we followed the instructions. They do Work, they just do not work for Dashboard filters ( Like the ones I showed in the picture.). They do work everywhere else. @Mauricio Cabezas

Hi Doug, just to confirm (since on the screenshot I can see

Wdf Tenant Id

as a reference to another dataset) - do you have the Workspace Data Filter applied to the

Dim sidd channels

dataset? Just to clarify, unlike normal filters and user data filters, the workspace data filters do not automatically propagate in the direction of arrow across the datasets in the model, but need to be explicitly applied and mapped to every dataset where they should be effective. You can check it either in the detail of the dataset on its “data filtering” tab or directly in the modeller there should be a “funnel” icon in the top right corner that opens list of workspace data filters and to which datasets they are applied.

@Michal Hauzírek @Mauricio Cabezas In DIM SIDD CHANNEL we have added the wdf_tenant_filter - as advised by your team - we added the wdf_filter to EVERY dimension and fact table. Your team also advised us to create a tenant table for the WDF Filter and that this would be the correct design So, we have a tenant table with all wdf_filter pointing to Dimension tables which point to the fact tables. I believe they are "explicitly applied and mapped to every dataset" but if you check what we have done you can see if im correct https://reporting.laivly.cloud/modeler/#/tenant-reporting-base-v3

Hi Doug, thank you for your clarification. I have impersonated your organization as our Admin user. I have two questions. You wrote that in

DIM SIDD CHANNEL

you have added the

wdf_tenant_filter

, how did you add it, Do you mean just with the arrow connection or by applying the WDF? I can see the WDF is not Applied in its details. And, another question, could you share with us, or let us know from which Child workspace/dashboard is the second image (filters) at the beginning of the thread, please? Thank you in advance.

Its a field in our table - i meant we added it to the table so that it would filter - we are connecting with two fields. I don't understand "I can see the WDF is not Applied in its details." Could be any child space... really...not Laivly..as we needed to fitler i managed to manually update each filter to add a metric and that for some reason worked.

Screenshot 2025-02-20 at 21.10.36.png

Got it, thats probably the issue.

Just to clarify - for the “Workspace Data Filter” to work within a dataset, it has to be explicitly enabled in each dataset where it should be effective (and mapped to a column in the associated table). There actually does not need to be any attribute or arrow representing this column. It can be there if you need it for the reporting i.e. want to display is somewhere, but if it is only for filtering, it does not need to be there. If you want all your datasets to be filtered by a workspace data filter, you should have tenant ID in all your physical tables in database exposed to GoodData and map the column in each of the datasets. Unlike standard visualization filters or dashboard filters, workspace data filters are not distributed between datasets over the arrows.

Yes i just didn't know about the last step we had the filter set in every table

Thank you Doug for you cooperation by providing all information to understand the issue. Have a nice weekend