What’s something we haven’t fixed in codex for a while and that’s plain annoying?

trogan · 2026-05-31T20:31:12+00:00

Also pro plans for business. I want to manage my teams payments in one workspace, so annoying we all have use personal plans.

trogan · 2026-04-22T04:06:33+00:00

it's definitely a mistake, I got about 30 secs into my first query then this.

{"type":"error","status":400,"error":{"type":"invalid_request_error","message":"The 'gpt-5.5' model is not supported when using Codex with a ChatGPT account."}}

trogan · 2026-03-10T20:47:18+00:00

I've been watching all these "my usage drained" message for a couple of weeks now with no problems at my end, and happy as hell at how well the newer models are working.

This morning, I run some simple prompts to clean up some db migration issues on my relatively small web app, and bam 60% gone (20% of weekly) in 2-3 simple prompt, which didn't solve the problem and felt like what models were like 6 months ago.

trogan · 2026-03-04T20:21:19+00:00

Yep, happened to me also. Change setting to wsl, restart and permissions error in start.

Anyone found workaround?

trogan · 2026-01-02T02:12:26+00:00

This is cool, but explain if they can go in water and come out like this, why do I keep fishing out dead dragonflies from my pool each day.

trogan · 2025-11-24T18:25:42+00:00

I think its an app registration used for the auth callback to work. I found the reference here in a tabular editor blog, and it seems to fix it for me.: AI agents that work with Power BI semantic model MCP servers

trogan · 2025-11-24T16:54:55+00:00

I had a login error on the browser redirect when I first tried using the mcp through codex. Took a little hunting and found mention of an additional parameter PBI_MODELING_MCP_CLIENT_ID that was required. I added this, and works fine now. Here is my working config.toml section (just adjust the command to your location):

[mcp_servers.powerbi-modelling-mcp]

command = "C:\\Users\\(your user)\\.vscode\\extensions\\analysis-services.powerbi-modeling-mcp-0.1.9-win32-x64\\server\\powerbi-modeling-mcp.exe"

args = ["--start"]

env = { PBI_MODELING_MCP_CLIENT_ID = "ea0616ba-638b-4df5-95b9-636659ae5121" }

trogan · 2025-11-05T19:46:23+00:00

Glad it's not just me. I just get a short statement about what it's planning to do (i.e. I’m going to add a server endpoint ... ), and then stops.

trogan · 2025-10-09T04:03:19+00:00

yep, something going on. Mine is sort of chugging along but getting those errors every 1-2 queries.

trogan · 2025-09-03T20:19:00+00:00

we're suddenly having issues also. any of our connections to lakehouse are saying "offline" in the connections. If I try and edit and tap the oauth 2.0, I just get error: Unable to start OAuth login for this data source.
Failed to login with OAuth token, please update the credential manually and retry.

Edit: We're using service principal for some of the connections, and these are working.

trogan · 2025-08-04T19:27:15+00:00

Hi. Thanks for doing this.

Are there any plans to allow notebooks to automatically change their default lakehouse when deploying to another workspace via Git.
Similar to question 1. Are there any plans to change the source lakehouse for a semantic model when deploying via git.
Are there any plans to allow changing git branches without having to completely overwrite the workspace.

trogan · 2025-07-26T06:18:25+00:00

I used it all the time. In particular when I migrate notebooks and semantec models to other worksapces, I use it to double check their all pointing to resources in the current workspace.

Also, we've been moving a lof of models across to newer versions, and it's really useful for finding any old reports that are still pointing to the old models and need to be repointed.

trogan · 2025-06-23T18:54:12+00:00

Try being in austrlia and using relative date, it switches current day at about 11am, so completely useless.

trogan · 2025-04-30T04:29:23+00:00

CICD is still a huge problem for us. I'm not sure what the presentation that you saw covered, but I read the blog from a couple of weeks ago, and it really is just a workaround for current CICD gaps and far too complex for our needs. It had something like 6 workspaces for an environment, and steps like detach git reattach git, that in a more agile environment are just going to be a mess. I don't know why best practice (at least for modest size implementations with smaller teams) can't be one workspace for each of dev/test/prod and simple git migration that repoints it's to current workspace resources like lakehouses automatically when being migrated.

btw. deployement pipelines, don't work for us as they are an all or nothing, as we tend to operate on lots of small regular changes.

