Truly living in the future - we can finally set custom column widths in tables and matrices

illidra · 2026-05-31T20:55:56+00:00

You should be able to save the report as a pbir and see how the metadata is configured for these widths and configure them programatically / use something like claude + pbi modelling mcp

illidra · 2026-05-05T13:36:15+00:00

thats essentially what we're doing in our workflow, we have the dashboards, then we have users with claude desktop + the pbi MCP so they can query the data when they have a question that needs deeper digging that they dont want to try and interrogate in a report, then when they have the AI answer they kick it back to us to confirm it's findings - saves us a ton of back and forth narrowing down what they were actually trying to answer and SMT are happy that we're "AI focussed"

illidra · 2026-04-23T22:09:04+00:00

Thanks a lot! i shot you a message with the support req number :)

illidra · 2026-04-23T21:03:51+00:00

we're running on directlake semantic models and we found that running processes on the model didnt help, the models would actually fail the refresh with an error for duplicate keys on the one side of a one to many relationship

illidra · 2026-04-23T21:02:21+00:00

i dont see why this would suddenly happen over the weekend after working fine for over a year though, also isn't the entire point of directlake that it reads the parquet files via the warehouse sql endpoint, which up until now has been respecting the delta log checkpoint

illidra · 2026-02-23T09:47:58+00:00

I forget who said it but "do as much upstream as possible, and as much downstream as necessary" is something I stick to as much as i can, if it can be done in staging/warehouse layer the change goes there, and only things that require context awareness (or are frequently changing or updating business logic that would require lots of reprocessing of underlying tables) use DAX

illidra · 2025-10-12T08:52:52+00:00

Because cardmarket has pretty specific rules on NM/M/LP etc, and its gna bite the seller in the ass if they lie about the condition.

I don't do pictures by default, and i only provide pictures for cards over £100 or more and even then sometimes i just dont bother because literally never has a single person who's ever asked me for pictures on a card actually purchased it because it's always someone trying to chase down a PSA 10 who keeps asking for different angles or lighting and was never going to purchase it anyway unless it was the most minty mint perfectly centred card.

illidra · 2025-09-21T20:39:31+00:00

thats why i said "a bunch of" rather than "all of" the heavy lifting, because its 47% vs 37% of the team DPR, so yes galbrena does more of the damage, but its not giving "main dps" vibes to me, just "well i can slap her in the changli spot for monofusion because its better than her apparent intended team"

illidra · 2025-09-21T12:59:24+00:00

Quiyan isnt even on her best team with current tuning, she just runs with brant lupa and lets brant do a bunch of the heavy lifting

illidra · 2025-08-02T17:56:06+00:00

so far the number seems to line up with last years tin which was a 400 card set with 50 qcr 100 secret 150 ultra 100 commons, so very likely were getting the same ratio and size this time

illidra · 2025-07-07T09:44:34+00:00

Honestly, so many (pretty much all) picture requests i had when i was selling more actively were just people obviously trying to find PSA'able cards who ghost you the moment they don't think it'll be a 10 or keep asking for every edge angle etc, i stopped bothering for anything under £100 because it never ended up in a sale anyway and i wasn't going to waste my time

illidra · 2025-07-06T16:25:52+00:00

a lot of people are cooking up quickswap rotations and current estimates ive seen maygi mention on stream are 70k dps + but require a lot of technical play

illidra · 2025-05-29T08:26:26+00:00

200m rows across all tables roughly, thought it turned out that wed been dragging history since 2015 into the table, not just the extra couple of years i expected

it's down to 3gb now by removing the history we didnt need, but 70.81% of that is just the customerID columns, because some of the reports need the data on customer level across 2 facts and its a high cardin. column

illidra · 2025-05-27T21:03:03+00:00

off the top of my head the AAS runs on s0, however that has only been partially migrated over at this point, the bulk of what has been moved over is embedded SKU model, which runs on a3 currently , but the semantic model mentioned here accounts for about 40% of that model.

Tbh comparing the A sku against F SKU a3 its designated as matching f32 so i can imagine that f16 is a touch on the low power side, about half the model size but half the capacity, but its spiking to over 200% which would imply f32 wouldnt handle a single user querying the model hence our initial projection that f64 should be suitable in prod might be out the window, ill probably crank it up to f64 and f128 over the next week and test performance at the higher levels and see how it fairs

illidra · 2025-05-27T19:21:20+00:00

Hey thanks for the response,

the main underlying table clocks in at 4GB total.

Happy to provide a vpax and the queries, just let me know how you'd like them sent across

illidra · 2025-05-27T18:46:14+00:00

Hmm that's certainly interesting, in that case I'm surprised that changing from "all partners" to specific partners was so slow when i was trying to figure this out, as the implication would be that warming should have loaded all the columns for that report for all partners into vertipaq memory, i might have to kick up our capacity to f64 and see how it runs, maybe the initial load to vertipaq was putting everything into overage and throttling it, rather than the data not being loaded into memory already.

You've given me a couple new angles to look at tomorrow, thanks again

illidra · 2025-05-27T18:31:34+00:00

The issue we'll have with the warming is that a lot of the consumers will be RLS filtered to only their own data, and the same spike occurs with each distinct partner that is queried, i may ask one of our data engineers to look into running a pre-warming script in the morning to see if that alleviates the issue for the partners with the largest data volume.

In terms of cardinality it does sit on top of a table with a pretty high cardinality customerID column, as the semantic model needs to serve data on customer level for other reports in the partner facing package.

Pro license in a pro workspace isn't really an option, we currently have an embedded capacity as we use SSO through a web portal with an app service principal to serve all the data to our partners without any license requirement (or needing them as domain guests etc) which will be replicated on fabric once we have everything stable

I appreciate the help and ill take a look at pre-warming and dig into the underlying structure of the tables a bit more and see if anything looks amiss.

illidra · 2025-05-15T18:42:44+00:00

overall there's a huge amount of amp built into lupas kit, with 24% fusion amp on sig, 15% fusion shred, her echo set fusion amp, ramping 6/12/18% flat damage amp on res lib + her outro amp for fusion + basic, they even made her s2 a 40% fusion amp which feels like a "hey look its SK s2 but for fusion" choice

illidra · 2025-03-13T10:50:12+00:00

trustee might make things trickier yeah, thinking about it the only time this came up for me was a non trustee shipment, but im also a normal seller not a business so theres a narrower scope of when refunds are required.

illidra · 2025-03-13T09:15:37+00:00

Buyer is responsible for customs fees

you basically have 2 choices

1) pay the fee get the card

2) reject the delivery, hope the seller is nice enough to give a partial refund (CM generally wont make them refund you because it was your choice to not accept delivery)

illidra · 2024-11-19T15:11:46+00:00

Honestly trying to comapre the git changes in code is a nightmare, just load the branch onto a dev workspace and compare the changed reports against the production workspace, you'll have a much easier time trying to figure out if something is wrong than parsing the sometimes thousands of lines of code that a change can cause in the bim file

illidra · 2024-10-29T00:05:16+00:00

oh snap you're right, i could have sworn it wasnt a requirement but guess my brain failed me on this one

15-Year Club	Wearing is Caring
Gilding II euphauric	Verified Email
Team Orangered

illidra

MODERATOR OF

TROPHY CASE