on
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!!
RE:
6 year later and we still need it!! hahahah it would be great. It's hard for me to understand why in the column chart the option is available but in the bar chart is not.
RE:
This is basic a requirement for so many clients that do not use items. Whilst there are extensions available, out of the box to not be able to accrue received costs seems a like a glaring omission. Nearly every demo I do, the potential client asks for this so get voting!!!
RE:
@Sakshi.JainWhat's the time-frame please? Can you ask for more details please?This issue is obviously affecting many tenants/customers.
RE:
Something that is long overdue and can bring so much benefit to an organisation.
RE:
This tool also should only allow to change translations that are tagged by a change/new in the original label,caption,tooltip,.. or by a manual tag by an admin, because of a wrong translation.I hope this will prevent many erroneous translations done by search and replace.And i think this will reduce the need of automatic translations, because there will not be so many entries.
RE:
Extremly needed - agree
RE:
This issue needs to be actioned as we are manually reclassing all the journals that posted on the wrong GL Code. Just only concerned, why we implemented the bundle products if we never check the GL side of it