Checklist

Check what Power Query profiles

A clean preview can leave rows unchecked.

About 1 min read

Before you use it

Use when
  • Power Query shows no empty values or errors, but you need to check the source table.

Keep this limit in mind

  • The column-quality labels do not replace checks of required fields, allowed codes or factual accuracy.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Checklist

  • Check that the query includes the records needed for the decision.
  • Select the needed profiling scope and record it with the result.

Why it matters

By default, Power Query profiles the first 1,000 rows. Use the profiling message at the lower left of the editor to switch to the entire dataset when needed. Check the query’s filters and row limits too: this setting does not restore rows already excluded from the query.

An example

In this example, a query keeps the first 1,000 of 12,000 source rows. Switching to entire-dataset profiling still leaves a blank country code in source row 12,000 outside the query.

Check your result

Record the query, relevant filters or row limits, and whether the profile covers its first 1,000 rows or its entire result.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingCheck what Power Query profiles

Evidence and sources
Supports

Power Query data profiling uses the first 1,000 rows by default and offers entire-dataset profiling. In Column distribution, distinct counts different values; unique counts values occurring once in the profiled column.

Claim limit: Tool-specific documented behavior, not a universal definition of unique or an empirical test of Power Query. Counts from a restricted query or partial profile do not establish source-wide coverage or a stable business identifier. Source reading history: selected_passages; 2026-10-11; Default profiling scope note, Column quality labels and Column distribution definitions. Official page was opened on 2026-10-10 and identified sections inspected. This verifies a narrow reference basis, not the effectiveness or completeness of independently drafted practice steps. On 2026-10-11 those sections were read again for cards 9726/9727. The content was readable despite the page’s generic authorization banner. No application or connector was executed. Agent release review: PostgreSQL 18 table expressions, NULL comparisons and aggregates, the UK Government Data Quality Framework and Microsoft Power Query profiling documentation were checked at the cited sections. The original examples and scope limits remain attached.

Using the data profiling tools - Power Query · Default profiling scope note and Column distribution definitions

Supports

Power Query filters reduce the rows available to later transformations and the preview; a Keep First Rows step restricts the query until it is removed.

Claim limit: The card’s conclusion about entire-dataset profiling combines this documented query restriction with the separate profiling-scope documentation. It is a bounded interpretation, not Power Query runtime verification or a reason to remove legitimate filters. Source reading history: selected_passages; 2026-10-11; Filter data early to improve performance; Use a data subset while developing a query. Sections were opened and read on 2026-10-11: filtering restricts later rows and preview, and Keep First Rows should be removed when the completed query needs the full dataset. Selected documentation passages, not application execution or independent acceptance. Agent release review: PostgreSQL 18 table expressions, NULL comparisons and aggregates, the UK Government Data Quality Framework and Microsoft Power Query profiling documentation were checked at the cited sections. The original examples and scope limits remain attached.

Best practices when working with Power Query · Filter data early to improve performance; Use a data subset while developing a query

Supports

Power Query Column quality displays valid, error, empty, unknown and unexpected-error categories for values in the profiled rows.

Claim limit: These are profiling labels. The selected documentation does not establish that the green category checks every business rule or whether a value corresponds to reality. Source reading history: selected_passages; 2026-10-11; Default profiling scope note, Column quality labels and Column distribution definitions. Official page was opened on 2026-10-10 and identified sections inspected. This verifies a narrow reference basis, not the effectiveness or completeness of independently drafted practice steps. On 2026-10-11 those sections were read again for cards 9726/9727. The content was readable despite the page’s generic authorization banner. No application or connector was executed. Agent release review: PostgreSQL 18 table expressions, NULL comparisons and aggregates, the UK Government Data Quality Framework and Microsoft Power Query profiling documentation were checked at the cited sections. The original examples and scope limits remain attached.

Using the data profiling tools - Power Query · Column quality, list of five categories and percentage display

All sources (2)
Edition and review

Version 0.1.0 · Published

Edition checked · 2026-11-12

Read this idea as JSON · Release details