New board topics in Microsoft Fabric Community

function logical error

Dicken — Mon, 14 Sep 2026 17:27:46 GMT

Hi, i kinda get why this error happens but thougt someone might have thoughts insights into the
error problem;

i i start with a true false ;

= let test =( x)=> Number.Round(x) = x
in test

but if i then us ;

if test then "whole" else "decimal"

i get an eroor but i can use ;

= (x)=> if Number.Round(x) = x then "whole" else "decimal"

sorry for the spacing , I could not get code tags to work and the formatting kept goiong all over the plaice.

why did i have to go thru the rest connection's properties again on my pipeline's copy job

db042190 — Mon, 14 Sep 2026 17:11:16 GMT

hi i was in a rush when this happened and can post more detail here if necessary, but last week when i went to run my pipeline which was already working, it seemed to me my rest connection to an sap api was inactivated and fabric was basically saying it needed to either be inactivated or fixed. That was unexpected and it seemed to me i was forced into more or less revisiting the copy job's setup steps in order for the problem to go away. i didnt need to reset the conn's credentials but i did need (it seemed) to "sign in" again to pbi. Can somebody tell me what this is all about? How is this going to run unattended if this kind of thing happens again?

Exrtract all workspace lineage list in service

Prasanth460 — Mon, 14 Sep 2026 15:41:45 GMT

Hi Experts,

I need a help on how to extract the lineage of all workspaces, reports inside those workspaces and data models connected to that reports and data base that semantic model used to connect.

layers: Workspace--> report--> semantic model--> data source(eg: AAS model).

I can get list till 3 layers but unable to get details of 4th layer(data source) using admin monitoring folder data.

I have fabric and platform admin access. could you please help me to know if there is a way to extract complete details in power bi service. Unfortunatly, I don't have access to run API's directly,

your support helps to get the detailed list of all the workspaces in power BI service.

view 'my posts'

Dicken — Mon, 14 Sep 2026 15:07:03 GMT

Hello,
I used to be able to go to 'account' and select view subscriptions and it would bring up my
previous questions, this seems to have been removed. so how do i see my posts?

Power BI Theme Gallery Redirecting to an Incorrect URL

ajaythomas — Mon, 14 Sep 2026 14:00:59 GMT

Power BI Theme Gallery are being redirected to an incorrect URL after new update

https://community.fabric.microsoft.comhttps//community.fabric.microsoft.com/category/powerbi/discussions/themesgallery

This issue impacts the user experience and prevents successful navigation to the expected destination.

How to add RLS on top of FUAM datasets

TobNyg — Mon, 14 Sep 2026 13:42:15 GMT

We are testing the FUAM reports and would like to share some of them with workspace administrators.

To achieve this, we want to implement RLS so that workspace owners can only see data for the workspaces they own.

I tried creating a composite model with an RLS security table containing User and WorkspaceName, and created a relationship to the Workspaces table.

However, the filtering does not seem to work properly for the Workspaces table, which is running in DirectQuery mode.

Has anyone implemented RLS for FUAM before, and if so, what approach would you recommend?

AdminCartograph: a Power BI custom visual for multi-layer subnational maps.

Nabilmj — Mon, 14 Sep 2026 13:40:05 GMT

Repo: AdminCartograph on github

Sideload the shipped .pbiviz from releases on AdminCartograph on github

The problem

Power BI's stock map visuals don't handle subnational boundaries the way governments, humanitarian orgs, and analysts working with OCHA / P-code data actually need. Shape Map has no labels, no drill, no bubbles-on-boundaries. Filled Map is Bing-tile-bound and doesn't take custom TopoJSON. Everyone I've talked to has the same workaround: export to QGIS, screenshot, paste into PowerPoint. AdminCartograph replaces that whole loop with one visual.

What it does

Bring your own geometry. Custom upload takes any GeoJSON or TopoJSON at design time (Admin1 required, Admin2 optional). Field-mapping dropdowns auto-detect ADM1_PCODE / pcode_1 / gid_1 / state_id and let you override. The uploaded geometry persists inside the .pbix — no distributing side-files. Eight OCHA countries ship in the bundle for quick starts (AFG, COD, HTI, IRN, LBN, SDN, SYR, YEM); everyone else uses the upload flow.

