{
  "schema": "vedokrok.public-item.v1",
  "release_id": "VEDOKROK-SEL-5d86e1b23401e578",
  "url": "/knowledge/check-what-power-query-profiles",
  "id": "MHC-D-RESEARCH-9726",
  "version": "0.1.0",
  "title": "Check what Power Query profiles",
  "summary": "A clean preview can leave rows unchecked.",
  "kind": "checklist",
  "body": "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.",
  "limits": [
    "The column-quality labels do not replace checks of required fields, allowed codes or factual accuracy."
  ],
  "topics": [
    "critical-thinking"
  ],
  "intents": [],
  "source_ids": [
    "ms-profile",
    "ms-profile-scope"
  ],
  "evidence": [
    {
      "claim": "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.",
      "source_id": "ms-profile",
      "role": "supports",
      "note": "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.\nSource 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.\nAgent 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.",
      "locator": "Default profiling scope note and Column distribution definitions"
    },
    {
      "claim": "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.",
      "source_id": "ms-profile-scope",
      "role": "supports",
      "note": "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.\nSource 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.\nAgent 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.",
      "locator": "Filter data early to improve performance; Use a data subset while developing a query"
    },
    {
      "claim": "Power Query Column quality displays valid, error, empty, unknown and unexpected-error categories for values in the profiled rows.",
      "source_id": "ms-profile",
      "role": "supports",
      "note": "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.\nSource 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.\nAgent 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.",
      "locator": "Column quality, list of five categories and percentage display"
    }
  ],
  "use_when": [
    "Power Query shows no empty values or errors, but you need to check the source table."
  ],
  "avoid_when": [
    "The column-quality labels do not replace checks of required fields, allowed codes or factual accuracy."
  ],
  "checklist": [
    "Check that the query includes the records needed for the decision.",
    "Select the needed profiling scope and record it with the result."
  ],
  "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": "Record the query, relevant filters or row limits, and whether the profile covers its first 1,000 rows or its entire result.",
  "published_at": "2026-11-12T18:37:40Z",
  "review": {
    "kind": "agent",
    "label": "Agent editorial and scoped source review",
    "reviewed_at": "2026-11-12T18:37:40Z"
  },
  "knowledge_origin": {
    "release_id": "MHC-RPUB-20261112-20287590",
    "corpus_commit": "20287590ddd3999b7492df232822b6a0f7d114b1",
    "manifest_sha256": "2a987660d12de0ce2bde77a421424f7762af1ff77872ef41093fecc33db74a95",
    "projection_sha256": "2807da39bbe6a3dee2db32a76675ac5185f5a33e8b0a5cdd0c22a4731f3378a0",
    "published_at": "2026-11-12T18:37:40Z"
  },
  "editorial_overlay": null,
  "editorial": null,
  "notices": [],
  "sources": [
    {
      "id": "ms-profile",
      "title": "Using the data profiling tools - Power Query",
      "url": "https://learn.microsoft.com/en-us/power-query/data-profiling-tools"
    },
    {
      "id": "ms-profile-scope",
      "title": "Best practices when working with Power Query",
      "url": "https://learn.microsoft.com/en-us/power-query/best-practices"
    }
  ],
  "relations": [
    {
      "from": "MHC-D-RESEARCH-9726",
      "to": "MHC-D-RESEARCH-9731",
      "type": "useful_with",
      "url": "/knowledge/publish-the-limits-with-the-data-extract"
    }
  ],
  "collections": [
    {
      "id": "RC-MHC-UNION-DATA-JOINS-QUALITY-DIAGNOSTICS-2026",
      "title": "Diagnose data joins and quality before trusting a report",
      "url": "/collections/diagnose-data-joins-and-quality-before-trusting-a-report"
    }
  ],
  "topic_hubs": [
    {
      "id": "critical-thinking",
      "title": "Critical thinking and evidence",
      "url": "/topics/critical-thinking"
    }
  ],
  "solution_packs": []
}
