Tableau Interactivity: Parameters, Combined Fields, Sets, and Filtering

7.1 Recap: Tableau Foundations and the Opening Quiz

7.1.1 What We Covered Before This Session

This session opens with a fast recap of everything the course has built so far, because the whole rest of the day leans on it — parameters, combined fields, sets, and filtering are all built on top of the vocabulary you already know.

The Tableau product family has many members — Tableau Server, Tableau Desktop, and Tableau on cloud among them. Desktop can be installed two ways: a 14-day trial version, or a one-year license that Tableau gives to students and anyone in academics. The very first step of any Tableau work is the data connection, which is also how every new project should start. There are file-based connections where we give a file — an Excel file or a text file — server-based connections where Tableau talks directly to server databases (roughly 80–90 different connections exist), and some safe data sources that ship ready to use.

Two connection modes matter for performance. A live connection keeps the data live, so the figures on the sheet refresh on the fly; that makes sense when we really need real-time numbers. When the data is huge and the purpose is analysis rather than real time, we can use an extract instead: Tableau takes a one-time dump of the data onto the laptop, and all the analysis runs against that local copy.

We also covered the six data types, and a feature called the data interpreter, which activates automatically whenever the data is not in a clean table format. In the demo it handled an Excel file with merged cells and even a PDF; you tick the checkbox, Tableau cleans the data as best it can, and then it gives you a report highlighting every change the data interpreter made. It is up to us to accept the cleaned version or stick to the original data. Once data is loaded, the view data option lets us glance through it, and we toured the Tableau visual interface: the cards, the pills, the show me tab, and the file menu. One naming detail that keeps coming up: fields are sometimes called pills, because once you place a field on one of the shelves, its size and shape are very close to a real pill, and the name stuck.

The two most important classification terms are dimensions and measures.

We also learned a little about hierarchies, sorting, and grouping, and today the session returns to those topics briefly. The instructor deliberately does not expect anyone to memorize the interface; these things come naturally with use, and the recordings cover anything we miss.

7.1.2 The Opening Quiz: Questions and Answers

The recap quiz is a quick-fire round over the terms above. Nobody is being judged — it exists purely to refresh. Every exchange, with the reasoning given, is preserved here.

7.2 Parameters

7.2.1 Why Parameters Exist

A parameter is a value we keep outside the visualization itself, so we do not have to hardcode numbers inside it. The instructor's analogy is code: when we write programs or keep files, we sometimes hold variables or numbers outside the code and pass them in as parameters, and the code changes automatically. Tableau has the same idea. On its own a parameter does nothing — it is an independent component that sits idle somewhere until a view or a filter uses it. Instead of editing a criterion every time the user's request changes, we create a parameter, link the visualization to it, and then changing the parameter changes the visualization for us.

7.2.2 Creating a Parameter and Linking It to a Filter

The worked example starts with a plain view: sales of all subcategories, built by dragging subcategory and sales onto the sheet. The request changes to "show me top 10, not all," so we right-click and add a filter, choose top by field, and type 10. It works, but the moment someone asks for top 5 instead, we have to go back into the filter, edit the criteria, and reapply. That is the pain parameters remove.

Instead of typing the number, the filter dialog offers a "create a new parameter" option. We name the parameter, and give it a minimum of 1 and a maximum of 10 — the range the end user is allowed to pick from. Now the new parameter appears as an object we own. We edit the filter again, but this time we choose "use parameter" instead of typing a number, so the filter takes its value from the parameter. Finally we right-click the parameter and choose show parameter, which places a visible control on the sheet. From then on, dragging the control to 5 shows five bars, 6 shows six, 7 shows seven, and so on — the user can go all the way from 1 to 10, and both extremes come from the range we set when creating the parameter. Nothing in the filter dialog is touched again; the whole chart follows the parameter value.

Comparison — hardcoded value versus parameter

When to pick which: a one-off fixed view can keep a hardcoded number; any view the user is expected to interrogate ("top 5 versus top 10 today?") should be parameter-driven.

7.2.3 What Parameters Do for Dashboards

The real payoff shows up later, because dashboards are all about interaction. Every parameter we create appears in a shared list of params, and those params can be used inside filters anywhere. When we say show parameter, we hand the end user the control, and they can explore top 5 versus top 10 on their own. The instructor frames this as the direction of the whole course: user asks "show me top five" today, "show me top ten" tomorrow — with a parameter the user does it themselves, and the interactiveness of the dashboard grows without the developer rebuilding anything.

