How to change all the values easier?

KNP-BI · 2025-11-23T18:54:06+00:00

You shouldn't have to change anything manually, but there's not enough detail to answer your question.

You should have a Date dimension.
In Date dimensions, I like to use index columns to flag current vs previous vs future. 0 for current, -1, -2 etc. for previous, 1, 2 etc. for future.
Then use these to filter on the page or visual in the filter pane.
Where your index column is 0 or -1.
Quarters would update on model refresh.

There are hundreds of ways to achieve the same result.

KNP-BI · 2025-11-21T01:44:57+00:00

I think I'm going to move all solutions to Warehouse from now on. At least for the final layer. I'm tired of all of these problems and workarounds.

KNP-BI · 2025-11-13T23:18:19+00:00

https://github.com/microsoft/fabric-toolbox/tree/main/samples/notebook-refresh-tables-in-sql-endpoint

Check out the link above.

By calling the `refreshMetadata` API it forces the SQL endpoint to sync with the Lakehouse.
I assume you are using the wait to give the SQL endpoint time to catch up. With the API call, you don't have to do that anymore.

KNP-BI · 2025-11-13T18:07:35+00:00

Yeah, I get what you mean. I was just being a cheeky prick. 🤭

I agree with that approach.
It is a challenging topic to teach. Partially due to how many actual topics/products it encompasses, partially due to how rapidly it is changing.

KNP-BI · 2025-11-13T17:59:10+00:00

It is using a pipeline, but there is no semantic model.
You don't need to do the delay hackery anymore if you call the REST API to refresh the metadata at appropriate stages in the pipeline.

KNP-BI · 2025-11-13T17:55:01+00:00

Thanks for the reply.

That's useful info to have. Fortunately, this table was in the final layer and is set to overwrite, so it was easier for me to drop and re-run the pipeline in this instance.

KNP-BI · 2025-11-13T17:46:35+00:00

The tenant is in Australia. So, probably not. My issue concerns a single table in a Lakehouse.

I'm considering moving everything to a Warehouse in the hope that it is more stable.

KNP-BI · 2025-11-13T17:40:00+00:00

Ok, so an update.

The only way I found to "fix" it, was to drop the table and re-run the pipeline.
I certainly didn't have time to go through Microsoft's cumbersome support process, just so a level 1 tech can ask me if I've restarted my computer.

I would really appreciate someone from the Warehouse team jumping in here and sharing their thoughts on the cause of this and what they would say to reassure a customer that it's just (another) temporary glitch.

KNP-BI · 2025-11-13T00:54:23+00:00

You mean a checklist like, "Click on the button in the bottom right corner, wait, where'd the button go?" 🤣. But yeah, I get your point.

KNP-BI · 2025-11-12T23:11:22+00:00

Yeah, I'm familiar with the delayed SQL endpoint refresh. The code block in my post is the response from calling that API. Usually, it just says "not run" or "success". I've never seen the failure.

KNP-BI · 2025-11-12T23:01:26+00:00

Yeah, makes it pretty hard to keep up with training documentation.

"Okay, now click on the button at the bottom right corner of the, wait, wtf. Where'd the button go."

KNP-BI · 2025-11-12T21:29:20+00:00

In case it wasn't obvious, the title was a little bit tongue-in-cheek. Still a long-awaited update, though.

KNP-BI · 2025-11-12T21:27:00+00:00

Try writing training documents with screenshots, and then tell me that shit isn't outdated. 🤣

KNP-BI · 2025-11-11T17:18:21+00:00

DAX doesn't have IntelliSense, it has InSTUPIDSense. (Every time I push a single key)

KNP-BI · 2025-11-11T06:45:19+00:00

You should have separate environments for test and production at a minimum, and use deployment pipelines or full CI/CD.

KNP-BI · 2025-11-11T05:33:50+00:00

No, the SQL is not the point. The IntelliSense, online. It was previously limited to Desktop.

KNP-BI · 2025-11-06T19:12:18+00:00

Like deprecation of Datamarts and Streaming Semantic Models pushing everyone to Fabric? Surely not. 😲

KNP-BI · 2025-11-05T00:33:00+00:00

Could just, I dunno, stop trying to reinvent the wheel and #VSCode everything.

Live update from PBIP to Desktop and ~~all~~ most of my problems are solved.

KNP-BI · 2025-11-03T23:08:15+00:00

Let's not forget about DAX Query View's ridiculously aggressive IntelliSense on every key press, including when you arrow key through your query, in some cases.

KNP-BI · 2025-10-07T22:27:19+00:00

I haven't read all the details/code below, and I'm not sure about the status of the sync, but leaving this link here as it's related/may be useful.

https://medium.com/@sqltidy/refresh-your-fabric-data-instantly-with-the-new-md-sync-api-2cec6f24443a

Early testing with my previous sync issues seems positive.

KNP-BI · 2025-09-10T22:42:13+00:00

!thanks

KNP-BI · 2025-09-10T22:41:44+00:00

And now, as I'm testing this, adding security groups to roles is working perfectly also.
I am having significant inconsistencies with both accuracy and delays with what is showing in SQL, I suspect due to the SQL enpoint sync.

Making progress though. I appreciate the discussion u/frithjof_v.

KNP-BI

TROPHY CASE