Add New Data in Power BI Guide

Adding new data to existing datasets in Power BI is a fundamental skill for enterprise analytics, whether you are appending new rows from monthly reports, merging supplementary columns from reference tables, or connecting entirely new data sources to enrich your data model. Power BI provides multiple methods for combining data, each suited to different scenarios, from the Power Query Editor's Append and Merge operations to incremental refresh for automated, ongoing data additions.

Appending Queries: Adding New Rows

The Append operation in Power Query combines two or more tables vertically by stacking rows from one table below another. This is the correct approach when your new data has the same column structure as your existing data and you need to add additional records.

Append Two Tables - In Power BI Desktop, go to Home > Append Queries. Select the primary table and the table to append. Power Query matches columns by name and data type, adding all rows from the second table to the first.
Append Three or More Tables - Select "Append Queries as New" to create a new combined table, then choose "Three or more tables" to append multiple sources simultaneously. Ideal for consolidating monthly or regional datasets.
Handling Mismatched Columns - When tables have different column structures, Power Query creates null values for missing columns. Review the appended result and handle nulls appropriately using Replace Values, Fill Down, or conditional column transformations.
Folder-Based Append - For recurring data files (monthly CSVs, quarterly Excel reports), use the Folder connector to automatically append all files in a SharePoint library or local folder. New files added to the folder are automatically included on refresh.
Performance Tip - When appending large tables, apply filters before the append step to reduce the data volume. Filter out irrelevant rows, outdated records, or test data at the source level rather than after appending.

Merging Queries: Adding New Columns

The Merge operation in Power Query combines tables horizontally by matching rows based on a common key column, similar to SQL JOINs. Use Merge when you need to enrich existing data with additional attributes from a related table.

Merge Types - Power Query supports six join types: Left Outer (all rows from left, matching from right), Right Outer, Full Outer, Inner (only matching rows), Left Anti (left rows with no match), and Right Anti. Left Outer is the most commonly used for data enrichment.
Multi-Column Keys - When a single column doesn't uniquely identify rows, hold Ctrl and select multiple columns as the merge key (e.g., merge on both CustomerID and Date for transactional data).
Expand Merged Columns - After merging, the result includes a column with nested tables. Click the expand icon to select which columns from the merged table to include, and choose whether to use the original column name as a prefix.
Fuzzy Matching - Enable fuzzy matching in the merge dialog for scenarios where key values don't match exactly (e.g., "Microsoft Corp" vs "Microsoft Corporation"). Configure similarity threshold and transformation table for consistent matching.
Merge vs Relationship - For dimension/fact table combinations (e.g., Sales + Products), consider using Power BI relationships instead of merging in Power Query. Relationships are more memory-efficient and support complex DAX calculations across related tables.

Adding New Data Sources to Existing Models

When you need to bring in entirely new data sources (a new database, API, or file) to complement your existing Power BI data model, the process involves connecting the new source, transforming the data, and defining relationships to existing tables.

Get Data - In Power BI Desktop, click Home > Get Data and select the appropriate connector (SQL Server, Excel, Web, OData, REST API, SharePoint, etc.). Configure connection parameters and credentials.
Transform in Power Query - Before loading the new data, apply transformations in the Power Query Editor: rename columns to match your naming conventions, change data types, remove unnecessary columns, and apply filters.
Define Relationships - After loading, navigate to the Model view and create relationships between the new table and existing tables. Match on common key columns (CustomerID, ProductID, DateKey) with the appropriate cardinality (one-to-many, many-to-one).
Update DAX Measures - Review existing DAX measures to determine if they need modification to incorporate the new data source. Measures using ALL, ALLEXCEPT, or CALCULATE with specific table references may need adjustment.
Test Thoroughly - Validate that existing reports and visuals continue to work correctly after adding the new source. Check that filters, slicers, and drill-through actions behave as expected with the expanded data model.

Incremental Refresh: Automated Data Addition

Incremental refresh is the enterprise approach to continuously adding new data to Power BI datasets. Instead of refreshing the entire dataset on each cycle, incremental refresh loads only new and modified records, dramatically reducing refresh time and resource consumption.

