Datamart - Missing Features

[Anonymous]

I'm starting to use a datamart, and noticing the following features are absent (compared to a dataset😞

• The "Model" view of a dataset has the "Manage relationships" button in the toolbar, but is absent from a datamart
• I am unable to create a calculated column in a datamart
• I am unable to create a many-to-many relationship between tables in a datamart

Will these features ever be added to a datamart?

[ibarrau]

Hi. I don't think users of this forum will have answers for that. I can say something like, you are building the datamart so why would you add a calculated column. There is no data problem that can't be solved with a good modeling, sql query + dax measure.

The many to many relationships is not an issue either because you can build them from scratch with a middle table.

You can always suggest your ideas at: https://ideas.powerbi.com/

You can always check the next features for power bi at: https://learn.microsoft.com/en-us/power-platform-release-plan/2022wave2/power-bi/planned-features

I hope that helps,

[lpetty421]

I have the same question as you.  I don't agree with the previous responder to your very good questions.  I expect the datamart to give the full pbi desktop capabilities and "experience" in the cloud environment;  to be able to replace the  desktop, and work as I would on the desktop, without having to know sql.  Which sometimes means calculated dax columns and calculated dax tables.  I know it be done in dataflows, but I expect dax for other functions that work on columns, like switch.

[Anonymous]

Thank you for the reply! I guess one of my hopes was that someone from Microsoft would see this and be able to respond, but if this is not the right place for that, then I can try https://ideas.powerbi.com/ as you suggested.

I agree with all your points. My datamart use case right now is trying to quickly convert a dataset that I recently inherited to a datamart. That means just quickly copying and pasting code from the Advanced Editor and getting it up and running. After that, I can dig deeper and change some of the modeling/queries to avoid calculated columns and many-to-many relationships.