Identifying Patterns and Trends

Introduction

This lesson completes the domain Visualize and analyze the data (25–30% of the PL-300 skills measured, outline dated April 20, 2026). Under "Identify patterns and trends" the official outline covers: using the Analyze feature in Power BI (such as Explain the increase/decrease), using grouping and binning, using clustering to identify segments, using AI visuals (key influencers, decomposition tree, anomaly detection, smart narrative, Q&A), using the Analytics pane (reference lines, trend lines, forecast), and using Python and R visuals. The exam describes a business question ("why did revenue drop?", "which customers behave alike?", "what will sales be next quarter?") and asks which feature answers it. Microsoft does not publish the number of questions or the question-type mix; OnLevelUp mock exams use a 50-question practice length and an 80% practice target, neither of which is official nor equal to the 700/1000 passing score.

After this lesson you will be able to pick the analysis feature that fits a question, configure the Analytics pane, group and bin data, interpret key influencers and decomposition trees, and recognise the limits and prerequisites of each feature.

Learning objectives

• Add reference lines, trend lines, forecasts, error bars and percentiles from the Analytics pane.
• Group and bin values, and use clustering on a scatter chart.
• Configure key influencers and a decomposition tree and interpret their output.
• Detect anomalies in a line chart and explain them.
• Use Explain the increase and the narrative visuals.
• Decide when a Python or R visual is needed and know its limits.

1. The Analytics pane

The Analytics pane (magnifying-glass icon beside Format) adds analytical overlays to supported visuals (mostly line, bar, column, area and scatter).

Forecast details that appear in exam scenarios: the visual needs a time-series axis (date type, continuous) and one value; you can ignore the last N points to test the forecast (hold-back), set seasonality (number of points per cycle, such as 12 for monthly data with a yearly cycle), and adjust the confidence interval (default 95%). The forecast is not available for visuals that use a legend with several series, and it is not supported with a categorical axis. Reference lines apply to the visual; they do not change the model.

Worked example: forecast and target line

Scenario. A line chart shows 36 months of subscription revenue. The CFO wants the next six months projected with seasonality, to test the forecast against the last three known months, and to see the monthly target of 450 k€ as a horizontal line.

Step 1. Make sure the X-axis uses DimDate[Date] as a continuous date (not the Year/Quarter/Month hierarchy) and set Revenue on the Y-axis.

Step 2. Analytics pane → Forecast → On. Set Forecast length to 6 points, Ignore last 3 points, Seasonality 12, Confidence interval 95%.

Step 3. Analytics pane → Constant line → value 450000, title "Target".

Step 4. Compare the forecast for the three held-back months with the actual values to judge accuracy before sharing.

Why not the alternatives. A calculated column cannot forecast. A measure with moving average smooths past data but does not extrapolate. With the date hierarchy on the axis, forecast stays greyed out because the axis is categorical.

2. Grouping, binning, and clustering

Grouping combines categories into custom groups. Right-click a field in a visual → New group, select values and Group. It creates a group column (in the model) and keeps an Other bucket for ungrouped values. For example, group 40 countries into Sales Territories. Better for few manual groups; for large mappings use a lookup table.

Binning divides numeric or date values into equal-sized bins: right-click a numeric field → New group → Bin with a bin size or a bin count. Examples: age in 10-year bins, order value in 50-€ bins, date in months. Binning plus a count visual builds a histogram. A bin field is a calculated group column stored in the model.

Clustering finds natural groups of similar points in a scatter chart: Visual header → More options → Automatically find clusters. Choose the number of clusters (or leave automatic) and name the field. Power BI adds a categorical field you can use as a legend or slicer. It requires at least two numeric measures or dimensions on the X and Y axes, and a detail field. It is meant for exploring segments, not for strict statistical modelling.

Differences: grouping and binning organize data you already have; clustering discovers segments from numeric behaviour.

3. AI visuals: key influencers, decomposition tree, Q&A, smart narrative

Key influencers. Answers "what drives this metric to be high/low or this category to occur?". Fields:

• Analyze: the metric or category to explain (for instance Churned = Yes, or Rating).
• Explain by: candidate factors, which can be categorical or numeric.
• Expand by: the unit of analysis for aggregated measures (such as Customer ID).

