Table from shortcut to dataverse table is not showing up in sql endpoint

[wilson_smyth]

I have a lakehouse with tables created via shortcut to dataverse tables.
A few weeks ago the shortcuts just stopped working, could not be queried in lakehouse or sql endpoint.

deleting and recreating the tables in the lakehouse resolved the issue in the lakehouse but not the sql endpoint.

Ive tried deleting and recreating the shortcut table in the lakehoues a few times and waiting, in case it needs overnight to update the sql endpoint but this has not worked.

Appreciate any advice

[v-prasare]

We are following up once again regarding your query. Could you please confirm if you have shared ideas with Microsoft?

If the you have any progress, we kindly request you to share the resolution or key insights here to help others in the community. If we don’t hear back, we’ll go ahead and close this thread.

Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.

Thank you for your understanding and participation.

[v-prasare]

Hi @wilson_smyth , As we haven’t heard back from you, we wanted to kindly follow up to check if the issue got resolved? or let us know if you need any further assistance here?

Thanks,

Prashanth Are

MS Fabric community support

[wilson_smyth · Accepted solution]

Annoyingly, this resolved itself after about 2 months meaning:

• we dont know the cause
• we dont know the resolution should it happen again.

Its making us question if Fabric is production ready for us as we see more than a few transient issues like this that magically resolve themselves.

[v-prasare]

Hi @wilson_smyth,

Thanks for actively participating MS Fabric community support.

It’s completely valid to be concerned when an issue resolves unexpectedly, leaving no clear understanding of what went wrong or how to prevent it in the future. While transient issues can occasionally occur in distributed systems, I agree that having more predictable behavior is key to production readiness.

To help the Fabric product team better understand and prioritize improvements, I kindly encourage you to submit detailed feedback on the Microsoft Fabric Ideas forum. Sharing specifics like the impact, duration, and how it affected your confidence in using Fabric will go a long way in shaping future reliability improvements.

We truly value your insights, and your input is critical to helping make Fabric more robust and production-ready for all users.

Thanks,

Prashanth Are

MS Fabric community support

[v-prasare]

Hi @wilson_smyth,

Please refer to similar thread solved in community and let me know if this helps?

https://community.fabric.microsoft.com/t5/Service/Fabric-Lakehouse-vs-SQL-Analytics-endpoint/m-p/375...

Thanks,

Prashanth Are

MS Fabric community support

[burakkaragoz]

Hi @wilson_smyth ,

When you create a shortcut to a Dataverse table in a Lakehouse, it should eventually reflect in the SQL endpoint, but there are known delays and sometimes sync issues. Recreating the shortcut usually helps on the Lakehouse side, but the SQL endpoint might not always pick it up immediately.

A few things to try:

• Make sure the shortcut is created in a supported format (Delta/Parquet)
• Check if the table appears in the INFORMATION_SCHEMA.TABLES view of the SQL endpoint
• Sometimes a workspace refresh or even publishing a small change to the Lakehouse can trigger the sync
• If nothing works, it might be a backend sync issue and worth raising a support ticket

Hope this helps a bit

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.

[wilson_smyth]

thanks for the reply  @burakkaragoz 

• i dont have an option wrt how the shortcut is created. the "wizard" just creates it.
  Note it did work the first time i created the shortcut table, it appeared in the sql endpoint.
  Its only since we deleted and recreated the shortcut tables that the issue has occurred.
  
  Sidenote, we had to delete the shortcut tables as they stopped working, for some unknown reason.
• the table does not appear in INFORMATION_SCHEMA.TABLES
• This has been going on for weeks, lots of other refreshes have occurred.
• raising a ticket requires a microsoft support contract which we dont have.
•  

[burakkaragoz]

@wilson_smyth 

This issue with Dataverse shortcuts not showing up in the Lakehouse SQL endpoint has come up a few times in the community, and unfortunately, there’s no perfect workaround yet—sometimes it resolves itself, sometimes not.

Based on your detailed description and my own experience:

• The sync between Dataverse shortcut tables and the SQL endpoint can be delayed or fail for reasons that aren’t always clear to users.
• Recreating the shortcut usually works for the Lakehouse, but doesn’t always force the update in the SQL endpoint, as you already noticed.
• The table not appearing in INFORMATION_SCHEMA.TABLES means the SQL endpoint metadata hasn’t picked it up.
• Workspace refreshes or small changes sometimes help, but not always.
• This kind of “self-healing” after a long delay is frustrating, especially for production scenarios.

A few practical suggestions:

• If you notice this issue again, try renaming the table slightly before recreating the shortcut—sometimes a new table name triggers the sync.
• Publishing a small dummy change (like adding and removing a test table) in the Lakehouse can occasionally force a metadata refresh.
• If possible, keep a log of when you create/modify shortcuts and when (if ever) they appear in the SQL endpoint—this can help identify patterns or timeframes.
• If you have a support contract, it’s worth raising a ticket so Microsoft can track these incidents.

Unfortunately, for now, there’s no guaranteed fix except to wait or try the above workarounds. You’re definitely not alone—hopefully, with more feedback, the sync process will become more reliable and transparent in the future.

Let me know if you discover anything new, or if you need help with a specific scenario!