Visual intuition: picture the finished sheet — subcategory names running down the rows, sales bars extending to the right, and the parameter control (a slider with "1" and "10" at the ends) floating on the sheet. Slide the thumb toward 5 and, bar by bar, the chart trims down to the five tallest bars; slide to 10 and the rest of the bars reappear. The tallest bars never change order — only how many of them stay visible, which is the takeaway: the parameter controls the cutoff, not the ranking.

Real-world & domain connection: parameter-driven top-N selectors are the most common dashboard control in business reporting — retail dashboards let a sales manager slide "top 10 stores" to "top 5 stores" before a weekly review, and finance teams reuse one parameter across every regional P&L sheet so a single control updates the whole workbook. In dashboard design terms, this is the shift from developer-built, fixed views to user-driven exploration: the visualization no longer answers one question, it hands the user the tool to ask their own.

7.3 Combined Fields

7.3.1 The Problem: Sorting Stays Inside the Groups

Sometimes we want two or more fields to behave as one. The demo builds a view of category and subcategory wise sales — a crosstab where category groups the subcategory rows. When we sort by sales from high to low, the sorting happens within the groups: the rows get sorted inside category and subcategory first, so the highest value overall in that view reads 320k, and each category block stays internally ordered. That is fine for browsing, but sometimes the user says, "I do not want the subgrouping — show me all the numbers sorted genuinely, top to bottom, across everything." That is the situation where we combine fields.

7.3.2 Combining Two Fields

To combine, right-click on one of the fields (category, for example), choose create, then combine fields, and add the second field (subcategory). Tableau collapses the two into a single combined field, and the hierarchy grouping is gone — category and subcategory now behave as one entity. Dragging the combined field in and sorting by sales sorts the values genuinely by number, regardless of which category a combination belongs to.

The difference is visible in the row order: the combined field treats "furniture + chair" as one key, so it can sit anywhere in the list based purely on its number.

7.3.3 Combining Three or More Fields

The same move works for three fields and more, and we can change the sequence of the fields inside the combination.

Visual intuition: picture the crosstab before combining — the row headers are indented in a tree (Furniture holding its subcategories, then Office Supplies holding its own), and the sales column bounces up and down as the group resets. After combining, the same rows become a single flat list: one unindented header per triple, sales falling steadily from 101 to the fasteners' low value, with no bumps where a new category begins. The flatness of the row headers is the visual signature that the sort is now genuine.

7.3.4 When Not to Combine

It matters not to over-correct. These group-wise crosstab views are not bad views — they are very useful when comparing region-wise or category-wise sales, and the instructor stresses that the combined field is for the cases where we genuinely need one flat, genuinely sorted list. Choose combine only when the grouped sort gets in the way; keep the grouped views for comparison work.

Real-world & domain connection: analysts combine fields when handing a "true top 20" to leadership — for example, ranking every product × store × region triple across a chain, or every country × business-line pair in a global P&L, so the biggest number genuinely surfaces instead of the biggest number per silo. It is the reporting handoff counterpart to exporting crosstabs: the flat list is what a decision maker reads top-to-bottom, and the grouped view is what an analyst compares column by column.

7.4 Sets

7.4.1 What a Set Is

A set is a hand-picked collection of members from a field, grouped together so Tableau always treats them as one unit. Unlike a hierarchy, which joins related fields at the field level, a set is not tied to field relationships — we can create a set out of anything, picking members randomly or by rules. Once a set exists, we can color by it, compare it against everything else, and reuse it in other sheets.

Comparison — set versus hierarchy

When to pick which: a set answers "these specific members travel together"; a hierarchy answers "this field belongs inside that one."

7.4.2 Creating a Set by Selection

The first demo starts with subcategory-wise sales sorted high to low. We want a few of those subcategories to travel together, so we drag the mouse over the bars we care about — Tableau highlights everything under the selection — right-click, and choose create set. Naming it my set finishes the job. Drop the set on color, and the selected members all get one color while everything else stays differentiated, so the set members jump out of the chart instantly.

7.4.3 Creating a Set Through the Dialog