How It Works - You define a date range parameter (e.g., load the last 3 years of data, refresh only the last 30 days). Power BI partitions the dataset by date and only refreshes partitions within the refresh window, leaving historical partitions untouched.
Configuration Steps - Create RangeStart and RangeEnd parameters in Power Query (DateTime type). Filter your date column using these parameters. In the Power BI Desktop model view, right-click the table and select "Incremental refresh" to configure the policy.
Requirements - The data source must support query folding (the ability to push filter predicates to the source). SQL Server, Azure SQL, Azure Synapse, Dataverse, and OData sources support query folding. Excel and CSV files do not.
Real-Time Data - Combine incremental refresh with DirectQuery for the latest partition to get near-real-time data. Historical partitions use Import mode for fast performance, while the current partition queries the source directly.
Licensing - Incremental refresh is available in Power BI Pro (with limitations) and fully featured in Premium Per User and Premium Per Capacity. Premium supports up to 48 refreshes per day and larger dataset sizes.

Managing Data Source Credentials and Gateway

When adding new data to Power BI datasets published to the service, credential management and gateway configuration determine whether scheduled refreshes succeed.

Cloud Data Sources - Azure SQL, SharePoint Online, Dataverse, and other cloud sources authenticate directly through the Power BI service using OAuth or service account credentials configured in dataset settings.
On-Premises Data Sources - SQL Server, Oracle, file shares, and other on-premises sources require an on-premises data gateway. Install the gateway on a server with network access to your data sources and configure data source credentials in the gateway admin portal.
Credential Updates - When adding a new data source to an existing published dataset, you must update the data source credentials in the Power BI service (Workspace > Dataset settings > Data source credentials) before scheduled refresh will work.
Gateway Clustering - For enterprise deployments, configure gateway clusters with multiple gateway members for high availability and load distribution across data sources.

Why Choose EPC Group for Power BI Data Management

EPC Group has designed and optimized Power BI data models for Fortune 500 organizations for over 29 years. As a former Microsoft Gold Partner (2016 to program retirement, the oldest in North America) and current Microsoft Solutions Partner, our Power BI practice brings deep expertise in data modeling, Power Query optimization, incremental refresh, and enterprise dataset management. Our founder, Errin O'Connor, authored the bestselling Microsoft Press book on Power BI, making EPC Group the authoritative partner for enterprise analytics implementations.

End-to-end Power BI data model design from source analysis through production deployment
Incremental refresh configuration that reduces refresh times by 80-90% for large enterprise datasets
Complex data integration patterns connecting 10+ data sources into unified analytics models
Performance optimization that delivers sub-second query response times on billion-row datasets

Need Help Managing Power BI Data?

EPC Group's Power BI experts design data models, configure data pipelines, and optimize refresh strategies that keep your enterprise analytics current, accurate, and performant at scale.

Schedule a Consultation Call (888) 381-9725

Frequently Asked Questions

What is the difference between Append and Merge in Power BI?

Append adds rows (vertical combination) by stacking data from two or more tables with the same column structure. Think of it like adding new records to an existing table. Merge adds columns (horizontal combination) by matching rows from two tables on a common key, similar to a SQL JOIN. Use Append when combining data from the same source structure (e.g., monthly sales files). Use Merge when enriching data with attributes from a lookup table (e.g., adding customer region from a customer dimension table).

How do I add data from a new Excel file to my existing Power BI dataset?

Open your Power BI Desktop file (.pbix), go to Home > Get Data > Excel, and select the new file. In Power Query, review and transform the data as needed. Then use Home > Append Queries to combine the new data with your existing table. Alternatively, store all Excel files in a single folder and use the Folder connector, which automatically picks up new files on each refresh without manual intervention.

Can I add data to a published Power BI dataset without using Desktop?

There are several options. Power BI Dataflows allow you to create and modify data transformation logic directly in the Power BI service browser. The Power BI REST API enables programmatic data push to push datasets. Power BI streaming datasets accept real-time data via API calls. For enterprise scenarios, modify the dataset in Power BI Desktop, republish, and let scheduled refresh handle data loading automatically.

What is incremental refresh and when should I use it?

Incremental refresh is a Power BI feature that refreshes only new and modified data rather than reloading the entire dataset. Use it when your dataset is large (millions of rows), your data source supports query folding, and you have a reliable date/timestamp column for partitioning. It reduces refresh times from hours to minutes, lowers source system load, and stays within Power BI dataset size limits by managing historical data partitions efficiently.

Why is my data refresh failing after adding a new data source?

The most common cause is missing or invalid credentials in the Power BI service. After adding a new data source and republishing, navigate to the dataset settings in the Power BI service and configure credentials for the new data source under "Data source credentials." If the source is on-premises, ensure the on-premises data gateway includes the new data source in its configuration. Also verify that the gateway service account has appropriate permissions to access the data source.

Power BI Strategy: 2026 Considerations for How To Add New Data To Existing Data In Power BI

