RE:
Any news on this topic?I can't see it on road map (as other pointed out) but is October 2024 still the expected date?This would be great as it would allow so many ways to interact programmatically with the entire Fabric environment.
RE:
The scenario I'm working with is data-level language translations. I've got all the work done to swap out the column for the correct language based on a slicer/language table, but what I want is to be able to default that slicer to the USERCULTURE value in a DAX measure. That way when a es-ES user visits the page it automatically sets the filter and they do not have to choose a data-translation language. Metadata translations work fine via Translation Builder, but the data-level one seem to require the user specifically choosing a language. Having this feature completed would solve this issue I think.
RE:
This calculation needs a rounding option as well.
RE:
All of what has been said before. I'm trying to build reports that don't break the people using them.
RE:
Yes, in Power Platform Dataflow. Having the ability to publish the Dataflow and not run it will be greatly appreciated. We have multiple Environments and when we promote our code to new environment, we have to publish each Dataflow - this way it will run automatically through a power flow. As we do not have access in Prod environments, and we use flows to turn the dataflows on. If the dataflow publishes and runs, it breaks the data in the backend. We cannot just limit it to 1 row and publish, as that is what will run each time the flow runs in the future from Power Automate Flow. Publish later doesn't work due to it will fail to run from Power Automate if not already published the correct version.
RE:
I don't think it's gone, it's inconsistent.Most items: Colour only. A few options (e.g. shape fill): Colour and transparency.Rare item (e.g. Title background colour): Colour with "no fill" as an option.I can see why this may not generally be appropriate for text colour options, but any background colour option should have "no fill" offered if transparency isn't.
RE:
This would be a much needed change as more orgs are looking to the Power BI Suite, including Report Builder, to replace SSRS for internal stakeholders.
RE:
I have some SVG columns in my report. They do seem inefficient, having to store a lot of SVG in the model.One trick I do is generating a bar per-row, then having a measure which combines the bars together into a single visual. This gives two presentations of the data (a single bar or several bars together) based on context. Therefore, being able to compose these functions towards a full SVG is important.In one report, I had a matrix with completely custom SVG cells. I was never happy with it. I wanted to customise the total cells to give overall values for the appropriate context (row, column, matrix) but combined with field parameters it didn't ever work. It seems visual calcs give an easier path to detecting total context, so combined with parameter support in visual calcs, this would provide a path to this kind of visual.
RE:
I totally support this request. Not having gateway connections in Power BI Report Builder with Power Query has made it hard to work with on-premises data. Adding this feature would make reporting much easier and let us fully use our current infrastructure. It’s a needed upgrade for anyone working in hybrid environments.
RE:
I don't know if commenting adds any visibility to an idea, but THIS! I have several dashboards with sources that refresh overnight and additional sources with live data that we connect to and refresh multiple times a day. It would be INCREDIBLY more efficient if we could choose to update all sources during the first refresh and then only the live source(s) during any intra-day refreshes.