The second route avoids the mouse: right-click a field, choose create set, and build the set from the dialog. The example defines a set that always contains table and chair together — whenever the data contains those two members, they belong to the set. Color by that set, and table and chair show as one group against the rest; the chart immediately tells us how this set is doing versus others. This dialog route is the one to use when the membership is a standing rule rather than whatever happens to be selected today.

7.4.4 Turning a Set into a Top Group

A set does not have to be frozen. Editing a set opens the same dialog, where we can swap the fixed member list for a rule — for example, "always show the top five members of this group." Now the set is dynamic: it still works as one color-coded unit, but its membership is always whatever the top five happen to be. That keeps the story current as the data changes.

7.4.5 A Real-world Set: Metros by GDP

Real-world: the instructor's example is state-wise GDP for all of India. With data on 20-plus states, comparing everything gets noisy, but the user only cares about the metros. We would select Delhi, Mumbai, Kolkata, and Bangalore and make a metro set; from then on that set always travels together in every comparison and every color coding, and the non-metros can be filtered away or kept as the contrast group. The same pattern generalizes to any product group, customer group, or region an organization cares about.

Visual intuition: picture a state-wise GDP bar chart, twenty-plus bars in a single color — the eye can spot the tallest few, but "how are the metros doing as a group?" takes a scan of every bar. Color the metro set, and four bars light up in one color while the rest stay muted: the comparison "metros versus the rest" now resolves before you finish looking at the chart. One color, one glance, one question answered.

7.4.6 Sets in Stories and Dashboards

Sets are where narratives start. When we build stories or dashboards, we often want to talk about specific things only — say, chairs and tables as the top four of the twelve items. A set gives us that focus: color the set, filter to the set, and every sheet in the dashboard knows which members are the protagonists. Any combination or permutation of members can become a set, which is exactly what makes sets flexible for visualization.

Real-world & domain connection: segment sets are a standard pattern in organizational reporting — a customer-success team defines a "top accounts" set for every dashboard, a marketing team keeps a "hero products" set across all their campaign sheets, and the metro-set pattern (Delhi, Mumbai, Kolkata, Bangalore in state-wise GDP data) is exactly how analysts focus executive dashboards on the few states that matter instead of all twenty-plus. Sets are how a narrative picks its protagonists once, in one place, and every sheet follows.

7.5 Titles and Captions

7.5.1 Editing the Title

Every worksheet shows a title at the top, and by default that title comes from the sheet name — sheet 1, sheet 2, and so on. That default is only a starting point: double-click the title and it becomes editable. We can give the sheet any title that describes the graph, such as "subcategory wise sales," change alignment to center, make it bold, and increase the font size so the heading actually reads as a heading. Double-clicking again later still lets us change any of it.

7.5.2 Auto Fields and Formatting the Title

Beyond plain text, the title editor can insert auto fields — dynamic pieces that Tableau fills in for us. The demo inserts the workbook name, and then the data source name, so the title reads something like "Subcategory wise sales — data source: Sample Superstore"; page count is another option. We can remove any inserted field with a click, combine them with separators such as a colon, and set background colors if we want the title to stand out. For proper formatting there is a separate format title option on the right-hand side: it controls shading (the demo gives the title a light gray gradient background) and borders (a dark blue border around the title is one click away).

7.5.3 Captions: Show, Hide, Edit

A caption is the explanatory line that can sit under the title. Captions come from the worksheet menu: show caption toggles one on, and Tableau fills in a default caption automatically. Like the title, the caption can be double-clicked and edited — make the font bigger, center it, make it italic, change its color. Both elements can be hidden independently through the worksheet menu (don't show title / don't show caption), which is handy when the sheet is small or the graph explains itself, and both can be brought back the same way.

7.5.4 Resetting with Clear

Formatting is easy to overdo, and stakeholders will sometimes ask for the plain default back. The format title and format caption panels both include a clear button: one click removes every formatting choice — shading, border, font changes — and restores the original default appearance. Nothing is lost permanently, because the edits were only formatting, not data.

Real-world & domain connection: titles are the first thing a stakeholder sees in a shared dashboard or a PDF export, so the demo habit — a descriptive title plus a live data-source label — is standard practice in organizations that ship recurring reports, where "which workbook, which data" must be verifiable at a glance even months later. The Clear button maps directly to the design principle that formatting should serve readability, not decorate it.

7.6 Exporting Worksheets