Five stacked layers. Choropleth (quantile / equal / manual / categorical), bubbles (√-area scaled, constant on-screen size at zoom), pie / donut / column / concentric glyphs per polygon, a full label engine, country outer glow.

Drill. Click an Admin1 → zoom to its Admin2 children, neighbour states dim to 55 %, three viewport-aware top-bar layouts, prev / next arrows that respect any external slicer's filter set.

Cross-filter both ways. Click a polygon → slicers narrow. Slicers narrow → the map auto-zooms to the filtered subset (Admin1 and Admin2 modes both).

Labels done properly. Area-weighted centroid with polylabel fallback for concave shapes, halos via paint-order: stroke fill, per-card Name source and Value source dropdowns, hide-on-overflow, constant on-screen size on zoom.

Legends: five of them. Choropleth, bubble, glyph categories, Admin-levels stroke samples, and a Values legend explaining what each label number means. Combined into one styled container when they share a corner.

Export. PDF / PowerPoint / page-image via the host's renderingFinished signal — the map renders inside the exported deck instead of showing "visual not supported". Plus an SVG-download modal for print-quality vector output.

Real-world touches. Admin1 / Admin2 aliases (Governorate / District, State / Locality), PCODE-tolerant matching (SD-01 == SD_01 == SD01), a name-based link field so you can join by state name when your data has no P-codes, an on-canvas mismatch banner that shows sample keys from both sides when nothing joins.

Under the hood

~7 K lines of TypeScript on top of powerbi-visuals-api 5.11, d3-geo, topojson-client. Full offline; embedded geometry via require() at bundle time. Format-pane model is strongly typed through formattingSettings (17 cards, deep-linked from the wiki). MIT-adjacent ISC license; the bundled COD boundaries carry OCHA / fieldmaps.io terms.

Docs

Every card, every setting, every failure mode is documented in the wiki: AdminCartograph wiki on github. The Install and Use page is the tour, Custom Geometry Upload is the killer feature's walkthrough.

Feedback and issues welcome. Especially interested in hearing which non-bundled countries people would use it with — the upload flow works for anywhere, but real-world reports of it in production are the best signal.

AdminCartograph: a Power BI custom visual for multi-layer subnational maps.

Nabilmj — Mon, 14 Sep 2026 13:55:06 GMT

Repo: https://github.com/nabilaljarmozi/AdminCartograph
Sideload the shipped .pbiviz from releases/AdminCartograph.pbiviz.

The problem

What it does

Bring your own geometry. Custom upload takes any GeoJSON or TopoJSON at design time (Admin1 required, Admin2 optional). Field-mapping dropdowns auto-detect ADM1_PCODE / pcode_1 / gid_1 / state_id and let you override. The uploaded geometry persists inside the .pbix — no distributing side-files. Eight OCHA countries ship in the bundle for quick starts (AFG, COD, HTI, IRN, LBN, SDN, SYR, YEM); everyone else uses the upload flow.
Five stacked layers. Choropleth (quantile / equal / manual / categorical), bubbles (√-area scaled, constant on-screen size at zoom), pie / donut / column / concentric glyphs per polygon, a full label engine, country outer glow.
Drill. Click an Admin1 → zoom to its Admin2 children, neighbour states dim to 55 %, three viewport-aware top-bar layouts, prev / next arrows that respect any external slicer's filter set.
Cross-filter both ways. Click a polygon → slicers narrow. Slicers narrow → the map auto-zooms to the filtered subset (Admin1 and Admin2 modes both).
Labels done properly. Area-weighted centroid with polylabel fallback for concave shapes, halos via paint-order: stroke fill, per-card Name source and Value source dropdowns, hide-on-overflow, constant on-screen size on zoom.
Legends: five of them. Choropleth, bubble, glyph categories, Admin-levels stroke samples, and a Values legend explaining what each label number means. Combined into one styled container when they share a corner.
Export. PDF / PowerPoint / page-image via the host's renderingFinished signal — the map renders inside the exported deck instead of showing "visual not supported". Plus an SVG-download modal for print-quality vector output.
Real-world touches. Admin1 / Admin2 aliases (Governorate / District, State / Locality), PCODE-tolerant matching (SD-01 == SD_01 == SD01), a name-based link field so you can join by state name when your data has no P-codes, an on-canvas mismatch banner that shows sample keys from both sides when nothing joins.

