on
RE:
This is a must have feature
RE:
Microsoft, please get rid of this unnecessary use of resources
RE:
High concurrency mode for Spark job definitions in ADF, same as for notebookshttps://blog.fabric.microsoft.com/en-US/blog/introducing-high-concurrency-mode-for-notebooks-in-pipelines-for-fabric-spark/
RE:
We would like this feature. Any update?
RE:
Must have
RE:
Ridiculous that we even need to point out that this is needed. Give us the power to make things look the way we want them to look, MS.
RE:
This has been under review for 7 years and its still not fixed?
RE:
Thanks for posting! Microsoft, please get rid of this unnecessary use of resources.
RE:
Thanks for posting this. I don't like the default semantic model either. We never use it. We create a new one every time from the lakehouse. I wish they would remove the L shape grouping with the default semantic model and SQL Analytics endpoint as well. It takes up too much real-estate and dirties up an otherwise beautiful organization of items. There are other ways to get to the SQL analytics endpoint. I say get rid of the L shape grouping and access the SQL analytics endpoint through the ... "more options". Or it isn't unreasonable to just access the SQL analytics endpoint using the toggle dropdown in the upper right corner of the lakehouse. Many of us are using SSMS anyway.Or allow users to configure the L grouping option on or off. To us it is very annoying to have many lakehouses in a workspace and it take up this much space.
RE:
Yay. Microsoft has implemented this. You can now add field parameters by opening a semantic in power bi desktop using "Edit" instead of "Connect" and then export it as a Project .PBIP file. Once you do that, you can open the project in Power BI desktop and go to the report view, choose the Model menu tab and then click the Parameters icon. From there you can select Field Parameters. Any edits you make to the semantic model here are live. It's wonderful!!