Forum Discussion

Ismail_ZA's avatar
Ismail_ZA
Regular Visitor
1 year ago
Solved

Table shortcut to Dataverse - Unable to Load

Hello 

 

I cannot create a table shortcut to Dataverse from a LakeHouse in Fabric.  I get the error below when expanding CDS2.

I've followed eveything in the link provided, but table do not display. 

 

However if I go to PowerApps for the same environment and Tables -> Link to Microsoft Fabric it works fine and all tables are created as shorcuts. But I only wants specific custom tables to be created as shortcuts in the Workspace.

 

I've currently using Fabric Capacity Trial, WorkSpaces are correctly licensed and I have System Admin security role within the environment.  URL for connection is correct and tables in Dataverse have Tracking Changes enabled.  

 

Can anyone please help me with what I'm doing wrong?

 

 

one lake
workspaces
  • Mauro89's avatar
    Mauro89
    1 year ago

    Hi Ismail_ZA,

     

    This is a known limitation right now. Creating Dataverse shortcuts directly from the Lakehouse UI doesn’t always surface all tables, especially custom ones. The “CDS2” error usually points to the connector not being able to enumerate tables from that environment.

     

    A few things to note:

     

    • The Power Apps → Link to Fabric option creates all tables because it bypasses that enumeration step — that’s why it works differently.
    • From the Lakehouse side, only standard entities are consistently visible. Custom tables don’t show, even with correct roles and change tracking enabled.
    • This behavior is the same on trial and paid capacity — it’s more of a connector gap than a licensing issue.

     

    Workaround:

     

    • Expose the needed Dataverse tables via Dataflows Gen2 and load them into the Lakehouse (gives you table-level control).

     

    If this helps you out feel free to mark it as solution. 

    Best regards!

2 Replies

  • Mauro89's avatar
    Mauro89
    Super User
    1 year ago

    Hi Ismail_ZA,

     

    This is a known limitation right now. Creating Dataverse shortcuts directly from the Lakehouse UI doesn’t always surface all tables, especially custom ones. The “CDS2” error usually points to the connector not being able to enumerate tables from that environment.

     

    A few things to note:

     

    • The Power Apps → Link to Fabric option creates all tables because it bypasses that enumeration step — that’s why it works differently.
    • From the Lakehouse side, only standard entities are consistently visible. Custom tables don’t show, even with correct roles and change tracking enabled.
    • This behavior is the same on trial and paid capacity — it’s more of a connector gap than a licensing issue.

     

    Workaround:

     

    • Expose the needed Dataverse tables via Dataflows Gen2 and load them into the Lakehouse (gives you table-level control).

     

    If this helps you out feel free to mark it as solution. 

    Best regards!