Under the hood

Docs

Every card, every setting, every failure mode is documented in the wiki: https://github.com/nabilaljarmozi/AdminCartograph/wiki. The Install and Use page is the tour, Custom Geometry Upload is the killer feature's walkthrough.

Two way slicer Selection

YashikaAgrawal — Mon, 14 Sep 2026 13:14:59 GMT

Hi,

I have two slicers in my Power BI report: Source Tenant and Migration Batch.

Currently, if I select a Source Tenant (for example, INFY), the corresponding Migration Batch (for example, Pilot-1) gets selected/filtered, and this is working as expected.

However, I need the reverse behavior as well.

For example, if I select Pilot-1 in the Migration Batch slicer, I want the corresponding Source Tenant (INFY or TCS, depending on the data) to be automatically selected in the Source Tenant slicer.

Is it possible to automatically select/check the corresponding value(s) in one native Power BI slicer based on a selection made in another slicer?

I am specifically looking for the actual slicer selection/checkbox to be automatically selected, rather than simply filtering the available values.

Thanks,

On-Premises Data Gateway Deprecated Warning – Looking for Step-by-Step Upgrade Guidance

JibinSebastian — Mon, 14 Sep 2026 12:59:14 GMT

Hi Community,

I recently received the following warning on one of our Microsoft Fabric / Power BI semantic models:

"On-Premises Gateway: The on-premises data gateway version that this semantic model uses is deprecated and will stop working in the future. Please upgrade your data gateway to the latest version to avoid connectivity issues."

Our semantic models are connected to an on-premises SQL Server through the Microsoft On-premises Data Gateway. The gateway is currently working, but because Microsoft is warning that the installed version will eventually stop being supported, I would like to upgrade it proactively.

Could someone please provide the recommended step-by-step process for safely upgrading an existing On-premises Data Gateway used by Microsoft Fabric and Power BI?

I would particularly like to understand whether I can install the latest gateway version directly over the existing installation or whether the current gateway needs to be uninstalled first.

I would also like to know whether the existing gateway cluster, SQL Server connections, credentials, data sources, and other configurations will remain intact after the upgrade.

Before performing the upgrade, should I back up or verify anything, such as the gateway recovery key or gateway cluster information?

Is there any expected downtime during the upgrade? Should Fabric pipelines, Power BI semantic model refreshes, and scheduled refreshes be temporarily paused before starting?

If the gateway is running on a production server, are there any additional precautions that should be taken? Is a Windows/server restart normally required after upgrading?

Finally, after completing the upgrade, what would be the recommended validation process to confirm that the gateway is online, SQL Server connectivity is working, semantic models are refreshing successfully, and Microsoft Fabric pipelines using the gateway continue to work correctly?

Our main objective is to upgrade the gateway safely while minimizing disruption to our production Fabric and Power BI workloads.

If anyone has recently completed a similar gateway upgrade, I would really appreciate a step-by-step procedure, checklist, or Microsoft documentation that you followed.

Thanks in advance for your help.

Best regards,
Jibin

Analyze feature in Power BI embed link

UsmanBhasa — Mon, 14 Sep 2026 11:09:53 GMT

I’m trying to use the Analyze > Explain why this increase/decrease feature in Power BI. It works fine when I access the report through the Workspace in Power BI Service, but it doesn’t work when the report is accessed through an embedded link directly in the browser.
it's for line chart. and it's in import mode as well. please help me if any options are there.

How to automatically export a PBI screenshot for the latest month?

SRJPBI — Mon, 14 Sep 2026 10:55:04 GMT

I have a Power BI report published in the online service. It automatically refreshes via a schedule. I now want to set up a scheduled process which automatically emails a screenshot of the report to certain people.

I know I can do this by setting up a subscription, but here's the tricky bit: the report has a couple of slicers for year and month. So if I set up a subscription with the slicers set to August 2026, then the screenshots will keep showing August 2026 unless I manually update the slicers.

Is there a way for me to have the slicers automatically update before the screenshot is emailed out?

I have access to Power Automate Desktop if that helps.

From On-Premises SQL Server to Microsoft Fabric with a Metadata-Driven Medallion Pipeline

