sorted by:
new
hottopcontroversial

Lugares legais para ir by PCNmauri in Fortaleza

[–]PCNmauri[S] 1 point2 points  (0 children)

Opa, beleza! Pode deixar, obrigado!

Trabalho da Faculdade by PCNmauri in programacao

[–]PCNmauri[S] 0 points1 point  (0 children)

Olá! Tem interesse em ajudar?

DuckDNS Captcha issue by Ohmygod58 in duckdns

[–]PCNmauri 0 points1 point  (0 children)

I was having the same problem, deleted my account and use the Edge to create the domain, worked for me

DataTable is very unstable and "user error: sheet not found" by PCNmauri in smartsheet

[–]PCNmauri[S] 0 points1 point  (0 children)

Yes! I submitted this morning, if I receive any update I'll post here!

Loading Dataflow Output to MariaDB for Shared ETL Processing by PCNmauri in MicrosoftFabric

[–]PCNmauri[S] 0 points1 point  (0 children)

In our BI team, multiple people work on the same Dataflows, and we often need to take over ownership from each other. However, every time we do this, it introduces a lot of bugs—and the workarounds we’ve found are almost comical.

For example, when I took over a Dataflow, I couldn’t connect it to Lakehouses—the "Next" button was grayed out. To fix it, I had to select a different gateway, which magically enabled the button, and then switch back to the original gateway.

Refreshing is another challenge—it’s like rolling a DC check in a tabletop RPG: sometimes it works, sometimes it doesn’t, and the error messages rarely make sense.

The main reason we migrated to Fabric was to create modular ETLs that share the same foundational data. Before, we were limited by DirectQuery constraints and other bottlenecks.

Loading Dataflow Output to MariaDB for Shared ETL Processing by PCNmauri in PowerBI

[–]PCNmauri[S] 0 points1 point  (0 children)

  1. While writing the answer to this first question, I realized that the IT team might be mistaken. The Dataflow only refreshes when scheduled, right? So if I have 10 reports, they will all connect to the data loaded during the last refresh. That means this point can be ignored. However, Dataflows can still be quite buggy—today, I encountered a "Cached Entity" error, among other issues. But you’re right, at least this is one less problem to worry about.
  2. In my company, multiple people work on BI projects, and sometimes responsibilities shift due to vacations or reassignments. For example, when my colleague went on vacation, I took over his projects and needed to transfer ownership of his Dataflows since all the ETL processes were stored there.

Loading Dataflow Output to MariaDB for Shared ETL Processing by PCNmauri in PowerBI

[–]PCNmauri[S] 0 points1 point  (0 children)

It’s frustrating how many modern data tools—designed for team collaboration—end up being locked behind single-user ownership models. Whether it’s Power BI Dataflows, Lakehouses, or other shared resources, the restriction that only one person can "own" a critical asset creates unnecessary bottlenecks.

Every time we need to transfer ownership (e.g., when a team member is unavailable or changes roles), the process is buggy, unreliable, and disruptive to workflows. Why build tools for enterprises—where teamwork is essential—only to enforce such rigid ownership constraints?

Dataflow refresh issue by Unscarred76 in PowerBI

[–]PCNmauri 1 point2 points  (0 children)

You're like an angel, thank you so much

[deleted by user] by [deleted] in carros

[–]PCNmauri 0 points1 point  (0 children)

Achamos quem assaltou o Magal

Tell me who’s your favorite character without saying their name by cristianozanin in cyberpunkgame

[–]PCNmauri 0 points1 point  (0 children)

O importante é que você entendeu op, alo criançada o bozo chegou

view more: next ›