EPC Group - Enterprise Microsoft AI, SharePoint, Power BI, and Azure Consulting
G2 High Performer Summer 2025, Momentum Leader Spring 2025, Leader Winter 2025, Leader Spring 2026
BlogContact
Ready to transform your Microsoft environment?Get started today
(888) 381-9725Get Free Consultation
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌

EPC Group

Enterprise Microsoft consulting with 29 years serving Fortune 500 companies.

(888) 381-9725
contact@epcgroup.net
4900 Woodway Drive - Suite 830
Houston, TX 77056

Follow Us

Solutions

  • All Services
  • Microsoft 365 Consulting
  • AI Governance
  • Azure AI Consulting
  • Cloud Migration
  • Microsoft Copilot
  • Data Governance
  • Microsoft Fabric
  • vCIO / vCAIO Services
  • Large-Scale Migrations
  • SharePoint Development

Industries

  • All Industries
  • Healthcare IT
  • Financial Services
  • Government
  • Education
  • Teams vs Slack

Power BI

  • Case Studies
  • 24/7 Emergency Support
  • Dashboard Guide
  • Gateway Setup
  • Premium Features
  • Lookup Functions
  • Power Pivot vs BI
  • Treemaps Guide
  • Dataverse
  • Power BI Consulting

Company

  • About Us
  • Our History
  • Microsoft Gold Partner
  • Case Studies
  • Testimonials
  • Blog
  • Resources
  • All Guides & Articles
  • Video Library
  • Client Reviews
  • Contact
  • Schedule a consultation

Microsoft Teams

  • Teams Questions
  • Teams Healthcare
  • Task Management
  • PSTN Calling
  • Enable Dial Pad

Azure & SharePoint

  • Azure Databricks
  • Azure DevOps
  • Azure Synapse
  • SharePoint MySites
  • SharePoint ECM
  • SharePoint vs M-Files

Comparisons

  • M365 vs Google
  • Databricks vs Dataproc
  • Dynamics vs SAP
  • Intune vs SCCM
  • Power BI vs MicroStrategy

Legal

  • Sitemap
  • Privacy Policy
  • Terms
  • Cookies

About EPC Group

EPC Group is a Microsoft consulting firm founded in 1997 (originally Enterprise Project Consulting, renamed EPC Group in 2005). 29 years of enterprise Microsoft consulting experience. Microsoft Gold Partner from 2003–2022 — the oldest Microsoft Gold Partner in North America — and currently a Microsoft Solutions Partner with six designations: Data & AI, Modern Work, Infrastructure, Security, Digital & App Innovation, and Business Applications.

Headquartered at 4900 Woodway Drive, Suite 830, Houston, TX 77056. Public clients include NASA, FBI, Federal Reserve, Pentagon, United Airlines, PepsiCo, Nike, and Northrop Grumman. 6,500+ SharePoint implementations, 1,500+ Power BI deployments, 500+ Microsoft Fabric implementations, 70+ Fortune 500 organizations served, 11,000+ enterprise engagements, 200+ Microsoft Power BI and Microsoft 365 consultants on staff.

About Errin O'Connor

Errin O'Connor is the Founder, CEO, and Chief AI Architect of EPC Group. Microsoft MVP for multiple years starting 2002–2003. 4× Microsoft Press bestselling author of Windows SharePoint Services 3.0 Inside Out (MS Press 2007), Microsoft SharePoint Foundation 2010 Inside Out (MS Press 2011), SharePoint 2013 Field Guide (Sams/Pearson 2014), and Microsoft Power BI Dashboards Step by Step (MS Press 2018).

Original SharePoint Beta Team member (Project Tahoe). Original Power BI Beta Team member (Project Crescent). FedRAMP framework contributor. Worked with U.S. CIO Vivek Kundra on the Obama administration's 25-Point Plan to reform federal IT, and with NASA CIO Chris Kemp as Lead Architect on the NASA Nebula Cloud project. Speaker at Microsoft Ignite, SharePoint Conference, KMWorld, and DATAVERSITY.

© 2026 EPC Group. All rights reserved. Microsoft, SharePoint, Power BI, Azure, Microsoft 365, Microsoft Copilot, Microsoft Fabric, and Microsoft Dynamics 365 are trademarks of the Microsoft group of companies.

How To Create A Table From Another Table In Power BI - EPC Group enterprise consulting

How To Create A Table From Another Table In Power BI

Expert insights on creating tables from other tables in Power BI from EPC Group's enterprise Microsoft consultants.

Back to Blog

How To Create A Table From Another Table In Power BI

Errin O'Connor
December 2025
8 min read

Creating a new table from an existing table in Power BI is a core data modeling technique that enables you to build summary tables, lookup tables, filtered subsets, and calculated reference tables without duplicating source data imports. DAX (Data Analysis Expressions) provides several powerful functions for this purpose, including SELECTCOLUMNS, SUMMARIZE, ADDCOLUMNS, FILTER, and DATATABLE. This guide covers each method with practical examples for enterprise reporting scenarios.

