TRENDING

TECHNOLOGY NEWS FROM AROUND THE WORLD

→
Power BI and Fabric Semantic Views preview: How to share a revenue definition
Business Intelligence · 2026
Business Intelligence

Power BI and Fabric Semantic Views preview: How to share a revenue definition

A practical preview evaluation for shared OneLake metrics, managed read-only Direct Lake models and a controlled rollout.

Yazılımcının GünlüğüPublished: Nov 18, 20263 min read
Reading progress0%

A shared table does not settle metric definitions

Two teams can use the same data and still disagree about whether revenue is measured before discounts or after returns. The November 2026 Semantic Views preview describes tables, relationships and business metrics separately from their consumers. Pick a single business question first. Specify closed orders, currency and the date a return affects the result. A shared definition becomes useful when the business can explain those choices.

Know what publishing creates

Microsoft says publishing the preview creates a managed, read-only Direct Lake on OneLake semantic model. The view remains the source of truth. Maintain an existing Power BI semantic model as a comparison when it provides advanced modeling you depend on. Run a pilot in a small lakehouse. Record source table versions and ownership alongside the YAML or other definition files. Check preview availability and supported behavior in the actual tenant.

Data processing architectureConceptual sketch · summary of the article's technical flow

Reconcile one metric across consumers

Create test rows with a sale, a partial return and a different currency. Record the expected answer in a known implementation. Then compare two consumers using the same filters. If they disagree, check date selection, identity, filtering and the treatment of returns separately. Use a test identity with access to only one region when examining visibility. A common metadata definition does not replace testing authority in each consumer.

Use the pilot to decide where to adopt

Keep the business decision, owner and expected results next to the definition. A change can be published before every consumer reads it, so verify what each report actually uses. Identify a fallback for incorrect totals. Include month-close behavior, role enforcement and a broken source load in the acceptance criteria. Choose adopters on the basis of measured consistency and recoverability while the feature is in preview.

Validate platform choices against real workloads

Choose Warehouse, Lakehouse, Eventhouse or another processing layer from workload requirements: query patterns, event latency, file sizes, data quality and access controls. Build a representative pilot and compare at least two suitable architectures using the same criteria. Document update, deletion, versioning and retention semantics before treating a demonstration as production-ready.

Manage capacity and ownership together

Analytics cost includes compute, refresh frequency, failed-job retries, replicated models and access control, not only storage volume. Track cost alongside data freshness and user-facing latency. Assign an owner, service target, schema-change policy and incident process to each dataset. Scale capacity only after evidence identifies the actual bottleneck.

Be the first reader ✎ Write a comment

Comments

No comments yet. Be the first to contribute.

Discussion question from the editor Is net revenue defined in one place or in several models at your organization?

Morgan Lee

Reading “Power BI and Fabric Semantic Views preview: How to share a revenue definition” raised this question for me: data lineage and model correctness need verification.

Sample editor reply

Editor note: Product claims and measured outcomes should be assessed separately. A small pilot with defined metrics is a useful first step.

Charlie Adams

We should also discuss maintenance cost. An easy rollout does not guarantee trouble-free upgrades.

Alex Morgan

I would start with a pilot and measurable success criteria rather than assuming a launch means proven value.

✎ Write a comment

Your first and last name will appear publicly alongside your comment.