Output: Key influencers tab ranks factors ("when Contract = Month-to-month, the likelihood of churn is 2.3x higher"). The Top segments tab shows combinations of factors with the highest rate. For a numeric target, it reports how the average changes (for example, "when tenure is under 12 months, the average rating decreases by 0.8"). Limits: needs enough rows, the analyzed field must be a column (not a measure) in the table, DirectQuery and some live sources have restrictions, and results are correlations, not proof of causation.

Decomposition tree. Interactive visual that breaks a measure down across dimensions in any order. Fields: Analyze (a measure) and Explain by (dimensions). Readers choose each next dimension, or use High value / Low value (AI splits) to pick the dimension with the highest or lowest value. Useful for ad hoc root-cause analysis: revenue by region, then by category, then by channel.

Q&A visual. Readers type questions; Power BI builds a visual. It depends on field names and synonyms in the model (Q&A setup, suggested questions). Microsoft has announced that the legacy Q&A experience will be deprecated in December 2026, so rely on it carefully and know Copilot as the successor for natural-language questions where licensed.

Smart narrative. A visual that writes dynamic text summaries of visuals on the page or report (key takeaways, trends, max/min). The text updates with filters and can be edited and customized with dynamic values from fields or measures. The newer Copilot narrative visual (see lesson 8) produces AI-written summaries and needs Copilot availability on the capacity and tenant.

Explain the increase/decrease (Analyze). Right-click a data point on a line or column chart → Analyze → Explain the increase (or decrease) when a point rises or falls compared with the previous one. Power BI tests dimensions in the model and shows visuals (waterfall, scatter, column) listing the factors with the largest contribution. Requirements: measures that sum or average, a chart with date or categorical axis, and not all visual types support it. Use it for a quick explanation on a spike without building a decomposition manually.

Worked example: why does churn happen?

Scenario. A telecom table Customers has CustomerID, Contract, Tenure, InternetService, MonthlyCharge, and Churned (Yes/No). The retention team asks: which factors increase churn? and which customer segments churn most?

Step 1. Add a Key influencers visual. Drag Churned to Analyze, choose "What influences Churned to be Yes?".

Step 2. Drag Contract, Tenure, InternetService, MonthlyCharge to Explain by. Leave Expand by empty because each row is a customer.

Step 3. Read the Key influencers tab: "Contract is Month-to-month → churn 3.1x more likely". Open Top segments to see "month-to-month, fibre, tenure under 12" with 62% churn versus 27% average.

Step 4. Add a decomposition tree with Churn count, then Contract, Region, to explore a chosen path.

Why the alternatives are worse. A scatter chart would need manual hypotheses. Clustering groups customers by numeric similarity but does not explain a target. A trend line only fits two numeric variables.

4. Anomaly detection and statistical visuals

Anomaly detection works on a line chart with a date axis. In the Analytics pane → Find anomalies, set Sensitivity (higher shows more points). Power BI marks anomalies with a symbol and, when a point is selected, shows possible explanations (fields in the model that contributed). You can add expected range shading. Limits: supported only on line charts with time series data in the Axis; it cannot be combined with a forecast on the same visual; the legend must not have multiple series.

Python and R visuals. Enable the scripting runtime in Desktop options. You drag fields into the visual's values; Power BI passes them as a data frame named dataset and the script draws an image with matplotlib, seaborn, ggplot2, etc. Characteristics:

• Runs in Desktop with a local Python/R install; in the service they run in a sandbox with a set of supported packages.
• Output is a static image: no cross-filtering from clicking the image, and tooltips are not interactive.
• Input is limited (rows are deduplicated; a maximum number of rows, 150 000, is used).
• Use when no built-in visual provides the analysis (for example a violin plot, a correlation matrix) and the audience accepts a static image.

# dataset has columns: Age, MonthlyCharge
import seaborn as sns, matplotlib.pyplot as plt
sns.regplot(data=dataset, x="Age", y="MonthlyCharge")
plt.show()

Alternatives before choosing a script visual: a custom visual from AppSource (e.g. box and whisker) is interactive and needs no runtime.

Statistical helpers inside the Desktop: Quick measure templates (such as "Average per category", "Rank", "Correlation coefficient", "Weighted average"), Show data as a table to check numbers, and the Performance analyzer for speed (lesson 7).

5. Choosing the feature: decision table

Worked example: pick the tool, justify, and discard the others