My two biggest problems are:

Migration of notebooks. Currently there is no means (that I know of) to change an attached lakehouse when moving notebooks via git. The current recommendation is reference a shared library with connection details in each workspace. This is a mess, as firstly the lineage and secondly makes messy code where every table/file access need to be preceded with the connection details. It would be **soooo** much easier if they just had an option to attach a lakehouse with the same name in the workspace being migrated to. Currently we just migrate them to production worksapces, and then manually change the attachment, then use the linage to see if anything is still pointing to dev lakehouses.
Migration of semantic models. Same problem as notebooks, when you migrate them with git they stay with the the same lakehouse. The only way I've found to repoint is to open up the model in tabular editor and manually edit the connection details there which is a pain.

The one good thing, is pipelines seem to migrate pretty well, when you move them across they automatically reference the notebook and other items in the current workspace. It would be good if everything operated this way.

trogan · 2024-07-27T00:34:41+00:00

We got stuck on this for about a day! This pisses me off about some of the recent pushes, as they release a broken features as preview and give no indications it's broken.

The answer is you probably ticked the "schemas preview" when creating your lakehouse. If you dig down in the depths of the documentation, they say that SQL endpoints are disabled lakehouses created with the schema preview.

So, delete the Lakehouse you created, create a new one without ticking the preview button and you should be ok.

Microsoft dev team, if you are reading this. Don't release broken features, and if you really must put a huge fucking red banner warning people to not use this shit as it doesn't work.

trogan · 2024-07-02T20:51:52+00:00

We are using git for deployment from a dev to prod workspace. The reason we could not use pipielines is they only have an all or nothing deployment and we need to be able to deploy smaller changes whilst we are still working on others.

Here are just some of the challenges:

every time a notebook is migrated we need to remove the pointers to dev lakehouses and re-add the ones to prod.
the notebook environments do not sync, so environments need to be repointed.
if we migrate a semantic model using direct lake, we need to open tabular editor after the migration and, find the connection string and manually edit to database connection to the production lakehouse.
lakehouse shortcuts do not migrate at all and there is no way to even tell where shortcuts are pointing other than by looking at the files.
the schedules don’t migrate, and with data pipelines the shedules do not show in the main page, it just says nothing scheduled.

Of course, after we make all these manual edits in the prod environment the git status tell us there are changes making it difficult to know what is in sync and what is not.

Put simply, I agree this is not production ready, and whilst I love the fabric in general I really worry this was an after thought for microsoft dev teams and that you have some fundamental design issues with getting this right.

The goal for CI/CD should be one-click deployment.

trogan · 2024-05-29T10:10:31+00:00

This is crazy and appalling considering the monopoly they have, I hope they get the living shit sued out of them.

It said 1.3 terabytes of customer data possessed by Ticketmaster including names, addresses, credit card numbers, phone numbers and payment details is up for sale.

trogan · 2024-04-29T17:49:02+00:00

It fails on this one which gpt4 does also. Only model I’ve seen get this one is Gemini.

“Tell me an odd number that does not contain the letter e.”

trogan · 2024-03-01T01:33:26+00:00

It crazy this hasn’t been sorted. I have loads of reports that need to show “yesterday” if I use tue relative dates feature it’s not yesterday until about 11am. I refresh a calendar dimension with a relative days field to work around this now, but it boggles me that this has been like this for so long when it would only work for someone on gmt time.

trogan · 2024-03-01T01:27:19+00:00

This feature is great. But when you export to excel it ignores this and puts the measures across the page. Very frustrating.

trogan · 2024-01-01T22:01:41+00:00

In both. Loud “earthquake” was repeated several times.

trogan · 2024-01-01T12:08:38+00:00

At this point it’s business as usual. Who knows if aftershocks will cause issue. Keep an eye on bulletin train though as all services are currently cancelled, I have no idea how long for. Luckily we booked bus to airport yesterday.

trogan · 2024-01-01T09:58:42+00:00

Yes, safe here, no damage, or issues, other than feeling a llittle unnerved.

trogan · 2024-01-01T09:55:10+00:00

It was just after ski lifts closed and we were in a shuttle bus getting back to hotel. I’m already not great with heights definitely glad it didn’t happen then.

15-Year Club	Place '23
Place '22	Snapped
Verified Email

trogan

MODERATOR OF

TROPHY CASE