Power BI Copilot grounds itself on the semantic model, NOT the underlying source data. That means Copilot answers are only as accurate as the DAX measure definitions, the field metadata (display folders, descriptions, hierarchies), and the synonyms taxonomy. In practice, the difference between a Copilot deployment that drives 32% time-savings and one users abandon within 90 days is whether the semantic model was Copilot-prepared.

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.

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.

How to Add New Data to Existing Data in Power Bi delivered by senior Microsoft architects

This How to Add New Data to Existing Data in Power Bi explainer is part of EPC Group's practitioner library. The audience is enterprise IT, compliance, and architecture leaders evaluating Microsoft technology choices for Fortune 500 and regulated-industry environments. Content reflects real production experience, not vendor marketing.

EPC Group ships How to Add New Data to Existing Data in Power Bi as part of broader Microsoft 365, SharePoint, Power BI, Azure, and Microsoft Copilot engagements. The decision criteria, deployment patterns, and governance considerations covered here come directly from senior architect playbooks honed across 11,000-plus enterprise engagements.

Fixed-fee accelerators with real scope

Predictable scope, predictable price, predictable outcome. Copilot Readiness, Security Hardening, Tenant Health Check, SharePoint Migration, and Teams Governance ship as defined accelerators where Big 4 firms quote open-ended time-and-materials. Most projects land in the $25K-$150K range for accelerators or $150K-$750K for full programs.

How EPC Group engages

Six-phase methodology applied to every engagement, compressed for fixed-fee accelerators and extended for full programs.

Discovery — two-week assessment of the current estate, gap analysis, risk register, target architecture, costed remediation roadmap.
Design — senior architect produces the target topology, identity framework, Conditional Access, Purview, governance model, and security posture, reviewed by client leads.
Pilot — 25 to 100 user pilot in a real business unit. Migrate, apply baselines, test integrations, capture feedback.
Wave rollout — migrate in waves of 500 to 2,500 users with communications, training, hypercare, and a per-wave retrospective.
Adoption — role-based training, Champions network, executive sponsor enablement, metrics tracked against a measured baseline.
Operate — optional managed-services retainer for license optimization, governance reviews, security monitoring, and quarterly business reviews.

Government and defense contractors

For federal agencies and CMMC-regulated suppliers, EPC Group delivers FedRAMP Moderate and High posture, GCC and GCC High tenants, CUI handling, and ITAR-controlled data segregation. Errin O'Connor (CEO and founder) is a contributor to the FedRAMP framework; that direct authorship shows up in how we architect Conditional Access for government endpoints.

Healthcare and life sciences

For hospitals, payors, and pharmaceutical companies, EPC Group enforces HIPAA, business associate agreements, and Microsoft Purview sensitivity labels for protected health information. Epic and Cerner integration patterns are part of our regulated-industry library, alongside 21 CFR Part 11 e-signature controls for clinical trials and validated SharePoint document workflows for life-sciences manufacturing.

Microsoft-only since 1997

29 years of Microsoft-exclusive consulting. Microsoft Solutions Partner with core designations across Modern Work, Security, and Data & AI.

EPC Group was the oldest continuous Microsoft Gold Partner in North America from 2016 until program retirement in 2022. Errin O'Connor authored four Microsoft Press bestsellers covering Power BI, SharePoint, Azure, and large-scale migrations.

Engagement models

Three engagement models cover most enterprise needs. Most clients start with a fixed-fee accelerator and grow into a full program or a managed-services retainer.

Fixed-fee accelerators — Copilot Readiness, Security Hardening, Tenant Health Check, SharePoint Migration, Teams Governance. Defined scope and price. Typical range $25,000 to $150,000 over four to twelve weeks.
Project engagements — full migration or governance program with milestone-based billing. Discovery through hypercare. Typical range $150,000 to $750,000-plus over three to nine months.
Managed services — tiered retainer for ongoing operations. Named senior architect on the account. From $3,500 per month with a twelve-month minimum.

Talk to a senior architect

30-minute discovery call. No pitch deck. Call (888) 381-9725 or schedule a discovery call and a senior architect responds within one business day.

Appending Queries: Adding New Rows

