u/AnalyticsFellow

Hi folks,

We're wanting to expose more of our data structure (semantic models + certain medallion aspects) to end users / business users. We assume a data catalog is the right paradigm here.

1. Who all has something live (or being worked on)?

2. I've heard Purview is more tech-focused and less end-user-friendly, that fair?

3. The only orgs I've spoken to who're doing this are doing very low-tech solutions like a web-hosted Excel file, or PDFs on a site. Are there any vendors that do this very compellingly (and cheaply)?

4. Something we could build ourselves and have it self-managing through Fabric?

Hi folks,

Love the Planner Agent but this is the bane of my existence:

Note: The Planner response explicitly indicates only a subset of tasks was returned, so this report reflects the available Planner data rather than the complete plan inventory.

It basically seems to grab a random 99 tasks and ignores the rest. This severely limits the impact of the agent. Are there any clever scalable solutions here, especially for analyzing large quantities of "Done" work?

*EDIT2: Downstream on this thread, referring to empty strings being displayed as NULLs, a Microsoft employee stated: "We're aware of the problem, and we're following up with an investigation, and fix. This is due to a recent update that added a lot of goodness to the data grid! Thanks for reporting it!"*
So presumably will be resolved soon. Thanks, all!

Hi folks,

Do tables in Fabric Warehouses support empty strings as the sole value of a field?

We're running into problems and I want to make sure we're diagnosing them correctly. We have a script writing to a table in a Warehouse in Fabric. The script coalesces an empty string:

COALESCE(t.FIELD_1, '')

However, we're finding that the above is stored as NULL, even though we're coalescing to an empty string.

Thanks!

EDIT: Screenshot to help illustrate as a select statement. This is more than a display thing, joins are impacted / etc.

https://preview.redd.it/6uxbhs4ztmbh1.png?width=990&format=png&auto=webp&s=a07a3e34deb76ca1e8d500d7947e012242fa22f8

Hi folks,

We're exploring ROI on Cowork but are finding the Cost Management dashboard to remain wildly out of date (or sometimes simply inaccurate). It doesn't consistently know which users have MS Copilot 365 licenses. It Isn't accurately mapping users to their credit limits. And it seems to take many hours for credit usage to show up there, if it does at all.

Anyone else having these problems? Is it possible that this is somehow a misconfiguration issue on our part? If not, I get the sense that the non-AI side of Cowork isn't ready for broad use yet.

Hi, folks,

My Fabric-focused team continues growing, and I'm looking to continue improving my leadership + management skills. There are lots of generic resources, but Fabric (and software like it, I'm sure) brings some pretty unique challenges. For example, having a software platform which is so rapidly evolving makes it difficult to figure out the right level of technical depth to get into-- I feel more in the weeds here than I would be in other IT management contexts. I'm still getting a feel for how much I can responsibly get out of the weeds.

I'm interested if anyone has blogs/book resources specifically for managers/directors/leaders of technical teams, in the fast-paced AI-powered rapid-feature-rollout world we operate in?

Read and loved The Phoenix Project previously, but I feel like it (and books like it) don't quite sync with the modern era.

Anyone have any resource recommendations? Thanks!

Hi folks,

We're slowly inching towards a data meshy architecture (not an easy task in Higher Ed!), but are struggling. We chose to err toward Warehouses instead of Lakehouses because many of the non-IT data experts are still comfortable with T-SQL. But we feel completely hampered because Warehouse 1 in Workspace 1 cannot query a table in Warehouse 2 in Workspace 2.

Let's say the Finance domain has a workspace containing a warehouse, and another division needs to query that table from their own domain/workspace. Best as I figure, they can't. I can pipe the data over, but we don't want that-- we want live querying of tables across warehouses in different workspaces.

This has folks extremely stressed out over here because we're worried we've been heading the wrong direction by using warehouses. Please help! Any insights would be much appreciated.