01One prompt takes your dashboards. Importing Power BI and Tableau files into Databricks went GA. The fine print is where the work lives.
02What happened this week. A seatbelt on the engine flip, a runtime out of support, document extraction with a precision mode, and access control that can tell an agent from a person.
03From Brickster.ai. The distance between a working demo and something you can live with. Plus how one of us became a Databricks Partner Champion, in six languages.
01
📊 One prompt takes your dashboards
AI/BI · Genie Code · went GA August 20
Your dashboards can switch sides
Importing Power BI and Tableau files into Databricks became generally available this week. It shipped, and the docs are refreshingly honest about where it struggles. We read all of them so you can skip to the parts that bite.
The headline first. On August 20, importing reports and data models from Power BI and Tableau with Genie Code became generally available on both AWS and Azure. The command is /importBI: you hand Genie Code a dashboard file, and it builds a Databricks AI/BI dashboard that sets out to replicate your visuals, wired to metric views. Metric views are the catalog objects that hold the business logic, the definitions of revenue, margin, and whatever else your company argues about in meetings.
One caution before anyone quotes the release stage in a planning doc: the notes here have churned. Report import went GA on July 2, a separately named Import BI files entry ran as Public Preview on July 9 and again on July 23, relationship support went GA on July 30, and the August 20 entry covers reports and data models under /importBI. Whether that is one feature changing stages or several adjacent surfaces, it reads as something being rebuilt week to week, which is also an argument for re-checking anything you read about it, including this.
The first practical surprise sits in the file picker. For Power BI it wants a .pbit template, not the .pbix you actually work in, and a template carries no data. Which explains the best practice in Databricks’ own docs: always attach a screenshot of the original, because Genie Code “migrates best when it can validate layout and numbers against a high-quality reference image.” An importer that asks for a photo of the thing it is importing is telling you, politely, how much of the checking still belongs to you. Tableau comes in as .twb, .twbx, .tds or .tdsx, and direct uploads cap at 100 MB.
The second surprise is a toggle. None of this runs until partner-powered AI features are enabled for both the account and the workspace. Plenty of security teams keep those off on purpose. Check yours before you promise anyone a demo.
The third is what happens after the import succeeds. Your new dashboard leans on metric views, and metric views keep their own rules. They cannot be joined: a query that tries fails with METRIC_VIEW_JOIN_NOT_SUPPORTED, and some BI features quietly generate joins on their own, so things can fail that you never wrote. SUM, COUNT, MIN and MAX over a measure are all rewritten to the measure’s own definition, so all four return the same number. And for non-additive measures, the ratios and percentages and anything involving DISTINCT, the docs say grand totals “might display incorrect values.” None of this is hidden. It is documented, plainly, on pages you will want open while you check the result. One more: imported metric views live inside their dashboard until you promote them into Unity Catalog for anything else to use.
A last piece of context makes this GA more interesting than a feature note. Back in April, Microsoft removed the BI compatibility mode option from the Power BI connector to Azure Databricks, the option that let Power BI query metric views directly. Reports that used it no longer function, the sanctioned path is now a native query, and Databricks’ docs point readers at a Fabric Ideas post where you can vote for its return. So the door from Power BI into Databricks got wider this week, four months after the door in the other direction got narrower. Whether to walk through it depends on where your dashboards should live, and “where they already are” is sometimes the right answer. That is our next article: /importBI against real .pbit and .twbx files, what survives the trip, and what quietly does not.
02
📰 What happened this week
The rest of the week, in plain language. Four items, each verified against the release notes rather than the reposts.
Deployment
The bundle engine flip arrives with a seatbelt
Last week we flagged August 26 as the date bundle deployments switch from the Terraform engine to the new direct engine. The calmer detail, published by the CLI maintainers this week: the default flips with CLI v1.14.0, which had not shipped as we went to press, and if migration hits any error your bundle simply stays on Terraform. If your CI pins the CLI version, nothing changes for you until you bump it. The one behavior genuinely worth learning: under the old engine, deleting a field from databricks.yml left the deployed value alone. Under the new one, deleting it resets the value to its default. If you want a value to survive, write it down explicitly.
Runtime clock
Databricks Runtime 13.3 LTS ran out of support on Saturday
Three years to the day after its release, DBR 13.3 LTS reached end of support on August 22. Nothing is scheduled to break: end of support is not a kill switch. What stops is fixes, patches and support. In our experience it is always the oldest, most load-bearing jobs that are pinned to the oldest runtime, precisely because nobody dares touch them. The announcement is not news, only the date is. That is exactly why it makes this list: deadlines do not send a second reminder, and this one just went from someday to overdue.
AI functions
Document extraction grew a precision mode
Two related items. Databricks published a Document Intelligence post on August 18, and a day later ai_extract precision mode went GA. Precision mode targets the hard cases: long documents, high-volume outputs, and schemas that need reasoning, like pulling hundreds of line items off invoices or contract terms scattered across a filing. Our standing advice applies double here: run a costed sample before pointing any extraction mode at a million documents. These functions are metered, and the meter is easiest to forget while the demo is impressing people.
Governance
Access control learned two new tricks
Role-based access control went GA on August 19: people assume a role and work with that role’s permissions only, instead of everything they have ever been granted, which is how you keep one client’s analysts out of another client’s tables when the same person serves both. Two days later, attribute-based policies picked up context attributes, in Beta: row filters and column masks can now key on which client application is calling and whether it is acting on someone’s behalf. That is aimed squarely at telling an agent apart from the human it acts for. Neither changes anything until you write the unglamorous policies that use them.
03
🧱 From Brickster.ai
Every item this week lands on the same line: the distance between a working demo and something you can live with. An importer went GA and immediately handed you a checklist. An engine flip whose most important detail is what happens when it fails. A runtime that aged out on schedule, three years to the day. Access controls that only matter once someone writes the boring policies.
We also published something more personal: How I became a Databricks Partner Champion, and how you can, now readable in English, Japanese, Korean, German, French and Portuguese. If your company is a Databricks partner and the badge is on your list, it is the write-up we wished existed a year ago.
Quick links this week:
→ brickster.ai/articles: The Partner Champion path from the inside, in six languages.
→ brickster.ai/digest/week: The full weekly digest behind section two, with every source we read.
→ brickster.ai/assistant: Ask it whether anything in this issue applies to the setup you are running.
📊 Wondering which of your dashboards would survive the trip to Databricks?
The Brickster Assistant searches our full archive and answers with citations.
