Hello,
thank for help, but I think it’s none of those, so I’ll try to explain better. My dashboard contains a table, which has a column “groupname” and a column “amount”. It also has a filter (a timespan, if that matters).
Lets take a special group as an example, and suppose there will be 10 records in that group if the dashboard filter is empty. So one of the rows of the table is
groupname | amount
mygroup | 10
Now I Select “Today” in the Timespan-Filter. This reduces the records to 3. Now that row is
groupname | amount
mygroup | 3
Everything as expected up to this point. But if I click on the “3” and select “View …” a question is generated with the filter for the “groupname”, and I end up with the 10 records. I expect only 3. The dashboard filter is ignored.
To the second part of the question: If I change the data model, I change the visibility of the columns everywhere, or am I not? Of course I have columns which are nowhere of interest. But others are relevant in one context, and irrelevant in another.
Sincerely
ctp
{
“browser-info”: {
“language”: “de”,
“platform”: “Win32”,
“userAgent”: “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:85.0) Gecko/20100101 Firefox/85.0”,
“vendor”: “”
},
“system-info”: {
“file.encoding”: “UTF-8”,
“java.runtime.name”: “OpenJDK Runtime Environment”,
“java.runtime.version”: “11.0.7+10”,
“java.vendor”: “AdoptOpenJDK”,
“java.vendor.url”: “https://adoptopenjdk.net/”,
“java.version”: “11.0.7”,
“java.vm.name”: “OpenJDK 64-Bit Server VM”,
“java.vm.version”: “11.0.7+10”,
“os.name”: “Linux”,
“os.version”: “4.15.0-128-generic”,
“user.language”: “en”,
“user.timezone”: “GMT”
},
“metabase-info”: {
“databases”: [
“mysql”,
“sqlserver”
],
“hosting-env”: “unknown”,
“application-database”: “mysql”,
“application-database-details”: {
“database”: {
“name”: “MySQL”,
“version”: “5.7.33-0ubuntu0.18.04.1”
},
“jdbc-driver”: {
“name”: “MariaDB Connector/J”,
“version”: “2.6.2”
}
},
“run-mode”: “prod”,
“version”: {
“date”: “2021-01-05”,
“tag”: “v0.37.5”,
“branch”: “release-x.37.x”,
“hash”: “be537ee”
},
“settings”: {
“report-timezone”: null
}
}
}