The filters added to the dashboard have been removed from the url

[al-ah]

Kibana version: 7.16.2

Describe the bug:
When you add a filter to the dashboard, that filter no longer exists in the URL and has been removed. See the figure below :

and its URL:

https://192.168.220.5:5601/app/dashboards#/view/Winlogbeat-Dashboard-ecs?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-30d,to:now))

But in version 7.12 this problem did not exist and the address is as follows:

https://192.168.220.5:5601/app/dashboards#/view/Winlogbeat-Dashboard-ecs?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-30d,to:now))&_a=(description:'Overview%20of%20all%20Windows%20Event%20Logs.',filters:!(('$state':(store:appState),meta:(alias:!n,disabled:!f,index:'winlogbeat-*',key:client.ip,negate:!f,params:(query:'127.0.0.1'),type:phrase),query:(match_phrase:(client.ip:'127.0.0.1')))),fullScreenMode:!f,options:(darkTheme:!f),query:(language:kuery,query:''),tags:!(),timeRestore:!f,title:'%5BWinlogbeat%5D%20Overview',viewMode:view)

[al-ah]

there is no answer ? :(

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[ThomThomson]

hi @alah64, the dashboard application state was intentionally removed from the URL in 7.14.0. I am going to close this issue as no specific problem that this causes was mentioned. If you have any specific problems we can re-open this issue to discuss workarounds!

[al-ah]

hi @ThomThomson, I imported the dashboards as an iframe in my plugin, and in previous versions I extracted and used the filter changes using the url. What can I do now that this feature has been removed?

Unfortunately, this trend, which has been going on for several years, has been dropped all of a sudden, and this can be frustrating for other developers who write plugins themselves.

[ThomThomson]

That's totally understandable @alah64, we actually added a PR to support a similar use case where a developer was pushing filters into an iframe dashboard via the URL. Your use case seems to be reading updates from the URL instead, but you could potentially work around that by using pinned filters in the iframe dashboard. Pinned filters will always be stored in the URL because they are part of the global state _g instead of the app state _a.

[al-ah]

That's totally understandable @alah64, we actually added a PR to support a similar use case where a developer was pushing filters into an iframe dashboard via the URL. Your use case seems to be reading updates from the URL instead, but you could potentially work around that by using pinned filters in the iframe dashboard. Pinned filters will always be stored in the URL because they are part of the global state _g instead of the app state _a.

Thanks for your tips
I hope I can use this method