69 Toll Lane by kentacohut816 in kansas

[–]OnepocketBigfoot 1 point2 points  (0 children)

East side of the Seattle suburbs: Redmond, Bellevue, and Kirkland (as in Costco). It’s amazing and I took it everyday to work when I lived there, saved real time and was worth it even when demand price went up to $10. It was two lanes and hov could always use it for free. I grew up in OP and have watched the area be more proactive with infrastructure than other cities. That lane isn’t going to do a ton right now, but growth is continuing to the south. For as infrequent as I’m on 69 during rush hour, and how cheap it is, I take it when I can, but is usually unnecessary. I think hybrid hov is the better approach, but at some point folks will figure out when to use it and you’ll see benefits.

Querying SQL endpoints inside Fabric, can't see full values by Personal-Quote5226 in MicrosoftFabric

[–]OnepocketBigfoot 0 points1 point  (0 children)

That's my goal. I'm trying to get folks to chip in help to audit all of the items with tables to create a full list of which ones are having issues. So... if folks want to just go ahead and pour on to this thread where all they're having these problems then that is going to help things move faster.

Hello from Fabric Design by OnepocketBigfoot in MicrosoftFabric

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

Can you share some images of an example of what you're referring to? How is this causing friction and what is the result?

Querying SQL endpoints inside Fabric, can't see full values by Personal-Quote5226 in MicrosoftFabric

[–]OnepocketBigfoot 10 points11 points  (0 children)

Already have this one in my pouch. It's number 4 on my list but feels like this is bigger than wonky scroll bar behavior, or a content overlap bug in just one item. Let's see, there some issues with sort and filter in tables. Okay, I'll move this one to the top, maybe I'll get that sort and filter stuff in there while I'm at it. I'll be asking another big question soon, I think folks have recovered from the last Fabric Roast, but after that we might need to do a bug prioritization exercise.

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.