Hello,
We have multiple embedded dashboards live with our customers, however when selecting values from a filter the dashboards break when the number of selections is relatively large i.e. 80-100 values manually selected.
I've tested this across several embedded dashboards and for different filters/fields and the same issue seems to be occurring. In the normal metabase UI (non-embedded) everything works as expected.
We're on version 0.44.0
Many thanks,
David
Hi @dmellor
What is your definition of "break"? Are there errors? Check Admin > Troubleshooting > Logs.
Latest release is 0.44.4: https://github.com/metabase/metabase/releases/latest
Hi @flamber apologies for the vague terminology there - "breaks" as in all questions display "There was a problem displaying this chart."
In the logs, when I add an additional value to the filter (and the charts don't work still) the only thing I can see is :
[f23f082f-998e-4674-b8ca-85bdd051236c] 2022-10-12T12:04:19+01:00 WARN org.eclipse.jetty.http.HttpParser Header is too large 8193>8192
However (not sure if this is related), when loading the embedded dashboard with no filter selections, which does work fine, I do see this error (truncated):
[a90bb35a-b3ec-4c8c-bc44-4eeb0ed4a445] 2022-10-12T12:06:08+01:00 ERROR metabase.models.params Could not find matching Field ID for target: [:dimension [:template-tag form_data_country_code]]
clojure.lang.ExceptionInfo: Output of unwrap-field-clause does not match schema:
[(not (present? :field)) (not (present? "id-or-name")) (not (present? "options"))]
{:type :schema.core/error, :schema (constrained [(one (eq :field) :field) (one (cond-pre (constrained Int "positive integer") (constrained Str "Non-blank string")) "id-or-name") (one (maybe (recursive (var metabase.mbql.schema/FieldOptions))) "options")] ":field clauses using a string field name must specify :base-type."), :value nil, :error [(not (present? :field)) (not (present? "id-or-name")) (not (present? "options"))]}
@dmellor Allow larger headers: https://www.metabase.com/docs/latest/configuring-metabase/environment-variables#mb_jetty_request_header_size
You can ignore the missing field error:
https://github.com/metabase/metabase/issues/15494 - upvote by clicking 
on the first post
Many thanks!