4.4Data updates & reports
The essentials in 30 seconds
- REFRESH: When the SOURCES data changes, Refresh (Data ribbon → Refresh) reloads the data — the data shapes and graphs update. The diagram remains UPDATED without redrawing it.
- → LIVING DOCUMENTATION: we maintain the DATA (Excel/basic, easy), the diagram FOLLOWS. Reliable (up-to-date) vs. outdated (misleading) documentation. Manual or automatic update.
- REPORTS: extract the data carried by the table forms (equipment inventory, list of positions, status of stages) — the diagram becomes a SOURCE of usable data.
Ongoing mini-case — Nadia applies “Data updating & reporting”
Nadia, quality and organization manager in a service SME in Algiers, must update a linked diagram (living documentation) and generate reports — the data ↔ diagram relationship in both directions. She starts from “Updating data & reports” and follows the procedure: On a linked diagram (4-1), modify the SOURCES data (the Excel file) then UPDATE (Data ribbon → Refresh): the data shapes and graphs are updated. Notice the LIVING documentation: we maintain the data, the diagram follows (without redrawing it); configure an automatic refresh if necessary. Generate a REPORT from the diagram: a tabular list of shapes and their properties (e.g. equipment inventory with IP/model/state). Appreciate the two-way relationship: feeding data into the diagram (linking) AND extracting data from the diagram (reporting). Expected Result: You refresh a linked diagram (it stays up to date = living documentation) and generate reports (extract carried data) — the complete realization of Visio as a living and actionable data documentation tool.
Ongoing case from section 4.4: it comes back in the script and the 48 hour challenge.
1. Updating
One of the great advantages of linking to data (4-1) is that the diagram can remain UP TO DATE: this is UPDATE. When the SOURCES data changes (the Excel file is updated, the database evolves — new equipment, modified states, changed positions), we UPDATE the diagram (Data → Refresh ribbon) and Visio RELOADS the data from the source: the linked shapes receive the new values, the data graphics (colors, bars, etc.) are updated accordingly. The diagram then reflects CURRENT REALITY, without redrawing it. This is what makes a linked diagram a LIVING DOCUMENTATION: we maintain the DATA (in Excel/the database, easy), and the diagram FOLLOWS. You can update manually, or configure automatic updating (at intervals). When refreshing, Visio manages matches and can report changes (new rows, deleted rows, conflicts) depending on the configuration.
2. Reports
The other part of this section is the generation of REPORTS from the diagram. Since the shapes carry data (shape data, link to data), we can EXTRACT this data in the form of a tabular REPORT: a list/table of shapes and their properties (for example, the list of all the devices in a network diagram with their IPs, models, states; the list of stations in an organization chart with their information; a state of the steps of a process with their durations/responsibles). Visio allows you to define and generate reports (choose the shapes, the fields to include, the criteria) — the diagram becomes a SOURCE of data that can be used in return. These reports are used to document, inventory, analyze (an inventory of equipment from the diagram, a list of contacts from the organization chart). Thus, the data ↔ diagram relationship works in BOTH DIRECTIONS: we FEED the diagram from data (link, 4-1) AND we EXTRACT data from the diagram (reports). Important points. (1) Refreshing makes documentation ALIVE and RELIABLE (up-to-date) — a major asset (outdated documentation is misleading; documentation that is current is still useful). (2) The reports allow you to EXPLOIT the information contained in the diagram (inventories, lists, analyses). (3) These capabilities (especially advanced linking/refreshing) are more comprehensive in Visio DESKTOP. Refreshing and reporting completes the cycle of data-related diagrams: a diagram that CARRYS data (4-1, 4-3), DISPLAYS it (4-2), stays UPDATED (refreshing) and allows you to EXTRACT reports from it. This is the complete realization of Visio's vision as a LIVING, actionable data documentation and visualization tool: the diagram is no longer a frozen drawing, but a data-connected, up-to-date object and information source — the culmination of the power of Visio.
🔎 Concrete example — Maintain the source, not the drawing
The documentation no longer rots.
Edit Excel Inventory → Refresh → the diagram follows.
Extract a report: equipment inventory (IP, model, status).
→ garbage in: the source must be maintained.Result: reliable and usable documentation.
Reflex: establish a process for updating the source.
Section vocabulary
- Update
- Reload the data from the source (Data ribbon → Refresh) when it changes: linked shapes receive the new values, data graphs update. The diagram remains up to date.
Simple example: In “Updating data & reports”, Nadia applies it as follows: on a linked diagram (4-1), modify the SOURCES data (the Excel file) then REFRESH (Data ribbon → Refresh): the data shapes and graphs are updated.
What it is not: It is not a simple decorative element: without this reference, the diagram loses clarity or rigor.
Reflex: Refresh → reload the data from the source (Data ribbon → Refresh) when it changes: linked shapes receive the new values, data graphs update
- Living documentation
- Thanks to updating, a linked diagram remains synchronized with reality: we maintain the DATA (Excel/base), the diagram FOLLOWS — documentation that does not expire.
Simple example: In “Updating data & reports”, Nadia applies it as follows: on a linked diagram (4-1), modify the SOURCES data (the Excel file) then REFRESH (Data ribbon → Refresh): the data shapes and graphs are updated.
What it is not: It is not a simple decorative element: without this reference, the diagram loses clarity or rigor.
Reflex: Living documentation → thanks to updating, a linked diagram remains synchronized with reality: we maintain the DATA (Excel/base), the diagram FOLLOWS — documentation that does not expire
- Reports
- Extract the data carried by the forms in table form (list of forms and their properties: equipment inventory, list of positions, status of stages); the diagram becomes a data source.
Simple example: In “Updating data & reports”, Nadia applies it as follows: on a linked diagram (4-1), modify the SOURCES data (the Excel file) then REFRESH (Data ribbon → Refresh): the data shapes and graphs are updated.
What it is not: It is not a simple decorative element: without this reference, the diagram loses clarity or rigor.
Reflex: Reports → extract the data carried by the forms in table form (list of forms and their properties: equipment inventory, list of positions, status of stages)
- Data relationship ↔ bidirectional diagram
- We FEED the diagram with data (link, 4-1) AND we EXTRACT data from the diagram (reports) — in both directions.
Simple example: In “Updating data & reports”, Nadia applies it as follows: on a linked diagram (4-1), modify the SOURCES data (the Excel file) then REFRESH (Data ribbon → Refresh): the data shapes and graphs are updated.
What it is not: It is not a simple decorative element: without this reference, the diagram loses clarity or rigor.
Reflex: Data relationship ↔ bidirectional diagram → we FEED the diagram from data (link, 4-1) AND we EXTRACT data from the diagram (reports) — in both directions
- Reliability (up to date)
- Up-to-date documentation remains RELIABLE and useful; Outdated documentation is misleading. Refreshing is a major advantage of linked diagrams.
Simple example: In “Updating data & reports”, Nadia applies it as follows: on a linked diagram (4-1), modify the SOURCES data (the Excel file) then REFRESH (Data ribbon → Refresh): the data shapes and graphs are updated.
What it is not: It is not a simple decorative element: without this reference, the diagram loses clarity or rigor.
Reflex: Reliability (up to date) → up-to-date documentation remains RELIABLE and useful
In practice — Refresh data and generate reports
- On a linked diagram (4-1), modify the SOURCES data (the Excel file) then UPDATE (Data ribbon → Refresh): the data shapes and graphs are updated.
- Notice the LIVING documentation: we maintain the data, the diagram follows (without redrawing it); configure an automatic refresh if necessary.
- Generate a REPORT from the diagram: a tabular list of shapes and their properties (e.g. equipment inventory with IP/model/state).
- Appreciate the two-way relationship: feeding data into the diagram (linking) AND extracting data from the diagram (reporting).
Script to say — Data updating & reporting
1) On a linked diagram (4-1), modify the SOURCES data (the Excel file) then UPDATE (Data ribbon → Refresh): the data shapes and graphs are updated. 2) Observe the LIVING documentation: we maintain the data, the diagram follows (without redrawing it); configure an automatic refresh if necessary. 3) Generate a REPORT from the diagram: a tabular list of shapes and their properties (e.g. equipment inventory with IP/model/state). 4) Appreciate the two-way relationship: feeding data into the diagram (linking) AND extracting data from the diagram (reporting). Then I check: You update a linked diagram (it stays up to date = living documentation) and generate reports (extract carried data) — the complete realization of Visio as a living and actionable data documentation tool
Adapt the names, forms and distribution format to your context.
Copy and paste model — Card 4.4
Card 4.4 — Updating data & reports
Objective: update a linked diagram (living documentation) and generate reports — the data ↔ diagram relationship in both directions
1. On a linked diagram (4-1), modify the SOURCES data (the Excel file) then UPDATE (Data ribbon → Refresh): the data shapes and graphs are updated.
2. Observe the LIVING documentation: we maintain the data, the diagram follows (without redrawing it); configure an automatic refresh if necessary.
3. Generate a REPORT from the diagram: a tabular list of shapes and their properties (e.g. equipment inventory with IP/model/state).
4. Appreciate the two-way relationship: feeding data into the diagram (linking) AND extracting data from the diagram (reporting).
Expected result: You update a linked diagram (it stays up to date = living documentation) and generate reports (extract carried data) — the complete realization of Visio as a living and actionable data documentation toolSME / low budget
Minimum version: REFRESH: When the SOURCES data changes, Refresh (Data ribbon → Refresh) reloads the data — the data shapes and graphs update. The diagram remains UPDATED without redrawing it. We limit ourselves to a model, a diagram and a PDF export.
Algerian SME
Local context: → LIVING DOCUMENTATION: we maintain the DATA (Excel/base, easy), the diagram FOLLOWS. Reliable (up-to-date) vs. outdated (misleading) documentation. Manual or automatic update. We adapt the wording, examples and distribution formats to the team.
Remote work
Remotely: REPORTS: extract the data carried by the table forms (equipment inventory, list of positions, status of stages) — the diagram becomes a usable SOURCE of data. We favor cloud storage, sharing by link and comments.
Multidisciplinary team
For a mixed audience: data relationship ↔ BIDIRECTIONAL diagram: FEED the diagram from data (link, 4-1) AND EXTRACT data from the diagram (reports). Completion of Visio as a VIVANTE data documentation/visualization tool. We explain the symbols and keep the wording short.
✓ Best practices
- Maintain the data source (not the drawing).
- Update the diagram when reality changes.
- Generate reports to exploit the information provided.
✗ Common pitfalls
- Do not maintain the source (updated diagram shows outdated).
- Redraw by hand instead of refreshing.
- Believing that a linked diagram remains correct without updating the source.
Key takeaways
- REFRESH: When the SOURCES data changes, Refresh (Data ribbon → Refresh) reloads the data — the data shapes and graphs update. The diagram remains UPDATED without redrawing it.
- → LIVING DOCUMENTATION: we maintain the DATA (Excel/basic, easy), the diagram FOLLOWS. Reliable (up-to-date) vs. outdated (misleading) documentation. Manual or automatic update.
- REPORTS: extract the data carried by the table forms (equipment inventory, list of positions, status of stages) — the diagram becomes a SOURCE of usable data.
- Data relationship ↔ BIDIRECTIONAL diagram: FEED the diagram from data (link, 4-1) AND EXTRACT data from the diagram (reports). Completion of Visio as a VIVANTE data documentation/visualization tool.
48h challenge — apply tomorrow
Within 48 hours, take a real diagram and apply “Data Refresh & Reports”: You refresh a linked diagram (it stays up to date = living documentation) and generate reports (extract carried data) — the complete realization of Visio as a living and actionable data documentation tool Deliver the .vsdx and a PDF export, with a sentence about what has changed.
- I know how to explain: REFRESH: When the SOURCES data changes, refresh (Data ribbon → Refresh) reloads the data — the data shapes and graphs update. The diagram remains UPDATED without redrawing it.
- → LIVING DOCUMENTATION: we maintain the DATA (Excel/basic, easy), the diagram FOLLOWS. Reliable (up-to-date) vs. outdated (misleading) documentation. Manual or automatic update.
- REPORTS: extract the data carried by the table forms (equipment inventory, list of positions, status of stages) — the diagram becomes a SOURCE of usable data.
Frequently asked questions
Why is a self-refreshing diagram a major asset, and how can you keep documentation up to date?
A diagram that updates (stays in sync with its source data) solves a classic and frustrating documentation problem: its expiration. Understanding this asset and how to leverage it transforms your approach to documentation. The problem of obsolete documentation: documentation (a network diagram, a flow chart, a process map) reflects a reality at a given moment. But reality is CHANGING (new equipment, reorganizations, developments). STATIC documentation (drawn once) gradually OUTDATES: it becomes inaccurate, then MISLEADING (it shows a reality that no longer exists). Outdated documentation is worse than useless — it is misleading (we rely on an obsolete network diagram to troubleshoot, an outdated organization chart, etc.). And maintaining it by hand (redrawing for each change) is tedious, and therefore often neglected — hence the documentation that rots. Why a diagram that UPDATES is a major asset: (1) It easily stays UPDATED. A diagram LINKED to data (4-1) can be UPDATED: when the source data changes (the Excel file, the database), we update and the diagram RELOADS the data — it reflects the CURRENT reality. We don't have to redraw: we maintain the DATA (easy, in Excel/the database), and the diagram FOLLOWS. (2) Documentation no longer expires. As long as you maintain the source data (which is easier than maintaining a diagram), the diagram remains accurate through updating. Documentation becomes ALIVE and RELIABLE — it can be trusted. (3) Separation of data/presentation (healthy). We manage the SOURCE of truth (the data, in an easy-to-maintain format — Excel, base); the diagram is a generated/updated VIEW of this data. This separation is effective: maintaining data is simpler than maintaining a complex drawing. (4) Reduced effort. Updating an Excel file (add a row, change a value) is much faster than reworking a chart by hand. Refresh automates diagram updating. How to KEEP documentation up to date (best practices): (1) LINK the diagram to a data SOURCE (Excel, database, SharePoint — section 4-1) that contains the information (network inventory, directory, process data). The diagram becomes a view of that source. (2) Maintain the data SOURCE (easy to update) rather than the diagram. When reality changes, update the DATA (the Excel, the base). This is the key point: manage the data, not the drawing. (3) REFRESH the diagram (manually when you need it, or automatically at intervals): it reloads the data and reflects the current reality. (4) Establish an update PROCESS: define who/when updates the source data (e.g. network inventory updated with each infrastructure change), to keep the source reliable. An updated diagram is only reliable if its SOURCE is maintained. (5) For data that ALREADY exists in systems (inventories, directories, databases), LINK directly to these systems when possible — this way the diagram reflects the reference data, up to date at the source. The concrete advantages: (1) An updated network diagram linked to the inventory remains reliable documentation of the infrastructure (it can be relied on for troubleshooting and planning). (2) An organization chart linked to the directory reflects the current organization. (3) A project dashboard linked to tracking data shows actual progress. In any case, the documentation remains USEFUL (up to date) instead of rotting. Nuances: (1) Refresh assumes a maintained data SOURCE — if no one updates the Excel/database, the refreshed chart will show stale data (the chart reflects the source; garbage in). The discipline of maintaining the source is essential. (2) Advanced linking/refreshing capabilities are more comprehensive in DESKTOP Visio. (3) Not all diagrams lend themselves to data linking (a conceptual process flowchart may not have a data source) — linking shines for diagrams based on real data (network, flowchart, dashboards). In summary: a diagram that updates itself is a major asset because it resolves the OUT-OF-DATE of documentation — instead of static documentation that becomes out of date and becomes misleading (and painful to maintain), we have LIVING documentation that remains UP-TO-DATE via updating: we maintain the source DATA (easy — Excel, basic), the diagram FOLLOWS. To maintain up-to-date documentation: LINK the diagram to a data source, MAINTAIN the source (not the drawing), UPDATES the diagram, and establish a PROCESS for updating the source. This makes documentation RELIABLE and useful (instead of rotting), with reduced effort (managing data vs. redrawing). That's one of the great benefits of Visio data binding: diagrams that stay in sync with reality — living, reliable, actionable documentation, the culmination of Visio's power for data documentation.
What does refreshing a linked diagram do?