Forum Discussion

ayoveral's avatar
ayoveral
New Member
2 years ago
Solved

Disable New table and Column for Semantic Model in Fabric

Hi everyone!    I have a model created in Fabric, previously I could create a table (I use it for meassure's) but now those options are disabled. Why or how can I re-enable it? Thanks a lot. 🙏 ...
  • mariussve1's avatar
    mariussve1
    2 years ago

    Hi again,

     

    Hmmm... seems strange because its a known limitation with direct lake that it does not support calculated tables/comumns:

    https://learn.microsoft.com/en-us/fabric/get-started/direct-lake-overview#known-issues-and-limitations

     

    • Calculated columns and calculated tables aren't supported.

    • Direct Lake tables can't currently be mixed with other table types, such as Import, DirectQuery, or Dual, in the same model. Composite models are currently not supported.

     

    Br

    Marius 🙂

  • Anonymous's avatar
    Anonymous
    2 years ago

    Hi,ayoveral ,orlandoramirez . I am glad to help you.
    Hello,mariussve1 ,SaiTejaTalasila .Thanks for your concern about this issue.

    Your answer is excellent!
    And I would like to share some additional solutions below.
    Here are some of my suggestions and tests.
    First of all for the model, the way to get the data is datalake, a connection that requires a connection from the cloud to the database for querying. At this time, the creation of calculation tables is not supported. At this time for the actual data source does not have the calculation table you created.
    Here is my test
    When the data in the semantic model is in import mode or directquery mode, I can modify the semantic model in the power bi service to create a new calculation table.

    You can see that the functionality is not disabled

    I reproduced the user's action: by creating a datalake and loading the data by connecting to SQL Server

    You can see that New table is disabled

    The import mode and directquery (creating reports by establishing a connection on the power bi desktop and finally publishing them to the service with the correct gateway connection) are not disabled.

    In fact, mariussve1 gave the right answer: the current inability to create calculation tables is a known limitation of Direct Lake, so I would recommend reloading the data in another way than DirectLake if you can, because at the moment, your problem is actually due to a limitation of the datalake functionality (you can try to delete and refetch the data model from the datalake if you can). (If possible, you can try to delete the data model obtained by datalake and obtain it again by other means, please make a good backup of your data to avoid losing important data).

    I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.

    Best Regards,

    Carson Jian,

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.