Understanding Calculated Tables in Power BI

Calculated tables are tables created using DAX expressions that derive their data from other tables in your model. They are computed during data refresh and stored in memory alongside your imported tables.

  • When to use calculated tables — Creating lookup/dimension tables, building role-playing dimension tables, generating date tables, creating filtered subsets for specific report pages, and building summary tables for performance optimization
  • When to avoid calculated tables — When the transformation can be done in Power Query (M language) during data load, which is generally more efficient for large datasets
  • Memory impact — Calculated tables consume memory in the data model; use them judiciously in large models with millions of rows
  • Refresh behavior — Calculated tables recalculate during every data refresh, so their content stays in sync with source data

Method 1: SELECTCOLUMNS — Create a Table with Specific Columns

SELECTCOLUMNS creates a new table by selecting and optionally renaming columns from an existing table. This is the most common method for creating a subset table.

ProductLookup =
SELECTCOLUMNS(
    Products,
    "Product ID", Products[ProductID],
    "Product Name", Products[ProductName],
    "Category", Products[Category]
)

  • Creates a new table with only the specified columns
  • Column names can be renamed in the output by providing new name strings
  • Useful for creating dimension/lookup tables from denormalized fact tables
  • Combine with DISTINCT or VALUES to remove duplicate rows

Method 2: SUMMARIZE — Create Aggregated Summary Tables

SUMMARIZE groups data by specified columns and can include aggregated measures, making it ideal for creating summary and rollup tables.

SalesSummary =
ADDCOLUMNS(
    SUMMARIZE(Sales, Sales[Region], Sales[Category]),
    "Total Revenue", CALCULATE(SUM(Sales[Amount])),
    "Order Count", CALCULATE(COUNTROWS(Sales))
)

  • SUMMARIZE creates distinct groupings; ADDCOLUMNS adds calculated aggregates
  • This pattern (SUMMARIZE + ADDCOLUMNS) is the recommended approach over using SUMMARIZE with aggregation expressions directly
  • Ideal for creating executive summary tables that pre-aggregate large fact tables
  • Use ROLLUP or ROLLUPGROUP within SUMMARIZE for subtotals and grand totals

Method 3: FILTER — Create Filtered Subset Tables

FILTER creates a new table containing only rows that meet specified conditions, useful for creating focused tables for specific business units, time periods, or status categories.

HighValueOrders =
FILTER(
    Orders,
    Orders[Amount] > 10000
    && Orders[Status] = "Completed"
)

  • Creates a table with all columns from the source but only matching rows
  • Multiple conditions can be combined with && (AND) and || (OR)
  • Useful for creating role-based views or department-specific data subsets
  • Combine with SELECTCOLUMNS to both filter rows and select specific columns

Method 4: DISTINCT and VALUES — Create Unique Value Tables

DISTINCT and VALUES extract unique values from a column to create lookup or reference tables.

UniqueCategories = DISTINCT(Products[Category])

RegionLookup =
DISTINCT(
    SELECTCOLUMNS(
        Sales,
        "Region", Sales[Region],
        "Country", Sales[Country]
    )
)

  • DISTINCT returns unique rows from a table expression (excludes blanks for single columns)
  • VALUES returns unique values including the blank row that represents missing relationships
  • Combine with SELECTCOLUMNS to create multi-column dimension tables from denormalized sources
  • Essential for star schema modeling where dimension tables need to be extracted from flat tables

Method 5: Power Query (Recommended for Large Datasets)

For large-scale data modeling, creating derived tables in Power Query (M language) during data load is generally more efficient than DAX calculated tables, as transformations happen during refresh rather than consuming in-memory resources.

  • Reference queries — Right-click a query in Power Query and select "Reference" to create a new query based on the existing one
  • Duplicate queries — Create an independent copy of a query that can be modified without affecting the original
  • Group By — Use the Group By transformation to create summary tables during data load
  • Remove Columns — Use Remove Other Columns to create lean lookup tables from wide fact tables
  • Merge Queries — Join multiple queries to create combined reference tables

Why Choose EPC Group for Power BI Data Modeling

EPC Group has over 29 years of enterprise business intelligence experience, with deep specialization in Power BI data modeling and DAX optimization. As a former Microsoft Gold Partner (2003–2022, the oldest in North America) and current Microsoft Solutions Partner, our Power BI architects have designed data models for Fortune 500 companies handling billions of rows across healthcare, finance, retail, and manufacturing. Our founder, Errin O'Connor, authored the bestselling Microsoft Press book on Power BI and leads a team of certified data modeling specialists.

  • Enterprise Power BI data model architecture and star schema design
  • DAX optimization for complex calculated tables and measures
  • Power Query ETL development for large-scale data transformations
  • Composite model design with DirectQuery and Import mode
  • Performance tuning for models with billions of rows

