In https://github.com/elastic/kibana/issues/111777, we decided that we want the Dashboard sharing data to be trimmed down, by providing references to saved objects, and unsaved changes by-value. This solves an issue with automating report generation where too much state by-value causes the POST URL to be too long to be used at all.
This means the POST URLs will often contain a hybrid state of references and state by-value. It makes maintenance of the automated report very complex, because the by-value state is permanent but the state that is referenced can be changed at any time.
We don't want to confuse users by giving them a surprise results in their reports, based on permanent state and state that can be edited later. We will add info in-context when the POST URL contains the hybrid state. We will keep the information in the UI terse and make sure if flows nicely with the context. More detail on this subject must be provided in the guide to automating reports in the documentation: https://www.elastic.co/guide/en/kibana/7.14/automating-report-generation.html
Kibana version: 8.x
In https://github.com/elastic/kibana/issues/111777, we decided that we want the Dashboard sharing data to be trimmed down, by providing references to saved objects, and unsaved changes by-value. This solves an issue with automating report generation where too much state by-value causes the POST URL to be too long to be used at all.
This means the POST URLs will often contain a hybrid state of references and state by-value. It makes maintenance of the automated report very complex, because the by-value state is permanent but the state that is referenced can be changed at any time.
We don't want to confuse users by giving them a surprise results in their reports, based on permanent state and state that can be edited later. We will add info in-context when the POST URL contains the hybrid state. We will keep the information in the UI terse and make sure if flows nicely with the context. More detail on this subject must be provided in the guide to automating reports in the documentation: https://www.elastic.co/guide/en/kibana/7.14/automating-report-generation.html