Creating an alias
To add an alias for a pair of widgets:
Warning
If you use a new DataLens object model with workbooks and collections:
- In the left-hand panel, select
- Open the appropriate workbook and select an object.
Follow the guide from step 2.
-
In the left-hand panel, click create one.
Dashboards and select the dashboard you need. If you do not have a dashboard, -
At the top of the page, click Edit.
-
To the right of the widget to add a link for, click
.-
Select a link type in the list for the widget you are going to link.
-
In the window that opens, for both widgets, select from the list the fields for which you are creating the alias. The fields must be of the same type.
-
Click
-
Click Apply.
Warning
Please note that you cannot create aliases for fields from the same dataset or fields with the same IDs from different datasets.
-
At the bottom of the Links window, click Apply.
-
-
In the top-right corner of the dashboard, click Save.
A chart named tutorial — Line chart is based on the tutorial dataset and a chart named tutorial 2 — Table is based on the tutorial 2 dataset.
1. Let's add a tutorial — Date selector of the Based on datasets type to the dashboard. In the selector parameters, select the tutorial
dataset and the Date
field. A link between the selector and the tutorial — Line chart chart is established automatically, since they are based on the same dataset.
2. Let's add a tutorial 2 — Manual input selector of the Manual input type to the dashboard. In the selector parameters, select the Calendar element type and the Date
field.
3. Let's establish a link between the tutorial 2 — Manual input selector and the tutorial 2 — Table chart using an alias. When creating an alias, select the Date
field in the selector and the Date 2
field in the tutorial 2
dataset.
As a result, the tutorial — Date selector filters the tutorial — Line chart chart, and the tutorial 2 — Manual input selector filters the tutorial 2 — Table chart.
4. Let's establish a link between the tutorial 2 — Manual input selector and the tutorial 2 — Line chart chart using an alias. When creating an alias, select the Date
field in the selector and the Date
field in the tutorial
dataset.
Setting a link between the tutorial 2 — Manual input selector and the tutorial — Line chart chart links the tutorial 2 — Manual input and tutorial — Date selectors. This happens because the tutorial — Line chart chart and the tutorial — Date selector are based on the same dataset. As a result, any selector causes the appropriate values to be set automatically in the other selector and both charts' filters. To unlink the selectors, set their link type to Not linked.
When adding an alias, make sure the field the selector uses for filtering is included in the dataset used to build the chart. Otherwise, the link will not work.
When creating a link between widgets on a dashboard, you may encounter a situation when the link does not work. This usually happens when you create a link between a selector and a chart built from different datasets. Such widgets end up being linked based on a field that is not used in the selector.
Let's consider this case as an example:
1. There is a chart on the dashboard named Sample: Sales trends
built from a dataset called Sample CH Sales
.
There is a field in the dataset (chart) called ShopID
which takes string values, such as sp-11
, sp-18
, and sp-23
.
2. The Sample CH ShopList
dataset serves as the store directory. It includes two fields: ShopID
and ShopName
.
3. We will add a selector on the ShopName
field to the dashboard. The field contains the shop name (Tau
, Zeta
, Kappa
) from the Sample CH ShopList
dataset.
4. We will create a link between the selector and the Sample: Sales trends
chart using an alias. It is not possible to create a link based on the store name since it is not included in the Sample CH Sales
dataset used to build the chart.
Therefore, we will create the link using the ShopID
field.
As a result, the values you choose in the selector do not have any effect on chart visualization because the widgets are linked through the ShopID
field, and the the selector picks its values from the ShopName
field.
The link is illegal because you cannot use one field to pick values for a dataset-based selector and a different field as the target of a link between datasets. This link mechanism is not supported.