Append Two Tables - In Power BI Desktop, go to Home > Append Queries. Select the primary table and the table to append. Power Query matches columns by name and data type, adding all rows from the second table to the first.
Append Three or More Tables - Select "Append Queries as New" to create a new combined table, then choose "Three or more tables" to append multiple sources simultaneously. Ideal for consolidating monthly or regional datasets.
Handling Mismatched Columns - When tables have different column structures, Power Query creates null values for missing columns. Review the appended result and handle nulls appropriately using Replace Values, Fill Down, or conditional column transformations.
Folder-Based Append - For recurring data files (monthly CSVs, quarterly Excel reports), use the Folder connector to automatically append all files in a SharePoint library or local folder. New files added to the folder are automatically included on refresh.
Performance Tip - When appending large tables, apply filters before the append step to reduce the data volume. Filter out irrelevant rows, outdated records, or test data at the source level rather than after appending.

Merging Queries: Adding New Columns

Merge Types - Power Query supports six join types: Left Outer (all rows from left, matching from right), Right Outer, Full Outer, Inner (only matching rows), Left Anti (left rows with no match), and Right Anti. Left Outer is the most commonly used for data enrichment.
Multi-Column Keys - When a single column doesn't uniquely identify rows, hold Ctrl and select multiple columns as the merge key (e.g., merge on both CustomerID and Date for transactional data).
Expand Merged Columns - After merging, the result includes a column with nested tables. Click the expand icon to select which columns from the merged table to include, and choose whether to use the original column name as a prefix.
Fuzzy Matching - Enable fuzzy matching in the merge dialog for scenarios where key values don't match exactly (e.g., "Microsoft Corp" vs "Microsoft Corporation"). Configure similarity threshold and transformation table for consistent matching.
Merge vs Relationship - For dimension/fact table combinations (e.g., Sales + Products), consider using Power BI relationships instead of merging in Power Query. Relationships are more memory-efficient and support complex DAX calculations across related tables.

Adding New Data Sources to Existing Models

Get Data - In Power BI Desktop, click Home > Get Data and select the appropriate connector (SQL Server, Excel, Web, OData, REST API, SharePoint, etc.). Configure connection parameters and credentials.
Transform in Power Query - Before loading the new data, apply transformations in the Power Query Editor: rename columns to match your naming conventions, change data types, remove unnecessary columns, and apply filters.
Define Relationships - After loading, navigate to the Model view and create relationships between the new table and existing tables. Match on common key columns (CustomerID, ProductID, DateKey) with the appropriate cardinality (one-to-many, many-to-one).
Update DAX Measures - Review existing DAX measures to determine if they need modification to incorporate the new data source. Measures using ALL, ALLEXCEPT, or CALCULATE with specific table references may need adjustment.
Test Thoroughly - Validate that existing reports and visuals continue to work correctly after adding the new source. Check that filters, slicers, and drill-through actions behave as expected with the expanded data model.

Incremental Refresh: Automated Data Addition

How It Works - You define a date range parameter (e.g., load the last 3 years of data, refresh only the last 30 days). Power BI partitions the dataset by date and only refreshes partitions within the refresh window, leaving historical partitions untouched.
Configuration Steps - Create RangeStart and RangeEnd parameters in Power Query (DateTime type). Filter your date column using these parameters. In the Power BI Desktop model view, right-click the table and select "Incremental refresh" to configure the policy.
Requirements - The data source must support query folding (the ability to push filter predicates to the source). SQL Server, Azure SQL, Azure Synapse, Dataverse, and OData sources support query folding. Excel and CSV files do not.
Real-Time Data - Combine incremental refresh with DirectQuery for the latest partition to get near-real-time data. Historical partitions use Import mode for fast performance, while the current partition queries the source directly.
Licensing - Incremental refresh is available in Power BI Pro (with limitations) and fully featured in Premium Per User and Premium Per Capacity. Premium supports up to 48 refreshes per day and larger dataset sizes.

Managing Data Source Credentials and Gateway

When adding new data to Power BI datasets published to the service, credential management and gateway configuration determine whether scheduled refreshes succeed.

Cloud Data Sources - Azure SQL, SharePoint Online, Dataverse, and other cloud sources authenticate directly through the Power BI service using OAuth or service account credentials configured in dataset settings.
On-Premises Data Sources - SQL Server, Oracle, file shares, and other on-premises sources require an on-premises data gateway. Install the gateway on a server with network access to your data sources and configure data source credentials in the gateway admin portal.
Credential Updates - When adding a new data source to an existing published dataset, you must update the data source credentials in the Power BI service (Workspace > Dataset settings > Data source credentials) before scheduled refresh will work.
Gateway Clustering - For enterprise deployments, configure gateway clusters with multiple gateway members for high availability and load distribution across data sources.

Why Choose EPC Group for Power BI Data Management

