I have a base dashboard and child dashboards, each with different data source. I want to filters on these child dashboards to lead to this childs datasources, but instead I see base datasources filter, can this be somehow changed? I think it didnt been like this before last week.

Hi Marketa, Could you provide screenshots of what exactly you are seeing from your end, please? Also, did you just notice this change today?

The issue is with workspace hiearchy, we have base dashboard - which have several child workspaces, each with different data source. Newly there is a Workspace Data filter option. I dont want any child to see base - data - I just want to inherite data model from base. When I switch on WDF there is no data visible in child.

So you use different database/schema for each workspace and the problem is with displayed values in attribute filter dropdowns which do not match values which are visible in the workspace, right? Could it be that the displayed values are coming from cache? Can you try to clear the cache for the workspace?

So you use different database/schema for each workspace and the problem is with displayed values in attribute filter dropdowns which do not match values which are visible in the workspace, right? — Yes, exactly. Could it be that the displayed values are coming from cache? - No, didnt happened before. It is new. Can you try to clear the cache for the workspace? Yes, cleaned on all data sources - same result. Does Site attribute have multiple labels? What do you mean by labels? It happens for all fields not just site. Is it possible that the filter drop down shows a different label than you expect? No, it show data from different data source then expected.

Hi Marketa, Sorry for the delay on this. We cannot reproduce the issue. The data source per tenant as well as WDF work as expected and they even work together. So we nee dto have the following questions addressed: 1. What is the parent workspace and what is the child workspace id? 2. What data source is configured in the parent and what is the database and schema it is pointed to (data source ID, server, schema, user)? 3. Are the workspaces truly in hierarchy? Is the parent really direct parent of the child or are there any workspaces in between? 4. What is the metadata object of the child workspace entity? Does it contain reference with a different data source id? Is there path specified? Is the path pointing to a different schema? 5. Is WDF defined for the parent workspace as a root? 6. Is workspace mapping rule present for EACH dataset of the LDM (specificly for the dataset containing source column of the attribute which they claim does not work properly)? 7. Is the setting defined for the child workspace and what is its value? 8. Can you obtain traceId of labelElements and execute requests in the child workspace so that we can look into logs? 9. Can you double check if the target database+schema really contains different data for the child workspace than parent workspace? If you are able to address any of these, we might be able to better pinpoint the issue as we still cannot reproduce the same behavior.

What is the parent workspace and what is the child workspace id? • Patent ID: 791c5675ec964350901e5af9e395base • Child ID: a3ba19c6e04e45dda861ebc3fa79daaf What data source is configured in the parent and what is the database and schema it is pointed to (data source ID, server, schema, user)? • Parent ◦ Data Source ID: 31aeeb6d-85ae-403a-850e-b1c1550f9b8d ◦ Schema name: public ◦ User: gooddata-dev Are the workspaces truly in hierarchy? • Yes Is the parent really direct parent of the child or are there any workspaces in between? • Yes they are, parent is true parent, no workspaces between What is the metadata object of the child workspace entity? ◦ What do you mean? Does it contain reference with a different data source id? ◦ Child have different source ID then parent Is there path specified? ◦ What do you mean? Is the path pointing to a different schema? ◦ same schema - “public” in different data sources Is WDF defined for the parent workspace as a root? ◦ WDF not defined Is workspace mapping rule present for EACH dataset of the LDM (specificly for the dataset containing source column of the attribute which they claim does not work properly)? ◦ Yes Is the setting defined for the child workspace and what is its value? ◦ What do you mean? Can you obtain traceId of labelElements and execute requests in the child workspace so that we can look into logs? ◦ How? Can you double check if the target database+schema really contains different data for the child workspace than parent workspace? • In database data are correctly Update: Without any changes, the filters acts properly now. Sending screenshot, we didnt done any changes on our site. Can you please investigate what changes was done that this changed back?

Hi Marketa, It's a bit difficult to try and search if no changes had been made at all. Did anything change in the data sources themselves? We can try and search the logs, but we would need the dashboard ID, or url to the dashboards in question.