"default semantic model objects" vs "default dataset objects"

[sam405]

In my lakehouse model view I have both "default semantic model objects" and "default dataset objects" (image below)

Can anyone shed light on the differences of these model views as they relate to editing, and consumption in reports?

I have not found any documentation mentioning both in the same context, but each referenced separately.

In my lakehouse model view the tables context menu shows "add to default semantic model" however many of the recent examples I have found refer to "add to default dataset" instead

image below

[TomMartens]

Hey @sam405 ,

I assume this is a glitch. I recommend you raise an issue.

Regards,

Tom

[Anonymous]

Hi @sam405 
Thanks for using Fabric Community.
When a Lakehouse is created a SQL analytics endpoint (warehouse) is automatically created which also automatically creates a default semantic model (previously default dataset). That is only accessible and editable via the SQL analytics endpoint. This is created as part of the process to immediately allow you to create a Power BI report off the Lakehouse data. The two tabs showing down there are because of a bug. I have informed our internal team and they are aware of this issue. It will be fixed soon.

In addition, you can always create a new semantic model from the Lakehouse/SQL analytics warehouse which is just a Power BI Direct Lake semantic model, using those tables and with much more capability in regards to semantic model authoring features.

Hope this helps. Please let me know if you have any further questions.

[Anonymous]

Hi @sam405 
We haven’t heard from you on the last response and was just checking back to see if your query got resolved. Otherwise, will respond back with the more details and we will try to help.
Thanks

[Anonymous]

Hi @sam405 
We haven’t heard from you on the last response and was just checking back to see if your query got resolved. Otherwise, will respond back with the more details and we will try to help.
Thanks

[sam405 · Accepted solution]

Thanks for pointing out this is a bug.