on
RE:
*This should be corrected so that the visual places employees in the correct location when a city name exists in multiple states.
RE:
Agreed. Having the ability to govern what gets propagated via shortcuts would be a massive help and also work toward a better "OneCopy" approach to data in OneLake. In cases where you want certain lakehouses/workspaces to only house specific data, the only current option is to basically duplicate data into a lakehouse.
RE:
Can't seem to find this very simple feature anywhere in PowerBI. Why is this marked as completed?
RE:
+1 for me too. I need to connect to my CMDB ( Spider) API, the authentication token is return within the response header. Since only a subset of the header is return, I have to create a custom connector to authenticate to the API and download the information into PowerBI.
RE:
Great idea. Tangicloud will add this as an option in our Excel,Import App.
RE:
good topic.
RE:
Sorry, it turns out there is a possibility to change the settings in the Power BI Tentant settings. With that, the above described restriction is solved.
RE:
Madness this has never been implemented. I just don't understand. It's been the number one thing I've been wanting for years and years. Neither myself nor my customers want variably width-ed columns on a matrix or table. It creates visual noise. It's bad. .... let alone having things then RE-size when someone drills down, so they have to spend time figuring out what has only changed visually and what has changed numerically. I have already wasted far far too much of my lifetime resizing columns to be evenly spaced. Only for it to all be lost when I change the measure on the viz. This is so very obvious.
RE:
For more details on the current behavior, incl. screenshots, and a basic Power Query implementation, please see https://community.fabric.microsoft.com/t5/Developer/Functions-in-Navigation-Tables-for-Power-BI-Custom-Connector/m-p/4278119/highlight/true#M58227.