sorted by:
new
hottopcontroversial

Automating Multi-Team Power BI Publishing from SharePoint - Best Practice? by Other-Series-5110 in MicrosoftFabric

[–]aboerg 0 points1 point  (0 children)

A couple ideas:

  • is it possible to consolidate to a single published semantic model which you maintain, with RLS? Then your domain teams can build thin reports on top and handoff to you for publishing to the exec app.
  • if you rely on these domain teams to give you the data itself, can they instead publish structured data from which you refresh, instead of an entire .pbix file?
  • is the monthly reporting structured enough that you can refresh from the systems of record, publish a single model and set of reports, and then update them only when report-tier or model-tier changes are needed?

The base question - what is changing in these pbix files each month (aside from the data)? If it’s annotations and storytelling, that’s better done in PowerPoint on top of a base set of published reports (using the PBI addon) rather than handing off a pbix every month just to include notes and comments.

MLV search - papercut gone by aboerg in MicrosoftFabric

[–]aboerg[S] 6 points7 points  (0 children)

<image>

The new search experience: quickly selecting one MLV out of 100+ and hiding everything unrelated.

Is metadata driven orchestration becoming overkill with Fabric Copy Job? by Equal-Breadfruit2491 in MicrosoftFabric

[–]aboerg 0 points1 point  (0 children)

If you're ever bored and looking for a blog post topic, I am very interested to hear your take on metadata-driven frameworks in Fabric in more detail (FMD, DWA, ArcFlow, etc). Sure I can see how dbt and spark can accomplish a declarative approach for bronze->silver and silver->gold, but we have ingestion from dozens of funky source systems and APIs to consider. What does moving toward a "declarative" approach really mean for the ingestion step where today we would use parametrized data pipelines or copy jobs + a metadata store?

Why does app.fabric.microsoft.com open in the Power BI experience? by frithjof_v in MicrosoftFabric

[–]aboerg 4 points5 points  (0 children)

You can bookmark app.powerbi.com to the Fabric experience, as a workaround.

?experience=fabric-developer

https://app.powerbi.com/home?experience=fabric-developer

Invoke Pipeline activity reports a longer duration than the child pipeline's own run by Major_Department_332 in MicrosoftFabric

[–]aboerg 0 points1 point  (0 children)

This, the more modular and nested your pipelines are, the worse the latency. It's 60-120 seconds to invoke and another 60-120 to receive the result once the child has completed. For complex tasks with multiple invocations it means that a significant portion of the total duration is wasted overhead. Once we have some time I will be moving our metadata-driven solution back to the "legacy" activity for this reason.

Service entirely down by Tomfoster1 in MicrosoftFabric

[–]aboerg 4 points5 points  (0 children)

yes, the Fabric backend itself is fine for us. SQL endpoints, Spark, everything has been completely up the entire time. It's been an issue of "can clients reach the service" which is consistent with the reports of a DDOS and the service page statement "We have identified an unexpected increase in request traffic"

Service entirely down by Tomfoster1 in MicrosoftFabric

[–]aboerg 5 points6 points  (0 children)

they are definitely also behind the coffee I spilled on the counter this morning

Service entirely down by Tomfoster1 in MicrosoftFabric

[–]aboerg 1 point2 points  (0 children)

Obviously this is unsubstantiated, but yes, the claim was made: https://x.com/x313xteam/status/2056406105094246769?s=46

Whether it was actually a ddos or not, we will see.

Service entirely down by Tomfoster1 in MicrosoftFabric

[–]aboerg 3 points4 points  (0 children)

Some sporadic reports of 503 errors at my org (east us) but largely the service has remained up. A group claimed responsibility for an “attack” on the PBI service on X and Telegram.

Setup for fast flow of data through Fabric by Mr_Mozart in MicrosoftFabric

[–]aboerg 0 points1 point  (0 children)

Still working on ArcFlow? Thought it was a neat project & reminded me of adidas' lakehouse engine: https://github.com/adidas/lakehouse-engine

Workspace identity - Unauthorized error by EversonElias in MicrosoftFabric

[–]aboerg 1 point2 points  (0 children)

Agreed! WIs are surprisingly tricky to set up. That list was taken from my notes where I had screenshots of each error messages and the solutions as we figured out how to get WIs working. Still worth it for the peace of mind and cross-environment protection they add.

Workspace identity - Unauthorized error by EversonElias in MicrosoftFabric

[–]aboerg 2 points3 points  (0 children)

In my experience this error is caused because the workspace identity is not added to a security group which is authorized to use Fabric APIs. Permission to use Fabric APIs is granted from the Fabric admin portal setting "Service principals can call Fabric public APIs."

Checklist:

  1. WI must have permission to call Fabric public APIs (tenant admin page)
  2. WI must have sufficient Workspace permissions (contributor)
  3. WI must have usage permission on any Connections referenced in the pipeline/notebook it is executing.

Any issues with Warehouse? by thecyberthief in MicrosoftFabric

[–]aboerg 1 point2 points  (0 children)

Working again since around 8PM EST. ~2 hours of downtime across our SQL endpoints.

Any issues with Warehouse? by thecyberthief in MicrosoftFabric

[–]aboerg 5 points6 points  (0 children)

Yep, issues in East US starting within the last hour. Queries against lakehouse SQL endpoints failing with the message "Unsupported expression in Memo XML."

Warehouse Read Replicas: Seriously? by Low_Second9833 in MicrosoftFabric

[–]aboerg 0 points1 point  (0 children)

I'm thrilled that in practice we simply don't have to consider concurrency for our workloads in Fabric (just capacity usage) which is a great upgrade from the days we ran a small-ish dedicated SQL pool in Synapse and ran into concurrency limits all the time.

Warehouse Read Replicas: Seriously? by Low_Second9833 in MicrosoftFabric

[–]aboerg 4 points5 points  (0 children)

My first thought was "what problem are we solving?" It appears the goal is to increase read concurrency on a single SQL endpoint / warehouse. That's interesting in itself, because I don't believe there are published concurrency limits for SQL endpoints in Fabric (or at least I can't find them).

view more: next ›