Skip to main content
This is 2026.9 preview documentation. Coverage here is incremental: a page exists only where 2026.9 differs or is newly documented.
This page is the mechanical path from Speckle.GetByUrl to Speckle - Get Tables. For how Get Tables and the 2026.9 3D visual work, see Power BI in 2026.9. For the connector that is available today, see How to use Speckle for Power BI. There is no automatic conversion. Renaming the function in the Advanced Editor is not enough.
Importing the new .pbiviz replaces the old visual in place. The two visuals share the same GUID. Import the new visual only as part of a planned report migration.

​
When to switch

Your report is at risk if all three statements are true:
  • It uses Speckle.GetByUrl.
  • It points to a model URL instead of a specific version.
  • The model will be published with a 4.0 authoring connector.
Version 4.0 authoring connectors publish artifact-only versions. The next refresh then fails with JsonRepresentationUnavailable. Pinning to a pre-4.0 version URL is a stopgap. Rebuild the report if it must keep following new versions.

​
Before and after

​
How to switch

​
Pin a broken report

If the report already fails, pin it to the last version published before 4.0.
1

Open the GetByUrl query

Open Power Query and select the query that calls Speckle.GetByUrl. You should see the model URL in the formula.
2

Pin the URL to a version

Change the model URL to .../models/MODEL_ID@VERSION_ID for the last version that still contains JSON. You should be able to refresh against that version again.
After you pin the URL, the report no longer follows new publishes. Continue the steps below when the report must pick up new versions.

​
Rebuild the queries

Use the existing model URL. Do not rename GetByUrl to GetTables in the Advanced Editor.
1

Open Speckle - Get Tables

Select Get Data, then Speckle - Get Tables. Enter the existing model URL. You should see the Navigator for that URL.
2

Load Objects

Load the Objects table. You should see one row per object, with Object Key, Application ID, and Model Info.
3

Invoke Properties and Relations

Invoke Properties and select only the property columns used by the report. If the report uses graph-backed fields such as levels or rooms, invoke Relations and select those fields. Relate each invoked result to Objects one-to-one using Object Key.
For Navigator layouts, column naming, and M helpers, see Power BI in 2026.9.

​
Reconnect charts, measures, and slicers

Update every report element that references the old table. Check column names. Shortened property paths, numeric collision suffixes, and the Type_ prefix may change table references and calculations.

​
Replace the 3D visual

1

Import the new visual

Import the new .pbiviz from Documents/Power BI Desktop/Custom Visuals. Because it uses the same GUID as the old visual, Power BI replaces the old visual in place.
2

Reconnect the field wells

Bind Objects[Model Info] to Model Info, Objects[Object Key] to Object Keys, existing tooltip fields to Object Data, and the previous category field to Color By. Recreate any color rules from the old visual on the new Edit page.
The 3D visual has no AppSource auto-update channel. Do not import the new .pbiviz into a report you are not ready to migrate.

​
Remove the old queries

Delete the GetByUrl queries after no visual, measure, or relationship references them.

​
Retained functions

Existing M functions remain available. They keep their 3.x contract and only accept the legacy GetByUrl table shape. The connector installs machine-wide. After it is updated, every report on that machine runs through the new binary. Existing GetByUrl queries still evaluate when their target version contains JSON.

​
FAQ

The downstream query steps still expect the old flat table and will fail. Rebuild the query from Speckle - Get Tables, load Objects, and invoke Properties and Relations.
No. Pinning to .../models/MODEL_ID@VERSION_ID is a recovery option. If the report must follow new publishes after a 4.0 authoring connector is in use, rebuild it with Speckle.GetTables and replace the visual.
The new .pbiviz replaces the old visual in place because they share the same GUID. Existing bindings break. Import it only during a planned migration, then reconnect Model Info, Object Keys, Object Data, and Color By.
Last modified on September 2, 2026