On the edit page it still works normally, but when I switch to share or attach the link to another software, all the charts fail.
In addition, when I select multiple objects in the filter, the charts get an error, and the editing page is still normal.
What version of Metabase are you using?
Do the underlying tables have their permissions set so All Users can query them? Public dashboards can only use unrestricted objects as they don’t have a credential.
I am using version 0.53.10.5
On the edit page, when I select many things, it still returns the values in the charts, but when I select about 3 or 4 things with the public link, it still works, but when I select about 7 or 8 things, it gives an error as shown in the picture.
I wonder if we’re hitting a URL length limit somewhere.
Are you accessing Metabase through a proxy, like nginx?
Is there anything in the browser dev tools console? Or any exceptions in the Metabase log?
I am using Internet Information Services (iis) proxy to run metabase. Then is it affected?
Looks like it is. I’m not that familiar with IIS (not a Windows Server guy) but a quick Google finds mentions of URL length configurations in a few places. This post seems to provide a good summary:
Documentation on web filtering features, where this limit might be enforced:
I think it's related to the values in the filter, for example, if the string contains ".", "," or "-", it will error the charts. Because I tried with a string value such as "A B C" it works fine, but when I changed it to another value like "A,B,C" it got an error.
If special characters are breaking it, then there’s a bug; those should be URL-encoded before getting into the query string.
Any chance you can upgrade to a more recent version? At least 53.18 if you don’t want to invoke any major changes? The current major version is 57.
Currently the couple is running versions 0.47.7 and 0.53.10.5. Then tell me which version should I upgrade to for the above problem? Because currently the public link has an error when selecting multiple values in the filter
It would probably help to run 56 or 57, which are under active development. Bugs in your old versions won’t get fixed.
I first check that IIS isn’t (accidentally or otherwise) de-escaping the URL during the rewrite phase and you need to re-escape it afterward to ensure the URL string is still valid.