ezalor — Mon, 14 Sep 2026 10:48:56 GMT

In this demo, I use DataCoolie to move WideWorldImporters data from an on-premises SQL Server into Microsoft Fabric. The pipeline is driven by one metadata.json file and follows the Bronze, Silver, and Gold pattern.

The focus here is the Fabric execution flow, not the earlier development process.

The complete sample is available in the datacoolie/dc-demo-fabric repository.

Architecture

The SQL Server remains on-premises, so ingestion runs from an external Polars runner. Downstream processing runs inside Fabric:

Stage	Runtime	Output
source2bronze	On-premises Polars	Parquet in Files/bronze
bronze2silver	Fabric Python 3.12 notebook with Polars and delta-rs	Delta tables in silver
silver2gold	Fabric Spark notebook	Delta tables in gold

The workspace uses two Lakehouses:

lh_wwi_medallion_demo
├── Files/bronze
├── Tables/silver
└── Tables/gold

lh_etl
└── Files/control/test-fabric
├── metadata/current/metadata.json
├── logs
└── watermarks

This keeps operational state separate from business data while allowing every runtime to use the same metadata and watermarks.

One metadata file, three stages

The final metadata contains four connections, 68 dataflows, and shared schema hints. Each dataflow declares its stage, source, destination, load type, watermark, merge keys, or SQL query. The runner remains generic: it reads this file and receives only the stage name it should execute.

The Fabric environment maps logical connections to:

bronze_parquet → Files/bronze
silver_delta → Tables/silver
gold_delta → Tables/gold

Note: An AI agent will assist in generating the metadata.json file.

Uploading the artifacts with Fabric CLI

After creating the two Lakehouses, install the Fabric CLI, authenticate, upload the metadata, and import the two notebooks:

