A practical guide to selective processing, schema governance and reliable executive reporting
The real cost of refreshing everything
A semantic model can refresh successfully and still fail its business purpose. The sales dashboard may contain incomplete orders, the margin report may combine mismatched reporting periods, or a schema change may disrupt a measure that executives use every morning. Meanwhile, large refresh jobs can consume capacity, query cloud warehouses and compete with interactive reporting.
The traditional response is often to refresh more frequently, increase capacity or rewrite the model. Sometimes that is necessary. But another question deserves attention first: which data and metadata actually changed, and what must be processed to deliver a reliable business answer?
Microsoft’s August 2026 Power BI feature summary introduced more granular semantic-model refresh choices in the Power BI Service modeling experience. The controls let editors distinguish schema synchronization from data refresh and, in supported workflows, operate on individual tables rather than always processing the whole model. They provide a better operational vocabulary. They do not, by themselves, guarantee lower costs or correct numbers.
The goal is not the fewest refreshes. It is the least necessary processing that still meets a documented freshness, completeness and accuracy standard. This guide explains the available controls, their limits and a practical way to implement them.
What changed in Power BI’s refresh experience
Power BI’s newer Service modeling interface offers three distinct refresh actions, described in the official data refresh documentation.
Refresh schema and data
This operation synchronizes the semantic model’s structure with its source and then refreshes data. It is appropriate when a reviewed source change must be reflected in the model and the related data needs updating. It is not automatically the safest option for routine production processing: a newly added source field or changed type can require downstream review.
Sync schema only
This updates the model structure without loading new data as part of that action. It is useful during planned modeling work, such as incorporating a new column, but it is not a validation step. Measures, relationships, report visuals, field visibility and row-level security still require review before a change reaches executive users.
Refresh data only
This loads current data while preserving the semantic model’s existing schema. It can help when a source adds columns that the business has not yet approved for the reporting layer. It does not protect against every breaking source change. A removed column, renamed field, incompatible type or failed Power Query transformation may still prevent refresh.
The controls also support table-level operations in the model editing experience. Instead of updating all tables, an editor can choose a specific table and determine whether its schema, data or both need attention. Microsoft’s guidance distinguishes editing from viewing mode: in viewing mode, only the Refresh data option is available.
The distinction matters because a production refresh is both a data operation and a change-management event. When schema adoption is deliberate, teams can test new fields and definitions before introducing them into established reports.
Table-level refresh is not incremental refresh
These terms are frequently confused. Table-level refresh answers which table should be processed. Incremental refresh answers which partitions or time periods within an imported table should be processed. They are complementary, not interchangeable.
Suppose a semantic model contains five years of orders and a small currency-rate table. Processing only the orders table can still be expensive if the entire five-year history is reloaded. A well-designed incremental policy can limit processing to recent partitions. Conversely, a table-level operation can avoid touching unrelated tables even when the target table has no incremental policy.
Microsoft documents incremental refresh policies using RangeStart and RangeEnd parameters, archive and refresh windows, and optional data-change detection. These policies have important assumptions. Historical corrections outside the refresh window may not be captured automatically. Change detection based on a maximum update timestamp does not necessarily detect hard deletions. Query folding must be checked so the source, rather than Power BI, does the intended filtering.
Advanced processing through the XMLA endpoint and enhanced REST API refresh provides additional control over tables and partitions in supported capacity configurations. Those are established engineering mechanisms with different prerequisites from the Service menu. Treat them as separate tools in the same operating model.
Storage mode changes the economics
Before changing a refresh schedule, determine whether each table uses Import, DirectQuery, Direct Lake or a composite configuration.
Import tables hold a copy of source data. Refreshing them can involve source scans, transformations, memory usage and semantic model processing. A large full refresh may temporarily need substantial additional memory while reports continue serving queries.
DirectQuery generally executes queries against the underlying source when report users interact with visuals. It does not require the same routine data import, but source compute cost, query latency and caching behavior become important.
Direct Lake reads from OneLake and has its own metadata and data-framing behavior. It should not be described as if every refresh reloads an imported dataset. Composite models mix these characteristics, so one model-wide rule may be inappropriate.
A useful first question is therefore not, ‘Can we refresh this model every fifteen minutes?’ It is, ‘What is the storage mode, when is the source actually ready, and what freshness does the business need?’ A faster refresh of incomplete source data simply delivers incomplete results sooner.
Five situations where selective refresh helps
1. A reference table changes independently
A product classification or currency-rate table may change daily while a large transactions table changes hourly. If the reporting logic permits, a targeted table refresh can avoid unnecessary processing. The important qualification is consistency: calculations combining facts and reference data must represent an approved business cutoff.
2. A source adds a field before governance approves it
A customer system introduces a new segment or status field. The BI team may want fresh values from existing columns without exposing the new field until its definition and access implications are reviewed. Refresh data only can preserve the current semantic schema during that review. A later schema sync should be an approved release.
3. Historical transactions rarely change
An orders table has years of history but most updates occur in the current period. Incremental refresh can avoid reprocessing stable historical partitions. The team still needs a policy for backdated returns, corrected invoices and finance restatements.
4. A report has a fixed executive deadline
A 9 a.m. report is only useful if all critical source feeds are complete before its refresh. An upstream completion signal and reconciliation gate can matter more than shaving five minutes from processing. The model should publish a validated business as-of timestamp, not merely the time the refresh job finished.
5. A schema release must be separated from data delivery
Data engineers may need to deploy a source change without immediately modifying executive measures or visuals. Separating schema synchronization from data refresh allows a controlled test-and-approve sequence. It does not remove the need for regression testing or a rollback plan.
A decision framework for the right operation
Use these rules as starting points, not universal prescriptions. Test them against the actual model, storage mode and workspace.
Source values changed; schema is stable: consider data-only processing at the relevant scope. Verify source completeness, key totals and business cutoff.
A reviewed source column or type change must enter the model: consider schema synchronization, downstream validation and then the appropriate data processing. Review measures, relationships, visibility and security.
A large imported fact table receives new records: consider incremental processing. Verify query folding, partition boundaries, correction horizons and deletion behavior.
Only a small dimension changed: consider table-level processing. Verify cross-table calculations and whether dependent objects require recalculation.
A business definition changed: use a coordinated model release, not an isolated refresh. Version the KPI definition and obtain stakeholder approval.
The model uses DirectQuery or Direct Lake: investigate source querying, metadata and cache behavior before assuming that a conventional Import refresh schedule is relevant.
Design a refresh contract, not just a calendar
A refresh contract is an agreement between data engineering, BI and business owners about when information is safe to publish. It has four parts.
Source readiness
Each critical upstream pipeline should publish a completion signal identifying its dataset, business date, expected partitions and validation result. For a margin report, sales, returns and cost allocations may all need to pass checks before the semantic model updates. A job that ran is not necessarily a job that produced complete data.
Schema compatibility
Classify source changes as additive, breaking or semantic. Adding a column can be technically harmless but still introduce sensitive information. Renaming a field can break transformations. Changing the meaning of ‘active customer’ can invalidate trend comparisons without changing any physical column name.
Business validation
Choose a concise set of checks: latest loaded business date, expected row counts, duplicate keys, missing values, reconciled financial totals and critical KPI definitions. Compare like-for-like reporting scopes. A green technical refresh indicator should never be the only evidence of correctness.
Ownership and escalation
Assign responsibility for upstream readiness, semantic model processing, business reconciliation and incident response. Define who can run schema syncs, full processing and exceptional historical backfills. For finance-critical models, changes that alter reporting definitions should require approval and a communication plan.
A practical implementation sequence
Step 1: Inventory the models that matter
Start with the reports executives actually use. For each semantic model, record its owner, workspace, capacity, storage mode, sources, tables, current refresh schedule, typical duration, recent failures, dependent reports and freshness SLA. Note gateways, incremental policies, Direct Lake configurations and XMLA-based automation.
Do not optimize every model simultaneously. Select one with a clear owner, measurable operational pain and enough history to compare before and after behavior.
Step 2: Establish a baseline
Collect representative refresh history, ideally including ordinary weekdays and a high-volume period. Track queue delay, processing duration, retries, failure reasons, source query load, capacity utilization and the interval from source-ready to report-ready. Capture the business data cutoff shown to users.
A shorter processing duration may be misleading if the new test ran on a lighter day. Compare similar data volumes and business cycles.
Step 3: Map table and report dependencies
Draw the path from source pipeline to imported or queried tables, relationships, calculations and executive reports. Group data by consistency requirements. Sales and returns may need to share a cutoff even if their pipelines finish at different times. Stable dimensions can sometimes be refreshed separately, but only when business rules permit.
If one semantic model serves dashboards with incompatible freshness requirements, consider whether separate models or explicit as-of labeling would be more reliable.
Step 4: Test the Service controls outside production
In a development workspace, test schema-and-data, schema-only and data-only operations. Introduce a harmless additive column, then a controlled breaking change, and observe how the model behaves. Test table-level actions where supported. Check calculations, report visuals, security rules and refresh history after each operation.
Document which controls are actually available to editors and viewers in the target environment. Do not infer universal behavior from a product announcement.
Step 5: Evaluate incremental and API processing separately
For large Import tables, inspect RangeStart and RangeEnd filters and confirm they fold to the source. Test late-arriving records and corrections outside the normal window. Determine whether periodic historical backfills are needed.
For supported capacities, enhanced refresh through the Power BI REST API can target tables or partitions and provides asynchronous status tracking, cancellation and retry-related options. Microsoft documents prerequisites including appropriate model capacity and Dataset.ReadWrite.All permission. An accepted asynchronous request is not proof that processing has completed or that the business totals reconcile.
Step 6: Build monitoring and a rollback path
Monitor four stages: upstream ready, processing started, processing completed and business validation passed. Alert on stale data, failed refreshes, unusually long duration and reconciliation exceptions. Record a known-good model version and a documented restoration procedure.
Schema-only synchronization is not a substitute for deployment testing. A model may accept a column while downstream DAX, relationships, visuals or security still require changes.
Step 7: Pilot, compare and approve
Run the revised strategy through comparable reporting windows. Measure freshness, accuracy, processing cost and incident rate together. Promote it only when the business outcomes remain correct and at least one operational constraint improves. Revisit the policy after source migrations, new data feeds, volume changes or reporting redesigns.
Illustrative example: an executive sales model
Consider a hypothetical company with orders, returns, advertising spend and exchange rates in one semantic model. Orders arrive hourly. Returns are finalized overnight. Advertising spend updates several times daily. Exchange rates are approved once each morning. This is an illustrative architecture, not a client case study or a claim of measured savings.
A naive design refreshes the entire Import model hourly. That may repeatedly process unchanged tables, yet the margin dashboard can still be wrong if it combines current orders with incomplete returns.
A more reliable design defines two business products. An operational sales dashboard may show recent orders and advertising performance with a clearly labeled cutoff. A finance-approved margin dashboard waits until returns and exchange rates pass validation. Processing groups and refresh timing follow these contracts.
If both dashboards must share a semantic model, test whether selective processing can maintain their different consistency requirements. Otherwise, separate models or explicit reporting-period labels may be preferable. The right architecture is the one that makes the meaning of each number unambiguous.
How to measure whether the change worked
A useful executive scorecard should include source-to-report latency, freshness SLA attainment, refresh failures, processing resource consumption, business reconciliation exceptions and schema-related incidents. Segment the measures by model and reporting period.
Cost must be measured across the architecture. Less Power BI processing may be offset by more frequent warehouse queries or higher DirectQuery consumption. Partial processing can still trigger dependent recalculation. Never promise a fixed percentage saving simply because fewer tables are refreshed.
Set acceptance criteria before the pilot. For example: no critical metric regressions; no increase in stale-data incidents; a documented schema release path; and an observed improvement in duration, capacity pressure or source workload. A fast refresh that misses the business deadline is not a success.
A 30-day rollout plan
Week 1
Select a critical model. Inventory storage modes, dependencies, refresh history, upstream completion signals and business cutoffs. Agree on three critical reconciliation checks.
Week 2
Reproduce refresh behavior in a test workspace. Exercise the new Service choices and verify additive and breaking schema changes. Confirm table-level behavior, report consistency and access permissions.
Week 3
Introduce the selected selective or incremental processing policy with monitoring, source readiness checks and a rollback plan. Compare it with the baseline during representative business windows.
Week 4
Review measured outcomes with BI, finance and platform owners. Approve production rollout only if accuracy and freshness remain acceptable. Publish the runbook, escalation contacts and a review date.
Common mistakes to avoid
Mistake 1: Using data-only refresh forever to avoid schema governance. Model and source can drift until processing fails. Maintain a schema review backlog.
Mistake 2: Refreshing a table without checking calculations that join it to other tables. Technically valid tables can produce inconsistent KPIs.
Mistake 3: Assuming incremental refresh captures all historical changes. Backdated corrections, hard deletions and non-folding queries require deliberate handling.
Mistake 4: Optimizing duration while ignoring upstream cost. Frequent small refreshes may repeatedly scan expensive source tables.
Mistake 5: Giving broad production refresh privileges without an owner or change process. Use role-based access and audit significant operations.
Mistake 6: Treating a successful refresh as proof of complete business data. Validate the source cutoff and critical totals.
Frequently asked questions
1. What are Power BI semantic model refresh controls?
They let teams choose whether to update schema, data or both, and in supported Service modeling workflows, apply operations at model or table scope. They complement incremental refresh and advanced processing tools.
No. It preserves the current semantic model schema during that operation, but incompatible source changes can still break queries, transformations or calculations.
3. When is sync schema only appropriate?
When a reviewed source structure change needs to enter the semantic model separately from data loading. Test downstream dependencies and process data as needed before releasing the change.
4. Is table-level refresh the same as incremental refresh?
No. Table-level refresh chooses a table. Incremental refresh chooses time-based partitions within an imported table. Both can matter in large models.
5. Will selective refresh automatically lower Power BI costs?
Not necessarily. Savings depend on processing work, capacity billing, source queries and dependencies. Measure before-and-after workload rather than assume a percentage.
6. What about Direct Lake?
Direct Lake does not behave like a conventional imported table. Confirm metadata, framing and data visibility behavior for the target model before choosing an operational policy.
7. How should we handle corrections to old transactions?
Set an incremental window that matches the correction horizon or add controlled historical reprocessing and reconciliation. A short window can miss valid restatements.
8. Are all advanced refresh features available on every license?
No. The Service interface and XMLA or enhanced REST API processing have different requirements. Check capacity, permissions and current Microsoft documentation before designing automation.
9. Should executive dashboards show a refresh timestamp?
Yes, but distinguish the technical processing time from the latest validated business data cutoff. A model refreshed at 9 a.m. can still contain yesterday’s source data.
10. What is the safest place to start?
Choose one important model, document its dependencies and business freshness contract, then run a measured nonproduction pilot. Validate outputs before changing a wider BI estate.
The executive takeaway
Granular refresh is valuable because it makes a previously hidden decision explicit: what changed, what must be processed and what must remain stable. Reliable executive BI still depends on source readiness, semantic definitions, tested changes and clear ownership.
Actiknow’s business intelligence consulting and implementation services cover data integration, modeling, reporting and refresh mechanisms. Its business intelligence dashboard development approach also emphasizes design, testing and operational maintenance. These are useful considerations when assessing the reliability of a wider reporting environment.
Discuss your Power BI refresh architecture
If your semantic models are slow, costly to operate or difficult to change safely, contact Actiknow to discuss a focused assessment of model dependencies, refresh governance and reporting controls. A useful first deliverable is a measurable improvement plan, not an unverified savings promise.
Official documentation and further reading
Microsoft’s August 2026 Power BI update describes the Service refresh choices. Microsoft’s data refresh guidance explains storage modes and processing behavior. Its incremental refresh documentation explains partition policies and correction risks. The enhanced REST API guidance covers supported advanced processing and prerequisites.
