Issue Creating Shortcuts to KQL Database from Digital Twin Lakehouse Output Tables

[Sireesha_r]

Hi All,

I have created a Digital Twin builder for a real-time use case, and I’m now pointing the generated Lakehouse output tables to a KQL (Kusto Query Language) database using shortcuts.

The ontology has been successfully created, all entities have run successfully, and I can see the data present in the tables.

However, while creating these shortcuts, I’ve noticed that some tables are successfully linked, whereas others fail during the shortcut creation process. Unfortunately, there’s no clear error message or detailed log to help diagnose the issue.

Has anyone encountered a similar problem or have any suggestions on how to resolve this?

Appreciate any guidance or support.

Reference Image:

[v-echaithra]

Hi @Sireesha_r ,

May I ask if you have resolved this issue? Please let us know if you have any further issues, we are happy to help.

Thank you.

[v-echaithra]

Hi @Sireesha_r ,

I wanted to check whether you were able to resolve the issue with the provided solutions. Please let us know if you need any further assistance.

Thank you.

[v-echaithra]

Hi @Sireesha_r ,

Thank you @tayloramy  for your inputs.

We’d like to follow up regarding the recent concern. Kindly confirm whether the issue has been resolved, or if further assistance is still required. We are available to support you and are committed to helping you reach a resolution.

Best Regards,
Chaithra E.

[tayloramy · Accepted solution]

Hi @Sireesha_r, 

This pattern (Digital Twin Builder -> Lakehouse ->KQL DB via shortcuts) should work, but there are a few easy-to-miss constraints that often explain why some tables shortcut fine while others fail.

Quick checks

1. Add in batches of 10
   Digital Twin Builder can generate a lot of output tables. In the KQL DB shortcut wizard you can only add 10 tables per pass; add the next 10 after the first batch completes. Microsoft's guide calls this out ("You can only add 10 tables at a time"), and it links to the KQL DB shortcut instructions.
2. Naming/character limitations
   KQL DB shortcuts (and OneLake shortcuts generally) are picky about names/characters:
   • No spaces in Delta table names (discovery can break). Doc
   • Shortcut names/paths can’t include “%” or “+”, and non-Latin chars aren't supported.
   If your entity/table names include spaces, symbols, or non-Latin characters, consider creating a sanitized copy/alias (or a Lakehouse-to-Lakehouse shortcut with a clean name) and point the KQL DB shortcut at that clean path.
3. Create the shortcut from the KQL Database, to the Digital Twin Builder lakehouse ("…dtdm")
   From your Eventhouse’s KQL DB: New -> OneLake shortcut ->Internal ->select your "<twin-name> dtdm"
   Lakehouse ->Tables ->pick a specific table. Then it will appear under Shortcuts and you’ll query it with external_table('YourShortcutName'). See the Digital Twin Builder handoff article here.
4. Shortcut creation quirks
   In KQL DB, shortcuts can't be renamed and are created one at a time (UI restriction).
   Propagation/recognition isn't instant; if a table was just created or is empty, give it a moment and try again. The OneLake docs note recognition delays and limits. Doc
5. Optionally try with acceleration off/on
   If you enabled "Accelerate" during creation and it fails, try creating the shortcut with it off, then enable it after. (Feature is preview; docs: Query acceleration over OneLake shortcuts.)
6. If the UI error is opaque, try the REST API
   The OneLake Shortcuts REST API returns clearer errors (bad path, illegal characters, etc.). Create/list the shortcut there to see the exact failure.

Why this path is supported
This is the exact flow Microsoft recommends for Digital Twin Builder: create an Eventhouse/KQL DB and add OneLake shortcuts for all "dtdm" lakehouse tables, then query with external_table(). Guide 

If you can share one failing table name/path (redact anything sensitive), folks here can sanity-check it against the naming rules above.

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, please mark this post as the solution.