Unable to refresh data from table shortcut

Hii Anonymous 

This is a DirectLake limitation, not a permissions issue. DirectLake semantic models currently do not support refreshing tables that come from ADLS shortcuts. While shortcuts work via the Lakehouse SQL Endpoint, DirectLake reads Delta files directly from OneLake and cannot resolve shortcut-backed tables during refresh. This is why normal Lakehouse tables refresh successfully but shortcut tables fail.Materialize the shortcut into a physical table in the Lakehouse, switch the model to Import mode, or use a Warehouse instead. Permissions and workspace identity changes will not resolve this issue.

According to the Microsoft Direct Lake documentation, there are two different Direct Lake modes, and this distinction is what explains the behavior you’re seeing:
https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-overview

1) Direct Lake on OneLake
This mode reads native Lakehouse Delta tables directly from OneLake and completely bypasses SQL.
In this mode, ADLS Gen2 shortcuts are not supported, because Direct Lake validates physical Delta files stored in the Lakehouse. Shortcuts fail this validation and cause refresh errors.

2) Direct Lake on SQL (Analytics Endpoint)
This mode uses the Lakehouse SQL analytics endpoint to discover and validate tables.
It can work with objects exposed through SQL, and can fall back to DirectQuery when needed. This is the mode referenced in the documentation when SQL endpoint support is mentioned.

If your semantic model was created in Direct Lake on OneLake, shortcuts will fail even though they can be queried via SQL. 

How to check / choose the mode
The mode is determined when the semantic model is created:

• Creating the model directly from Lakehouse tables → Direct Lake on OneLake

  • Go to the Lakehouse, select New semantic model, and pick tables directly from the Lakehouse explorer

• Creating the model from the Lakehouse SQL analytics endpoint or a Warehouse → Direct Lake on SQL

  • Get data → Fabric → Lakehouse SQL endpoint

If shortcuts are required, verify which Direct Lake mode your model is using and recreate the semantic model using the SQL analytics endpoint, or materialize the shortcut into a native Lakehouse table.