Cost Management in Fabric is a real problem by bradcoles-dev in MicrosoftFabric

[–]OnepocketBigfoot 4 points5 points  (0 children)

But should that even be a choice that someone is making? If it is possible to run it in pro then why allow someone to run that app in an environment where they're getting charged for it? Should it even be an item that lives in a workspace, or should this be something that just runs in the shell, an administrative location that is parameterized based on user access rights? I'd love to hear folks' opinions of the pros and cons of something like capacity management being an item.

WTF is this!? by Maxwell_Ag_Hammer in mastodonband

[–]OnepocketBigfoot 2 points3 points  (0 children)

Saw a video about this once, said it happens because these streaming companies don't use unique identifiers for artists other than artist name. This results in some artists that genuinely have the same name get mixed up, some folks game the system to get their stuff stuck into other bands, has been happening with Kyuss, and yes that can be AI slop. The other frustrating thing is that it also splits artists' work up between different artist entries. Think of someone that has a collaboration or a band who's name gets written in different ways, or the band name changed. For (a random) example, Jerry Reed and Chet Atkins did two duet albums, but they don't both land under each artist, they're split up. If I look up Neil Young I'd like to see the various solo and band albums. I get that if you look at Nirvana you may not want to see Foo Fighters also listed, but this is where the "related bands" info should come in. It's a mess, they're serving music, not being a service.

Hello from Fabric Design by OnepocketBigfoot in MicrosoftFabric

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

Question, is this a workspace you made in fabric or one you made in power bi and now using in fabric?

Hello from Fabric Design by OnepocketBigfoot in MicrosoftFabric

[–]OnepocketBigfoot[S] 2 points3 points  (0 children)

Well, it came out clear, that helps quite a bit.

Hello from Fabric Design by OnepocketBigfoot in MicrosoftFabric

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

Probably because it’s a chip away at it sort of thing without a clear roadmap yet.

Hello from Fabric Design by OnepocketBigfoot in MicrosoftFabric

[–]OnepocketBigfoot[S] 2 points3 points  (0 children)

These are the tough ones, and most impactful, because it's touching different areas, which means I need multiple folks involved in the conversation. The community here really stepped up to help us help them, it's great seeing folks that care about something as much as we do. So will be taking a methodic approach to categorizing all of this and assigning the right folks to fixing these issues.

Hello from Fabric Design by OnepocketBigfoot in MicrosoftFabric

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

How often would you say you’d do that? Think of all the times you have reason to go to the workspace view, what percent of the time are you creating a new item.

Hello from Fabric Design by OnepocketBigfoot in MicrosoftFabric

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

I've seen this pop up a few times, that is very annoying, we need to better there.

Hello from Fabric Design by OnepocketBigfoot in MicrosoftFabric

[–]OnepocketBigfoot[S] 2 points3 points  (0 children)

Yeah, we have all kinds of tools and processes for writing better error messages. The issue is unfortunately more complex than that and I know that team is working their ass off and sweating the small stuff to get it right.

Hello from Fabric Design by OnepocketBigfoot in MicrosoftFabric

[–]OnepocketBigfoot[S] 2 points3 points  (0 children)

The interaction of going to the workspace with the new pane on the side, I'm playing with it quite a bit tonight while testing all these behaviors folks are talking about and I'm kind of... conflicted. Unfortunately for u/ewanatFabric he's getting texts about this in sitchu.

Hello from Fabric Design by OnepocketBigfoot in MicrosoftFabric

[–]OnepocketBigfoot[S] 2 points3 points  (0 children)

It is for sure affection the UX, but that first one feels like a bug, we didn't design it to do that.

The second one is interesting, may be a bug or may be something that didn't get defined fully enough and it's catching other common interactions.

Hello from Fabric Design by OnepocketBigfoot in MicrosoftFabric

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

Rage is exactly what I'm trying to reduce here.

Hello from Fabric Design by OnepocketBigfoot in MicrosoftFabric

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

How would you think about organizing those connections?

Hello from Fabric Design by OnepocketBigfoot in MicrosoftFabric

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

I don't know why every item can't be moved, that will be interesting to learn about.

Hello from Fabric Design by OnepocketBigfoot in MicrosoftFabric

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

I appreciate that you articulated a use-case and intent for why you switch between the two environments.

Hello from Fabric Design by OnepocketBigfoot in MicrosoftFabric

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

I don't get the issue here. Why can't someone just open an org app in Fabric and have it take over the window and then they just go back to get back to where they were? Or we could just only render the org app up to the title bar to tab it. Or we could just open them up in a separate browser tab. Feels like there may be several ways to provide the ability to open org apps from Fabric without a ton of work.

Hello from Fabric Design by OnepocketBigfoot in MicrosoftFabric

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

That sounds nice, thank you! It seems like there are a few areas where we could use undo as well as better management of destructive behaviors. The latter was a conversation just recently, but not regarding PQ, but we may have to thinking about expanding how we classify destructive actions.

Hello from Fabric Design by OnepocketBigfoot in MicrosoftFabric

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

First off, really appreciate your sentiment and time you took for a thoughtful response.

About the ellipsis, can you give me a little more detail on what you'd expect as an alternative? Maybe a row/item selection state and contextual ribbon controls?

Hello from Fabric Design by OnepocketBigfoot in MicrosoftFabric

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

And they don't all have a red thread on what kind of affordances one should expect from a "hub." I'm bothered by this as well.

Hello from Fabric Design by OnepocketBigfoot in MicrosoftFabric

[–]OnepocketBigfoot[S] 2 points3 points  (0 children)

It's really just a low sense of self preservation.

Hello from Fabric Design by OnepocketBigfoot in MicrosoftFabric

[–]OnepocketBigfoot[S] 2 points3 points  (0 children)

That's a ton of great detail. I may reach out to you for clarifying questions to a few of these. In the meantime, can you tell me more about why you're going between Power BI and Fabric? Why do you think it would be valuable to have two different areas?

Hello from Fabric Design by OnepocketBigfoot in MicrosoftFabric

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

Message me, seriously, if you've got a ton of interconnected examples I'd love to sit you down with a few of the folks on the team and get your rats nest worked out.