Scenario. A grocery chain sees online orders spike on 14 March. Analysts must (1) find out whether it is a true anomaly, (2) learn what drove it, and (3) predict next March's volume.

Step 1. On a line chart of daily orders, turn on Find anomalies. Select the 14 March marker to read the explanations (for example promotion SPRING25 and region North).

Step 2. To drill further, right-click the point and use Explain the increase, or build a decomposition tree from order count by channel, region, and promotion.

Step 3. For next March, use Forecast with seasonality 365 for daily data over at least two full years, remembering that anomaly detection and forecast cannot be on the same visual, so duplicate the visual.

Why others are worse. Key influencers needs a target field to classify and does not detect time anomalies. Clustering groups points, not dates. A Python visual might do it but is static and slower.

6. Pitfalls and exam tips

• Forecast greyed out: the axis is not a continuous date, or there are several series in the legend.
• Anomaly detection and forecast cannot be used on the same visual.
• Key influencers shows correlation, not causation; the analyzed field is a column.
• Decomposition tree is for exploration with reader control; key influencers is for statistical ranking of drivers.
• Clustering needs a scatter chart (two numeric values and a detail field).
• Binning needs a numeric or date field; grouping works on categories.
• Python/R visuals are static images: no cross-filtering from the image, and the runtime must be installed in Desktop.
• Q&A is being deprecated (announced for December 2026): in new questions the AI answer is Copilot, or the decomposition tree or key influencers for analysis.
• Exam tip: map verbs to features: predict → forecast; unusual → anomaly; why/what drives → key influencers; break down → decomposition tree; similar groups → clustering; summarize in words → narrative.

7. Mini case study

Situation. A subscription company with 400 000 customers asks the analyst for: (a) the main factors behind cancellations; (b) six-month forecast of monthly recurring revenue with a visible target of 5 M€; (c) a flag on days where sign-ups jump unexpectedly; (d) customer segments by monthly spend and tenure for marketing; (e) a histogram of customer lifetime value in 100-€ steps; (f) an executive page with a text summary that updates with filters.

Question. Which features answer each request?

Solution, commented.

1. (a) Key influencers with Cancelled in Analyze and plan, tenure, country and support tickets in Explain by.
2. (b) Forecast on a line chart with continuous dates, seasonality 12, plus a constant line at 5,000,000.
3. (c) Find anomalies on a separate line chart of daily sign-ups, because it cannot coexist with a forecast on the same visual.
4. (d) Clustering on a scatter chart with tenure on X, spend on Y and customer as details.
5. (e) Binning CLV with bin size 100, then a column chart of the customer count.
6. (f) Smart narrative (or Copilot narrative if licensed) on the summary page.

Why not the alternatives. A decomposition tree helps exploration for (a), but the request is to rank the factors. A calculated column for the histogram bins would work but the built-in bin is faster to maintain. A Python script for clustering would be static.

Key terms

• Analytics pane: overlay tools (lines, trend, forecast, anomalies) on visuals.
• Forecast: time-series prediction with a confidence band.
• Binning: grouping numeric or date values into equal intervals.
• Clustering: automatic grouping of similar points in a scatter chart.
• Key influencers: AI visual ranking factors that drive a metric.
• Decomposition tree: visual breaking down a measure by dimensions chosen by the reader.
• Anomaly detection: automatic marking of unusual points on a time-series line.
• Smart narrative: auto-generated, editable text summary.
• Seasonality: the number of points in a repeating cycle.

Summary checklist

• I can add constant, average, percentile and trend lines, and configure a forecast.
• I know why a forecast may be unavailable.
• I can group, bin and cluster data.
• I can set up key influencers and a decomposition tree and interpret them.
• I can enable anomaly detection and know its limits.
• I know what Python and R visuals can and cannot do.
• I can map a business question to the correct analysis feature.

Official sources

• Study guide for Exam PL-300: https://learn.microsoft.com/en-us/credentials/certifications/resources/study-guides/pl-300 (opens in a new tab)
• Analytics pane in Power BI Desktop: https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-analytics-pane (opens in a new tab)
• Key influencers visualizations: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-influencers (opens in a new tab)
• Anomaly detection: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-anomaly-detection (opens in a new tab)
• Decomposition tree: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-decomposition-tree (opens in a new tab)
• What's new in Power BI: https://learn.microsoft.com/en-us/power-bi/fundamentals/whats-new (opens in a new tab)