Disable New table and Column for Semantic Model in Fabric

[ayoveral]

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 · Accepted solution]

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-limitatio...

• 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 · Accepted solution]

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.

[SaiTejaTalasila]

Hi @ayoveral ,

You can go through this article -

https://data-mozart.com/migrate-existing-power-bi-semantic-models-to-direct-lake-a-step-by-step-guid...

I hope it will be helpful

Thanks,

Sai Teja 

[ayoveral]

Hi! , it's a Power BI services Fabric semantic model. The conection to other tables is via Diret Lake but before I was able to create a table as seen in the image ( MEDIDAS )

[mariussve1 · Accepted solution]

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-limitatio...

• 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 🙂

[orlandoramirez]

Hi. I'm facing the same situation. In my case the semantic model was created directly in Fabric, not through PBI Desktop and the only source is a data warehouse. The option was available for some time and even we were able to create one table (see image below), but then it got disabled a couple days ago along with the "new column" option. We need to create several calculated tables to avoid creating views in the datawarehouse as those generates warnings about performance and we don't have other ways to solve what we need.

[valentinpl1993]

Hi, I have the EXACTLY SAME PROBLEM as you. Did you find any solution or awnser?

thx

[orlandoramirez]

Hi. No, the problem remains. There's a lot of people saying me that is a limitation and this is not possible to be active. But it was, and it worked. 

[mariussve1]

Hi,

Are you using Power BI Desktop? If so, could you please screenshot the whole pbi window?

Is the data tab also disabled? Is the connection live connection to a dataset? Please provide some more info

br

Marius 🙂

[valentinpl1993]

Hi, I'm having the same issue.

My report is connected by Direct Lake. I used to be able to create tables and columns (see image 1, I created the table "m_MEDIDA" in Power Bi Service but it says "import"), but suddenly this option has become disabled. I'm no longer able to create tables or columns, and it's quite annoying. I found a workaround by changing the connection mode to DirectQuery, but since my data is large and I need performance, this is not the solution I want.

I need to restore the ability to create tables and columns or at least know if this is a new restriction from Fabric, so I can adjust my workflow accordingly.

In response to your questions, I'm using Power BI Desktop. Here is a picture (see image 2, those I mark with red I created in the semantic model in power bi Service).

The connection to my dataset is a "live connection".

Thanks for your attention, I hope this helps.

Waiting for answers.

img1

img2