Optimize Your Power BI Data Models

EPC Group's Power BI architects can help you design efficient data models, write optimized DAX, and build enterprise-grade reporting solutions. Contact us for a Power BI data modeling assessment.

Schedule a ConsultationCall (888) 381-9725

Frequently Asked Questions

What is the difference between a calculated table and a Power Query table?

A calculated table is created using DAX and computed in memory after data load. A Power Query table is created using M language during the data load/refresh process. Power Query tables are generally more memory-efficient because they fold transformations back to the data source when possible. Calculated tables are more convenient for DAX-based logic that references measures and the model context.

Do calculated tables affect report performance?

Calculated tables consume memory in the data model and increase refresh time since they must be recalculated during every refresh. For small to medium tables (under a few million rows), the impact is minimal. For very large derived tables, consider using Power Query instead, which can leverage query folding for better performance.

Can I create relationships with calculated tables?

Yes. Calculated tables behave like any other table in the data model. You can create relationships between calculated tables and imported tables using standard relationship configurations. This is a common pattern when extracting dimension tables from denormalized fact tables to build a proper star schema.

How do I create a date table from an existing table?

Use the CALENDAR or CALENDARAUTO function to generate a date table. CALENDARAUTO automatically scans all date columns in your model and creates a complete date range. You can then enrich the date table with ADDCOLUMNS to add Year, Quarter, Month, Week, and DayOfWeek columns. Mark the table as a Date Table in the model for proper time intelligence.

Can I use UNION or INTERSECT to combine tables?

Yes. DAX provides UNION (combines rows from two or more tables), INTERSECT (returns rows common to two tables), and EXCEPT (returns rows in the first table that are not in the second). These set operations are useful for creating consolidated tables from multiple source tables, such as merging regional sales tables or combining actual vs. budget data.

Related Resources

Continue exploring power bi insights and services

power bi

6 Reasons to Use Power Automate in Power BI

power bi

Ad Hoc Reporting

power bi

Add New Data in Power BI

power bi

Agriculture Power BI Consulting

Explore All Services

Why Organizations Choose EPC Group

EPC Group is a Houston-based Microsoft consulting firm with 29 years of enterprise implementation experience and over 10,000 successful deployments across Power BI, Microsoft Fabric, SharePoint, Azure, Microsoft 365, and Copilot. We serve organizations across all industries including Fortune 500, federal agencies, healthcare, financial services, government, manufacturing, energy, education, retail, technology, and global enterprises.

What sets EPC Group apart is our governance-first approach. Every engagement begins with a security and compliance assessment. Our team of senior architects brings hands-on delivery experience across HIPAA, SOC 2, FedRAMP, and CMMC environments. We own outcomes, not hours.

  • Fixed-fee accelerators with predictable pricing and defined deliverables
  • Senior architect engagement on every project, not rotating juniors
  • Compliance-native delivery for regulated industries
  • End-to-end coverage from strategy through 24/7 managed services
  • 11,000+ enterprise engagements refined into repeatable, risk-controlled patterns

Call (888) 381-9725 or email contact@epcgroup.net for a free assessment.

Power BI Strategy: 2026 Considerations for How To Create A Table From Another Table In Power BI

Power BI capacity sizing in 2026 starts with the F-SKU economics: F2 ($263/mo) covers small workloads with up to 4 GB of memory and roughly 30 reports, F4 ($526/mo) handles a typical mid-market deployment with semantic-model refresh windows under 10 minutes, and F64 ($5,257/mo) is the sweet spot for enterprises consuming Power BI alongside Microsoft Fabric data engineering, lakehouse storage, and real-time intelligence. Capacity right-sizing should be revisited every 90 days because Microsoft adjusts F-SKU memory allocations, paginated report performance, and Direct Lake mode availability with each major service update.

Direct Lake mode has changed the economics of enterprise Power BI in 2026: instead of importing data into Vertipaq, semantic models now query OneLake-resident Parquet files at near-Import-mode performance without the refresh-window cost. For a Fortune 500 finance organization migrating from a 30-minute Import-mode refresh, the equivalent Direct Lake model typically queries fact data in under 800 ms while removing the entire refresh-orchestration job from Azure Data Factory.

Decision factors EPC Group evaluates

  • Capacity sizing decision (F2/F4/F64+) tied to peak concurrent users and refresh window
  • Copilot grounding quality assessment of semantic-model metadata
  • Direct Lake mode adoption for Fabric-resident semantic models
  • License optimization audit (Pro vs Premium Per User vs F-SKU)
  • Row-level security via service principal authentication

See related EPC Group services at /services or schedule a discovery call at /contact.