on
RE:
This would greatly help me as I post multiple trade agreements daily, and this would make my job faster and catch errors before posting.
RE:
100% agree. Sometimes terminology changes and it needs to be reflected in the semantic layer. This basically makes it extremely difficult when trying to promote shared semantic models that have dozens of thin reports connected...or any other downstream use of a semantic model Microsoft leverages.Running into this issue now with a dataflow column name change that feeds multiple shared semantic models, and essentially dozens and dozens of reports that need to be modified in the Service; as well as awareness to anyone using those semantic models outside of the Service.
RE:
This has been planned since 2021, and we're currently in 2024. Are there any updates on this?
RE:
This is a very common issue that consultant face in their implementation.As a work around we may use custom Financial dimensions For LC number, as single LC number can not be tagged with multiple PO in D365 F&O
RE:
This is becoming very important, or at last be able to filter by the task labelling or artifact type like in the main workspace screen
RE:
This is symptomatic of a bigger problem in Power BI in which the interface is designed in a way that prioritises marketing a new feature to users above ease of use or accessibility - c.f. popup hints, surveys, splash pages.In general, I would like a "stop using the interface of the product I am paying you money for to market new features at me" option, but that seems pretty unlikely to happen.
RE:
Would love to see this improvement, that AutoComplete only triggers when you begin typing characters. If your attempting to 'well format' your DAX code. AutoComplete is automatically triggered when you hit enter, and then if you hit 'tab' to indent your code, you've just inserted 'ABS()' or 'AddColumns' or pick your first "A*" function that's accessible. Then you have to remove it and and cancel out of the autocomplete suggestion before hitting tab. Adds multiple unnecessary keystrokes for each new lineThis also impacts the new Dax Query view, equally frustrating. Been dealing with this for a while, finally went looking for an opportunity to improve this 'feature'
RE:
This would be a great feature when UAT.
RE:
I like this idea, would deployment pipelines work for this scenario?
RE:
This feature request represents and absolute must-have and core-feature for our implementation project. Would be great to see an estimation for the implementation roadmap.