End-to-end Power BI data model design from source analysis through production deployment
Incremental refresh configuration that reduces refresh times by 80-90% for large enterprise datasets
Complex data integration patterns connecting 10+ data sources into unified analytics models
Performance optimization that delivers sub-second query response times on billion-row datasets

Need Help Managing Power BI Data?

EPC Group's Power BI experts design data models, configure data pipelines, and optimize refresh strategies that keep your enterprise analytics current, accurate, and performant at scale.

Schedule a Consultation Call (888) 381-9725

Frequently Asked Questions

What is the difference between Append and Merge in Power BI?

How do I add data from a new Excel file to my existing Power BI dataset?

Can I add data to a published Power BI dataset without using Desktop?

What is incremental refresh and when should I use it?

Why is my data refresh failing after adding a new data source?

Power BI Strategy: 2026 Considerations for How To Add New Data To Existing Data In Power BI

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.

How to Add New Data to Existing Data in Power Bi delivered by senior Microsoft architects

Fixed-fee accelerators with real scope

How EPC Group engages

Six-phase methodology applied to every engagement, compressed for fixed-fee accelerators and extended for full programs.

Discovery — two-week assessment of the current estate, gap analysis, risk register, target architecture, costed remediation roadmap.
Design — senior architect produces the target topology, identity framework, Conditional Access, Purview, governance model, and security posture, reviewed by client leads.
Pilot — 25 to 100 user pilot in a real business unit. Migrate, apply baselines, test integrations, capture feedback.
Wave rollout — migrate in waves of 500 to 2,500 users with communications, training, hypercare, and a per-wave retrospective.
Adoption — role-based training, Champions network, executive sponsor enablement, metrics tracked against a measured baseline.
Operate — optional managed-services retainer for license optimization, governance reviews, security monitoring, and quarterly business reviews.

Government and defense contractors

Healthcare and life sciences

Microsoft-only since 1997

29 years of Microsoft-exclusive consulting. Microsoft Solutions Partner with core designations across Modern Work, Security, and Data & AI.

Engagement models

Three engagement models cover most enterprise needs. Most clients start with a fixed-fee accelerator and grow into a full program or a managed-services retainer.

Fixed-fee accelerators — Copilot Readiness, Security Hardening, Tenant Health Check, SharePoint Migration, Teams Governance. Defined scope and price. Typical range $25,000 to $150,000 over four to twelve weeks.
Project engagements — full migration or governance program with milestone-based billing. Discovery through hypercare. Typical range $150,000 to $750,000-plus over three to nine months.
Managed services — tiered retainer for ongoing operations. Named senior architect on the account. From $3,500 per month with a twelve-month minimum.

Talk to a senior architect

30-minute discovery call. No pitch deck. Call (888) 381-9725 or schedule a discovery call and a senior architect responds within one business day.

Appending Queries: Adding New Rows

Merging Queries: Adding New Columns

Adding New Data Sources to Existing Models

Incremental Refresh: Automated Data Addition

Managing Data Source Credentials and Gateway

Why Choose EPC Group for Power BI Data Management

Need Help Managing Power BI Data?

Frequently Asked Questions

Related Resources

6 Reasons to Use Power Automate in Power BI

Ad Hoc Reporting

Agriculture Power BI Consulting

Alteryx vs Power BI

Power BI Strategy: 2026 Considerations for How To Add New Data To Existing Data In Power BI

Decision factors EPC Group evaluates

How to Add New Data to Existing Data in Power Bi delivered by senior Microsoft architects

Fixed-fee accelerators with real scope

How EPC Group engages

Government and defense contractors

Healthcare and life sciences

Microsoft-only since 1997

Engagement models

Talk to a senior architect

Appending Queries: Adding New Rows

Merging Queries: Adding New Columns

Adding New Data Sources to Existing Models

Incremental Refresh: Automated Data Addition

Managing Data Source Credentials and Gateway

Why Choose EPC Group for Power BI Data Management

Need Help Managing Power BI Data?

Frequently Asked Questions

Related Resources

6 Reasons to Use Power Automate in Power BI

Ad Hoc Reporting

Agriculture Power BI Consulting

Alteryx vs Power BI

Power BI Strategy: 2026 Considerations for How To Add New Data To Existing Data In Power BI

Decision factors EPC Group evaluates

How to Add New Data to Existing Data in Power Bi delivered by senior Microsoft architects

Fixed-fee accelerators with real scope

How EPC Group engages

Government and defense contractors

Healthcare and life sciences

Microsoft-only since 1997

Engagement models

Talk to a senior architect