7.6.1 The Export Menu at a Glance

Tableau worksheets can leave Tableau in several formats. The export options are: print to PDF, export as image, export the data as an MDB file (Microsoft database), export the crosstab to Excel, and copy to the clipboard. Which one you pick depends on who is asking — a stakeholder wanting a static report, a colleague wanting the raw numbers, or a quick paste into a presentation.

7.6.2 Print to PDF

File, print to PDF asks whether we want the entire workbook or only the active sheet.

7.6.3 Export as Image

When the deliverable is a picture — an email, a report, a slide — worksheet, export, export as image saves the current sheet as an image file. The dialog asks whether to include all the elements on the sheet; confirming produces a standalone image of exactly what the sheet shows.

7.6.4 Export Data and Crosstab

Sometimes someone says, "give me the raw data, I will do my own numbers." Worksheet, export, data saves the underlying data as an MDB file — the Microsoft database format. Alternatively, export crosstab sends the sheet's aggregated numbers to Excel as a region-wise, category-wise table, so the recipient gets the crosstab we see on screen and can build their own calculations on top of it. The demo's crosstab came out as exactly the row-and-column numbers the sheet displayed.

7.6.5 Copy to the Clipboard

The clipboard route is the fastest. The demo chart was a region-wise sales view, colored by category, with category and sales shown as labels — the instructor built it in a few clicks: put region on columns (had it gone on rows, the regions would run vertically), put sales on the axis, then drag category onto color so each region's bar splits by category, and put category and sales on labels to show the numbers.

Visual intuition: the copied chart reads as three side-by-side vertical bars, one per region, each bar split into stacked color segments with numbers on them — east is the tallest at 670k, central follows at 500k with its technology segment (170) and office supplies segment (167) labeled on the chart. The takeaway in one glance: the chart answers "which region sells the most, and what mix inside it?" without a single extra click.

Real-world & domain connection: copy-image-to-clipboard (Ctrl+V into PowerPoint) is a standard quick-report workflow for sharing chart snapshots in meetings, while the crosstab-to-Excel and data-to-MDB routes are everyday reporting handoffs — analysts hand raw numbers to teams that do their own analysis, and the fit-settings habit keeps exported PDFs presentation-ready for stakeholders.

7.7 Metadata Management

7.7.1 Hiding and Unhiding Fields

The metadata pane holds every field in the data source, and part of managing it is keeping the pane tidy. Right-click a field and choose hide, and it disappears from the pane. Hidden fields are not gone — the show hidden fields option brings them back as grayed-out entries, and a right-click unhides them for good. This is useful when a data source has dozens of fields but a project only needs a handful.

7.7.2 Renaming Fields

Field names can be changed without touching the source data. Rename by single-clicking the field name, or through the small arrow at the bottom edge of the field chip. A clearer name — for example renaming a cryptic source column to something the business understands — makes every subsequent sheet easier to read.

7.7.3 Hierarchies

Hierarchies were part of the recap, and the demo builds one live. Drag one field over another when the fields are logically related — for example dragging city over country — and Tableau nests them into a hierarchy; more fields can be added under the hierarchy, and the sequence can be changed at any time. A hierarchy is built for drill-down: pull the hierarchy onto a shelf, and every related field comes along in one drag instead of being dragged separately, then we zoom into the data level by level — country, then region, then state, then city. Location is a hierarchy name, not a field: it will never appear in the source table, only as the grouping that owns the fields underneath it. Hierarchy members carry a distinct icon in the pane.

7.7.4 Folders and Searching

