Embedded dashboard with locked filters doesn't fill dropdown options

[larsko]

Hello,

We have been using metabase now for a few years, but since last month (possibly a longer) we are experiencing issues that the dropdown filter doesn't get populated with data. They show as a search box instead of a dropdown with choices. This only happens in the embedded dashboards, on metabase itself the dropdowns do get populated.

I also raised an issue on github about this, but sadly there was no reply here, hence why I'm making this here aswell.

Basically we have a filter that is a unique code per customer. This is a locked filter, but when that is the case, the linked filters to that show up as a search box, instead of a dropdown with options.. But when I change the customer code to be an editable filter, the linked filters work as expected, so we get the dropdown with the options.

Presumable this is because we go over the limit of (300?) items in the dropdown when we haven't grouped by the unique customer code yet, so the linked filters show up as a searchbox, and then only afterwards the customer code filter is applied?

I think there was another user which has a similar issue as we have posted here: Dropdown filters display as text fields once embedded

[larsko]

Upon further investigation, it seems like the params which we send in our payload are automatically used as a linked filter for our filters, even though the filters are not set up this way.

Example:
ContainerID is our locked filter which we send with the payload like given in the example.

We have these filter options:

Where products groups is not linked to the ContainerID filter

but StandardProduct for example is:

So when we then have our embedded dashboard in a customer enviroment, I would expect the ProductsGroups filter to be filled with data from ALL customers, since it is not linked to the ContainerID filter.
And the StandardProduct filter will only be filled with data from specifically that ContainerID.
But both of these have an amount of options of only the specific ContainerID

So my question is, are filters given through the payload supposed to be acting like a "linked filter" even though it is not specified that way in the dashboard? We have used it that way for years, and it seems that only in the last few months this behaviour has changed.