Hello,
 

Unfortunately, such changes are not feasible in the context of Classic UI dashboards, as the configuration of these charts (dashboard object, filters, sorting, etc.) is stored in the database as JSON configurations.

 A whole tab corresponds to a single record in the SysDashboard table, and all settings are stored in the Items column.
 

In this format, the field value used for filtering is not just an Id, but an entire config with various parameters.
 

Therefore, a much faster solution would be copying the dashboard tab and modifying it manually:

On the other hand, in Freedom UI, dashboards are not stored in the database but directly in the schema of the page. As a result, you can modify the parameters directly in the schema.


 However, this approach also requires time and is unlikely to yield a faster result than simply copying and manually adjusting the lookup field value.

Also, in Freedom UI, you can dynamically filter charts using the Quick Filter. This way, you only need to configure the charts once, and by using the quick filter, you can check all regions of interest dynamically.
 

Thank you for reaching out!

Pavlo Sokil,

Does the approach with Freeform UI work for Dashboards (Підсумки), but not for separate Entities (Sections like Lead or Opportunity)?

Leonid,
 

The Dashboard section is a unique section implemented in Classic UI, and unfortunately, it is not possible to configure such a dynamic filter in this section.
 

However, you can manually set up same dashboards in Freedom UI. For example, you can create a new home page and implement the solution with quick filters there.

Leonid writes:

Pavlo Sokil,

Does the approach with Freeform UI work for Dashboards (Підсумки), but not for separate Entities (Sections like Lead or Opportunity)?

If you select data from SysDashboard, you can find dashboard configuration. I see filtration settings are stored in Items column. 
Maybe you can update this with SQL script

Hi Leonid, 

You could build one dashboard and then install the Quick filters for Creatio, add a simple filter to the section and let the end users apply that filter themselves. I believe it'd be cashed for them anyway if they want to have it always applied. 

https://marketplace.creatio.com/app/salesup-quick-filters-creatio

Best,
Jacek

Hi,

When dashboards are added to an edit page, the corresponding records are created in SysWidgetDashboard and SysWidgetDashboardLcz tables.

If a dashboard is added not to an edit page but to the "Dashboards" tab, then records will be added in the SysDashboard and SysDashboardLcz tables, respectively.
.
Also, these data are correspondingly bound to the package that was set as the current package when the dashboards were created.

The thing is that dashboards are localizable system objects. When a dashboard is created, records are created in two tables:
- a record about a dashboard created in the localization, which corresponds to the base culture of the system, is created in the [SysWidgetDashboard]/[SysDashboard] table;
-records about dashboards of all other localizations are created in the [SysWidgetDashboardLcz]/[SysDashboardLcz] table and are linked to a record in the [SysWidgetDashboard]/[SysDashboard] table by the [RecordId] column.

So, basically, all you need to do is prepare a package that contains all the needed data bindings and SQL scenarios to perform the records' entry into the tables mentioned above.

More information on data binding is available at our academy.
Also, knowledge of SQL might be needed to find the needed dashboard in the database, although you can always create a lookup and search via UI.