Folders organize fields into named groups in the pane. The key setup step: before creating a folder, first group the field listing by folders (the menu option that changes the pane's sort). Then right-click, create folder, give it a name, and drag fields under it. Folders shrink the visible list, and the search box at the top of the pane finds any field instantly even when the pane is crowded.

7.7.5 Calculated Fields

A calculated field is a new field we define with a formula over the existing fields. Right-click anywhere in the pane, choose create calculated field, and the editor opens. The left-hand list shows the fields, and the function list is complete — every function comes with its syntax, a plain-language description of what it does, and the parameters it needs, so the editor doubles as documentation. Aggregations like average, minimum, and maximum are there; string functions can convert a passed string into its ASCII codes; date functions support date addition, date difference, a date parser, and a date day function that returns the specific day for any date passed to it. The editor validates the syntax live and shows an error when the formula is wrong, so a bad formula has to be fixed before it can be used.

The demo defines the cost price: take sales and subtract profit.

$$\text{Cost price}=\text{Sales}-\text{Profit}$$

The verbal description of the formula is simple: "the sum of the difference between the sales and the profit." Per record, the difference gives the cost price for that product id — placed product-wise on a sheet, Tableau shows the sum of the difference for every product id at record level. Once created, the calculated field appears in the field list and behaves like any regular field inside further calculations and reports.

7.7.6 Data Preparation: At the Source or in Tableau

There are two philosophies of preparation, and both are valid. Option one: prepare the data at the source before it ever reaches Tableau — do all the calculations in the database or the ETL tool, and use Tableau purely for drag-and-drop. Option two: bring the data in and handle the logic inside Tableau with calculated fields and the functions above. Real projects usually do some of both — you cannot always take data preparation to its logical end at the source, so Tableau's calculated fields cover the rest. Fields can be added, edited, and deleted freely, and the values flow into sheets like any source field.

Real-world & domain connection: the source-versus-Tableau choice mirrors how analytics teams actually split work — data warehouses and ETL pipelines (Extract, Transform, Load) compute the heavy, company-wide logic once for everyone, while analysts keep project-specific formulas like cost price as calculated fields inside Tableau so they can iterate without waiting on the warehouse team. Calculated fields are also where business logic like margins, growth rates, and day-of-week flags live in daily reporting, because the formula is documented, reusable, and shared with every sheet that references it.

7.8 Filtering the Data

7.8.1 Why Filtering Is a Dashboard Skill

So far the sheets have shown everything the drag produced, with no way to narrow it. Filtering is the mechanism for narrowing, and the instructor's framing is explicit: filters are a core component for dashboards, because dashboards must let the end user be flexible and explore on their own. "Show me only the west, compare east with west" — that is what filtering will make possible. Every technique here carries over into the dashboard sheets later.

7.8.2 The Filter Shelf and the Filter Dialog

The most direct route is the filter shelf. Drag the field we want to filter on into the filter shelf, and the filter dialog opens automatically. The dialog has four tabs — General, Wildcard, Condition, and Top — and we are not forced to use them all: the summary at the bottom tells us exactly what combination is active, and each tab handles a different style of rule.

7.8.3 The General Tab

The General tab is the default. It lists the field's values with checkboxes: select all, select none, pick individual values, or invert the selection with exclude.

7.8.4 The Wildcard Tab

Wildcard filtering matches values by pattern instead of picking them one by one: contains, starts with, ends with, or exactly matches, with a box to type the pattern.

7.8.5 The Top and Condition Tabs

The Top tab limits by rank: show me the top 10 subcategories by sales, or top 5 by sales, with the ranking based on a chosen field and aggregation. The Condition tab limits by a numeric rule: for example, keep only values where sales is greater than or equal to zero. All four tabs can be combined in one filter — select values on General, pattern-match on Wildcard, keep the ones over zero on Condition, and cap the list at the top 10 by sales on Top — and the summary line lists every rule that is in force.

7.8.6 Filtering by Date

Date fields get their own treatment. Dropping order date onto the filter shelf offers several date-specific modes.

7.8.7 Interactive Filters: Show Filter

The filter shelf route works, but every change happens inside a dialog, which is a developer-mode workflow. For the end user, right-click any field and choose show filter instead: the field appears as a filter control on the right-hand side of the sheet, fully interactive. No dialog, no navigation — click values and the view updates. The control's style is configurable from the same menu: single value list (radio buttons, one at a time), single value dropdown, multiple value dropdown, slider (best for date ranges and number ranges), wildcard match, and the checkbox list.

7.8.8 Linking Filters: Show Only Relevant Values

With two filters on the sheet — category at the top and subcategory below — the pair can be linked. Right-click the lower filter and tick show only relevant values, and Tableau automatically filters the subcategory list to whatever belongs to the selected category: choosing furniture leaves only the furniture subcategories, choosing office supplies leaves only its own. The demo confirms the behavior — picking accessories only works under technology, and the two filters stay synchronized. This linking is precisely what dashboards need: one selection should filter the next, and if there is a third level, the third should follow the second.

7.8.9 Filtering by Headers

Headers filter directly on the chart itself. With subcategory-wise sales on the sheet, double-click the accessories header and everything else vanishes — only accessories remains. Removing the filter brings the full list back. For several values at once, multi-select the headers (for example accessories, copier, and storage), right-click, and choose keep only — exactly those three stay and the rest go. Any chart linked to the same field updates to the same selection. No filter shelf, no dialog: just click on the values you care about.

7.8.10 Filtering by Legends

Wherever a legend exists, it filters too. In a chart colored by category, clicking the office supplies legend entry zooms the view to office supplies only; selecting two entries and choosing keep only keeps exactly those two; choosing exclude removes the clicked entries and keeps the rest. The demo does all three against the category legend — click, keep only, exclude — and clears back to full data with the remove option. Legends behave like header filters for the color dimension.

7.8.11 Summary of Filtering

Five routes, one goal. Filter shelf: drag the field up and pick values in the dialog. Interactive filters: right-click, show filter, and the control lives on the sheet with multiple styles. Show only relevant values: link stacked filters so one updates the next. Headers: double-click one value or multi-select and keep only. Legends: click, keep only, or exclude on the color legend. All five feed the same end: the user zooms into what interests them, hides what does not, and makes the decision making interesting. That is the interactiveness that dashboards are built to deliver, and each of these techniques is exactly the piece a dashboard will later assemble.

7.8.12 Exam-Focused Q&A

The session ends with a question about the exam, and the answer shapes how to study.

Real-world & domain connection: interactive filtering with show only relevant values is what makes organizational dashboards self-service — one filter cascades through every sheet, so a sales manager can drill from region to subcategory without a developer. In dashboard design terms this is the analytical-dashboard pattern: strategic dashboards simply display, while analytical dashboards hand the user the controls — filters, drill-downs, and cascading selections — so the user explores causes, not just snapshots.

Exam Guidance Summary

The session's exam-relevant material, gathered in one place.

The EC1 quiz — five marks, fixed deadline

• The EC1 quiz is enabled and carries five marks with roughly 20 or 25 questions. The system mail went out, and the last date is 29 February — check with classmates so nobody misses it, because late completion triggers a lot of admin work.

The final exam — conceptual, not practical

• The final exam is theoretical, not practical. Question types are conceptual and case-study based: choose the right visualization for a scenario, state the key things for dashboarding, explain what to avoid, and list the prerequisites for a given case. Preparation means understanding concepts and being able to argue a visualization choice, not memorizing clicks.

Quiz answers worth keeping in mind

Dashboard case study

• Expect filtering to matter in the dashboard case study: the five routes (filter shelf, interactive filters, relevant values linking, headers, legends) and the idea that a dashboard should let the user explore on their own — one selection cascades, every chart updates together, and the end user drives the analysis without a developer.

Key Industry Applications

The real-world patterns from this session, in one place.

• Tableau acquisition in the field: Tableau Desktop's two acquisition paths matter in practice — a 14-day trial for quick evaluation and the one-year academic license for students — and Tableau Server is how enterprises let one or two developers publish for the whole organization while everyone else consumes the dashboards.
• Live versus extract in real workloads: live connections are used where figures must be on the fly (real-time dashboards), while extracts — a one-time local dump — are the standard choice for analysis workloads over huge data, because analysis copies avoid network latency.
• The data interpreter against messy exports: the data interpreter handles messy source files such as merged-cell Excel sheets and PDFs, which is a constant real-world pain when raw exports come from other departments.
• Segment sets in reporting: the metro set example — a set of Delhi, Mumbai, Kolkata, and Bangalore in state-wise GDP data — shows the pattern of business segment sets, which are used to focus comparisons and color coding in reporting.
• Parameters as user-driven controls: parameters are the mechanism behind user-driven report controls — the same idea as passing variables into code — and they appear in dashboards as the top-N selectors that business users touch daily.
• Reporting handoffs: combining fields into a single key, and exporting crosstabs to Excel or data to MDB, are everyday reporting handoffs: analysts hand raw numbers to teams that do their own analysis.
• Self-service dashboards: interactive filtering with show only relevant values is what makes organizational dashboards self-service — one filter cascades through every sheet, so a sales manager can drill from region to subcategory without a developer.
• Quick-share workflow: copy-image-to-clipboard (Ctrl+V into PowerPoint) is a standard quick-report workflow for sharing chart snapshots in meetings.