Embedding Preview doesn't behave like Metabase Application when filter is locked and linked about metabase HOT 1 CLOSED

Since this issue is split from #41586. I'll repost my comment which was specifically for the preview issue.

I can confirm that the preview and the embed behave differently. I updated the issue description with proper filter values to reproduce the issue. You need to set (3rd) Text 2 filter to have any values except Doohicky for this to happen.

The difference in the behavior is that when we query on preview, we call GET /api/dashboard/:id/params/:param-key/values to get the values. This would behave differently from when we're actually call on the dashboard since it would pass the linked parameter in the URL GET /api/dashboard/:id/params/:param-key/values?:linked-param-key=Doohickey.

When we call this on embed it's GET /api/embed/dashboard/:jwt/params/:param-key/values. And BE could use the parameter values inside the :jwt filter proper results.

I think what we should do here is to add an equivalent endpoint in preview_embed endpoint so we could call GET /api/preview_embed/dashboard/:jwt/params/:param-key/values instead of using the dashboard endpoint.

from metabase.