Wiki source code of Analyse des dépendances

Last modified by Aurelie Bertrand on 2026/07/06 16:22
Show last authors
1 {{ddtoc/}}
2
3 ----
4
5 (% class="wikigeneratedid" %)
6 Dependency analysis is a mechanism that enables you to identify the relationships between the various elements of your environment.
7 For example, you can easily determine which dashboard pages use a chart, or identify all the charts that use a particular format.
8
9 = Dependency analysis =
10
11 (% class="wikigeneratedid" id="HUsages" %)
12 When the tool is opened, the analysis runs automatically.
13
14 (% class="wikigeneratedid" %)
15 The dependency analysis scans all DigDash elements, starting with roles. The more elements there are (Flows, data models, dimensions, measures, etc.), the longer the analysis may take.
16 If you are using a WLNK file server, all files on the server are analysed. If the server contains a very large number of elements, the analysis time may increase considerably.
17
18 (% class="wikigeneratedid" %)
19 Once the analysis is complete, your entire environment is mapped out and you will be able to analyse categories of elements or specific elements.
20
21 (% class="wikigeneratedid" %)
22 [[image:Dpeendency_analysis_en.png]]
23
24 For example, to find out whether a format is being used, and by whom, apply the following filter:
25
26 * In the **Filters** section, open the **‘Focus on** ’ drop-down menu to select **‘Format’:
27 **[[image:1783344601066-128.png]]
28
29 * Then, in the **Display** section, change the display order from **‘contains** ’ to **‘used by'**:
30 [[image:1783344692585-931.png]]
31
32 This way, the view displays all formats, and by expanding the ‘Formats’ items, you can see where they are used:
33
34 [[image:Dpeendency_analysis_format_en.png]]
35 In the screenshot above, the **Euro **format **is **used by 11 charts in the **Retail** role.
36
37 This allows you to identify precisely how all the elements in your environment are used.
38
39 The **‘Backup’** button takes you to the page for **backing up your **data. See the page [[Backup and Restore>>doc:Digdash.deployment.configuration.backup_restore.WebHome]] page for further details.
40
41 == Relationships between resources ==
42
43 Please note that some links between resources are not immediately obvious.
44 It is important to bear in mind both directions: ‘**contains**’ and ‘**is contained in**’.
45
46 === {{glossaryReference glossaryId="Glossary" entryId="Flux"}}Flow{{/glossaryReference}} (chart) ===
47
48 A flow can be used in at least two different ways:
49
50 * because it **is used within** a dashboard page
51 * because it **contains** a device, such as an email
52
53 So, by using the “used” filter in “is contained in” mode, you can see charts that are not on any dashboard page, nor in any {{glossaryReference glossaryId="Glossary" entryId="fabrique de documents"}}document builder{{/glossaryReference}}. And yet they are identified as “used” because they contain a link to a device (document server, email, FTP, etc.).
54
55 === Measure and dimension ===
56
57 Measures and dimensions can be used in a wide variety of contexts (non-exhaustive list):
58
59 * chart
60 * interaction
61 * hierarchy
62 * formatting
63 * objective
64
65 However, a measure may also be used in none of these elements, and serve only to calculate another measure.
66
67 = Other uses of dependency analysis =
68
69 == Studio: confirmation of actions ==
70
71 In your day-to-day use of Studio, you will need to delete elements that may be used simultaneously in very different contexts, and potentially as a result of actions taken by other users.
72
73 Thanks to dependency analysis, you will be notified of the use of the elements you wish to delete:
74
75 [[image:Format_deletion_warning_en.png]]
76
77 In the example above, 3 formats are to be deleted, but the confirmation window indicates that two of them are currently in use: **Euro**, **Nbr. abbrev..**
78
79 == Studio: on-demand analysis ==
80
81 Still within Studio, you are not obliged to use the **Dependency Analysis** manager as your starting point.
82
83 For example, by right-clicking on a chart, you can see at a glance where they are used:
84
85 [[image:Dpeendency_analysis_flow_en.png]]
86
87 The manager opens. The view is already filtered to show the selected chart and is in ‘is contained in’ mode.
88 You can then see at a glance that the chart appears on **a dashboard page**:
89
90 [[image:1783346679740-536.png]]
91
92 The same principle applies to data models, formats, document servers and all elements of your environment.
93
94 == Saving ==
95
96 The dependency analysis mechanism is also used transparently during **saving:**
97 you can select just one chart and all the elements on which it depends will be included in the restore archive (formats, colours, scripts, etc.).
98
99 In the screenshot below, a single chart has been selected (by clicking on the numbers to the right of the tick box in the Wallet column):
100
101 [[image:Roles_en.png||height="86" width="745"]]
102
103 In the options available via the **Options** button at the top right of the page, you must tick the first box before downloading:
104
105 [[image:Backup_options_en.png]]
106
107 See the page [[Backup and Restore>>doc:Digdash.deployment.configuration.backup_restore.WebHome]] for further details.
108
109 == Data Catalog ==
110
111 The dependency analysis manager allows you to query a specific element on an ad hoc basis, but you can also generate reports. This enables you to analyse or document entire sections of your environment in the form of tables or graphs, and even use a {{glossaryReference glossaryId="Glossary" entryId="fabrique de documents"}}document builder{{/glossaryReference}}.
112
113 To do this**, **you can use data sources of the **‘Data Catalog’ **type. See** **the page [[Connecting to the Data Catalog>>doc:Digdash.user_guide.studio.Create_datamodel.Data_connection.connect_data_catalog.WebHome]] for further details.
114
115 [[image:Dependency_data_catalog_en.png]]
116
117 (% class="wikigeneratedid" %)
118 In the example above, we are creating a three-column data source: **{{glossaryReference glossaryId="Glossary" entryId="Flux"}}Flow{{/glossaryReference}}**, **Dashboard Page**, **Role**.
119 This enables you to create charts showing the links between flows and **dashboard** pages by role.
120
121 (% class="wikigeneratedid" %)
122 Another type of source, more focused **on “documentation”**, could present **measures and data sources** by **role**.
123 By ticking the **“Description”** box for the **Measures **and **Data Sources **columns, you can then create tables explaining the purpose of each metric. As the tables can be filtered by role and data source within the dashboard, navigating this new, customised knowledge base is made easier.