pip install --upgrade ms-fabric-cli fab auth login $workspace = 'wwi_medallion_demo_test_fabric.Workspace' $etl = "$workspace/lh_etl.Lakehouse" fab mkdir "$etl/Files/control/test-fabric/metadata/current" fab cp '.\metadata.json' ` "$etl/Files/control/test-fabric/metadata/current/metadata.json" -f fab import "$workspace/run_fabric_polars.Notebook" ` -i '.\runners\run_fabric_polars.ipynb' --format ipynb -f fab import "$workspace/run_fabric_spark.Notebook" ` -i '.\runners\run_fabric_spark.ipynb' --format ipynb -f

Stage 1: SQL Server to Bronze

The on-premises runner reads 31 business tables and appends raw Parquet batches to OneLake. Every table has a watermark: ValidFrom, LastEditedWhen, or VehicleTemperatureID. Timestamp-based flows reread a one-day overlap to reduce the chance of missing late records.

Bronze files are organized by ingestion date:

Files/bronze/<schema>__<table>/YYYY/MM/DD/

This stage still runs on-premises because it requires SQL Server connectivity:

$control = 'abfss://wwi_medallion_demo_test_fabric@onelake.dfs.fabric.microsoft.com/lh_etl.Lakehouse/Files/control/test-fabric' python '.\runners\run_fabric_polars_azure_sdk.py' ` --metadata-path "$control/metadata/current/metadata.json" ` --watermark-base-path "$control/watermarks" ` --base-log-path "$control/logs" ` --stage source2bronze --max-workers 4

Stage 2: Bronze to Silver

A Fabric Python notebook runs this stage with Polars and delta-rs, without Spark. It reads new Bronze files through __file_modification_time, removes duplicate source keys, and performs a Delta merge_upsert for all 31 tables.

The result is a current-state Silver replica while Bronze keeps the raw append history.

After Bronze is ready, start the notebook with Fabric CLI. The Lakehouse configuration binds the notebook to lh_wwi_medallion_demo:

$lakehouseConfig = '{"defaultLakehouse":{"name":"lh_wwi_medallion_demo","id":"<lakehouse-id>","workspaceId":"<workspace-id>"}}' fab job run "$workspace/run_fabric_polars.Notebook" ` -P "STAGE:string=bronze2silver,_inlineInstallationEnabled:bool=true" ` -C $lakehouseConfig --timeout 3600

Stage 3: Silver to Gold

The final stage runs in a Fabric Spark notebook. SQL queries stored in metadata read two-level names such as silver.Sales__InvoiceLines and create six Gold products:

DimDate
DimGeography
DimProduct
DimPerson
DimDeliveryMethod
FactInvoiceLineProfitability

The source instance had no customer data, so customer-dependent Gold models were intentionally excluded.

Run Gold only after the Silver notebook succeeds:

fab job run "$workspace/run_fabric_spark.Notebook" ` -P "STAGE:string=silver2gold,_inlineInstallationEnabled:bool=true" ` -C $lakehouseConfig --timeout 3600

Monitoring the complete flow

Fabric Monitoring shows notebook status, duration, and execution details. DataCoolie writes dataflow-level logs and watermarks to lh_etl, allowing DataCoolie Studio to display metadata, assets, lineage, jobs, and individual dataflow runs across all three stages.

Result

The completed pipeline has 31 incremental Bronze flows, 31 key-merged Silver tables, and six Gold products. The runner stays generic; metadata defines the tables, watermarks, merge keys, paths, and SQL transformations.

This separation makes the pipeline easier to extend and keeps the hybrid on-premises/Fabric workflow observable as one system.

Calendar visual showing events across multiple dates

maurcoll — Mon, 14 Sep 2026 10:25:34 GMT

Hi
I need to create a calendar style visual where I can see events and the staff needed for each event.
I have a start date and end date for each event similar to the below

Event	Start Date	End Date	Staff required
event 1	01/09/2026	03/09/2026	10 staff, 1 supervisor

I have joined to a calendar table on the start date.
I need it to look similar to the below with a date slicer so I can look going forward

01/09/2026

event 1, 10 staff 1 supervisor

event 2, 5 staff

02/09/2026

event 1, 10 staff 1 supervisor

event 3, 20 staff, 2 supervisor

03/09/2026

event 1, 10 staff 1 supervisor

event 3, 20 staff, 2 supervisor

Issue Export Summarized Data & Fields Parameter

pinellus — Mon, 14 Sep 2026 10:09:08 GMT

Since this morning, users can no longer export "Summarized data" from a matrix visual. The matrix uses three Field Parameters (on Rows, Columns and Values) to let users dynamically choose the fields to cross-tabulate. No changes were made to the report or the semantic model. The following error appears:

"Couldn't create the file. Generating the query for the Export data operation resulted in an error. Verify that the visual contains measures from more than one table, because in that case an error may occur in the data export operation."

Impact: All users of the report are affected. Export "Data with current layout" still works, so the issue is specific to the summarized-data query generation.

Expected: Summarized-data export used to work with this same visual until 11 Sep 2026.

Note: This appears to be a service-side regression in the summarized-data query generation for visuals using Field Parameters with measures from multiple tables.

Are we the only ones with this problem??

Have any of you come across this problem as well?

Refresh Failed

ArchStanton — Mon, 14 Sep 2026 08:01:14 GMT

Hi,

My reports have been refreshing every night for several years without any problems until today, this is the error message I get:

I'm not very technical and so I hope the fix is easy and straightforward, can anybody shed some light on why this has happened and how to fix it please?

Thank you!

Best Practices for Ingestion Logging and Metadata Management in Microsoft Fabric

RMori95610 — Mon, 14 Sep 2026 06:35:14 GMT

Hi Fabric Community,

We are building a data platform in Microsoft Fabric to ingest Salesforce and Marketo data into a Lakehouse.

We are currently planning to use the following medallion architecture:

Salesforce / Marketo → Bronze → Silver → Gold

Our basic approach is to keep the Bronze layer as close to the raw source data as possible, while performing transformations such as data type conversion, deduplication, JSON parsing, and upserts in the Silver layer.

For Marketo in particular, we are considering using the Bulk Extract APIs to extract data such as Leads, Activities, and Program Members as CSV files and store the raw CSV files directly in the Files area of the Bronze Lakehouse.

At the same time, since we plan to run incremental ingestion through a daily Fabric Pipeline, we are wondering whether we should separately record ingestion metadata for operational monitoring, troubleshooting, and reruns.

For example, we are considering storing information such as:

Dataset name
Pipeline Run ID / Batch ID
Extraction start and end timestamps specified in the source API
Timestamp when the data was successfully stored in Bronze
Source file name/path
Number of records ingested
Processing status (Success / Failed, etc.)

One idea is to create a separate Ingestion Log / Control Table in the Lakehouse and insert one record per dataset for each Pipeline run, for example:

run_id	dataset	extract_from	extract_to	ingested_at	record_count	status
RUN001	MarketoActivity	2026/09/13 09:00	2026/09/14 12:00	2026/09/14 12:08	15,230	Success

I would appreciate your advice on the following questions:

When implementing scheduled incremental ingestion using Fabric Pipelines, is it common or recommended to maintain a separate ingestion log/control table like this? Or are Fabric Pipeline run history, Monitoring Hub, and other built-in monitoring capabilities generally sufficient, making a separate table unnecessary?
Should technical metadata columns such as ingested_at or batch_id be added directly to the raw data in the Bronze layer? Or is it better practice to keep Bronze as an unchanged copy of the source data and manage ingestion metadata separately in a control/log table?
When storing raw CSV files directly in the Files area of a Bronze Lakehouse, as in the case of the Marketo Bulk Extract APIs, what is the recommended way to associate each file with its ingestion metadata? For example, we are considering recording the file name/path and Pipeline Run ID in the ingestion control table.
From the perspective of reruns, failure recovery, and detecting missing data, what would you recommend as the minimum metadata that should be retained?

At this point, we are not planning to maintain a separate watermark control table. For data such as Marketo Activities, we are considering using a time-based extraction window with a small overlap to reduce the risk of missing records around extraction boundaries or due to short processing/API availability delays.

If anyone has implemented a similar ingestion architecture in Microsoft Fabric, I would greatly appreciate any recommendations, best practices, or examples of how you manage ingestion metadata in practice.

Thank you in advance for your help!

Connection error while using dataflow in power bi desktop

MostVIP2023 — Mon, 14 Sep 2026 03:22:20 GMT

Hello experts,

When I try to connect the dataflow in desktop,it shows below error, would you pls advise me how to solve it?

ZigZag pattern as new Column for ID

damit230183 — Mon, 14 Sep 2026 02:26:30 GMT

Hi,

I am looking for ZigZag pattern for the report,

I have this

I would like to show table like this

Thanks

Power BI Proライセンス未保有者でも共有BIが見れる件

SB樋川幸絵 — Mon, 14 Sep 2026 01:43:46 GMT

現在組織でPower BI Proライセンスを複数所有しています。

Proライセンスを保有しているユーザー同士は作成したBIのWEB閲覧が可能だと思いますが
Proライセンスを所有していないユーザーでも一部閲覧が可能になっています。（一部のみ）
以下パターンが発生している状況ですが、原因や対策など教えてください。

①Pro保有者が部署メンバーへ作成済みBIを公開＆共有（Pro保有A、ProなしB、ProなしC）
②Pro保有AとProなしBは閲覧できた
③ProなしCは閲覧できなかった

New board topics in Microsoft Fabric Community

function logical error

why did i have to go thru the rest connection's properties again on my pipeline's copy job

Exrtract all workspace lineage list in service

view 'my posts'

Power BI Theme Gallery Redirecting to an Incorrect URL

How to add RLS on top of FUAM datasets

AdminCartograph: a Power BI custom visual for multi-layer subnational maps.

AdminCartograph: a Power BI custom visual for multi-layer subnational maps.

The problem

What it does

Under the hood

Docs

Two way slicer Selection

On-Premises Data Gateway Deprecated Warning – Looking for Step-by-Step Upgrade Guidance

Analyze feature in Power BI embed link

How to automatically export a PBI screenshot for the latest month?

From On-Premises SQL Server to Microsoft Fabric with a Metadata-Driven Medallion Pipeline

Architecture

One metadata file, three stages

Uploading the artifacts with Fabric CLI

Stage 1: SQL Server to Bronze

Stage 2: Bronze to Silver

Stage 3: Silver to Gold

Monitoring the complete flow

Result

Further reading

Calendar visual showing events across multiple dates

Issue Export Summarized Data & Fields Parameter

Refresh Failed

Best Practices for Ingestion Logging and Metadata Management in Microsoft Fabric

Connection error while using dataflow in power bi desktop

ZigZag pattern as new Column for ID

Power BI Proライセンス未保有者でも共有BIが見れる件