Barra de navegación
Cuando tengo un gráfico de barras, por lo general fechas (meses), la barra de desplazamiento podría configurarse para situarse siempre al final o al inicio del gráfico (idea), de tal manera que cuando veo todo el año en los filtros generales, pueda tener en un gráfico mi resumen acumulado y en otro el detalle por mes donde pueda ver siempre viendo el último mes ( desplazado hacia la derecha). Podría usar la inversión de datos, pero por lo general se visualiza de izquierda a derecha cuando queremos ver tendencia.
Semantic model connection bindings should be in source control (Git)
Semantic model data source connection bindings should be source controlled. A semantic model can contain multiple data source references, each of which can be mapped to a separate Fabric data connection. Currently, the semantic model definition is source controlled, but these data source → connection bindings are not. After a Git sync or deployment, the connections therefore have to be mapped to the semantic model again, either manually through Semantic model settings → Gateway and cloud connections → Maps to, or programmatically using the connection binding API. The connection bindings should instead be included in the source-controlled semantic model definition and automatically applied during Git sync and deployment. Preferably, the connection ID should also support Variable Library variables. Since the connection is identified by a GUID, the binding could accept a String/GUID Variable Library value, allowing the same semantic model definition to be used across environments with different connections. The Variable Library would then provide the appropriate connection IDs for each environment. This would eliminate the need for separate manual or programmatic connection-binding steps after Git synchronization or deployment.
Bulk changing column names in Visualizations Pane
We often use raw/api column names or measures with a set nomenclature to be consistent and to keep track of them but we do not want to display these names in the visuals. Currently we have to change the names one by one and once we press enter after changing the name, depending on your model size, it takes between 2-10 seconds to load up. If we have 10-20 columns in a table visual, we have to change the names one by one and wait for it to get loaded every single time. I suggest to include a bulk updating where we can change the names for each field used in the Visualizations Pane for any visual and click an Apply button to load up the changes in one go.Set default x axis scrolling position
Enable selection of the default scroll position for the x-axis on a chart. For example, on a line chart with dates as the x-axis, when not all of the data can display in the view at once, the scroll defaults to the beginning/left end of the x-axis and the most recent dates are at the far end causing the end user to always have to scroll to see the most recent data. If you could set the visual to default to the right end, then the user would only have to scroll if they wanted to see more history.
Table Visual — Rounded Corners and Pill-Style Cell Backgrounds
Add the option to display cell background colors as rounded rectangles or pill-shaped labels within the native Table visual. Currently, applying a background color fills the entire cell with a solid rectangle. I would like the ability to adjust the corner radius and padding, creating a colored background around the value with space between the background and the cell edges. Suggested formatting options: Corner radius: Adjust from square corners to fully rounded pills. Padding: Control the spacing around the value and inside the cell. Background width: Fit the background to the text or use a consistent width across the column. Conditional formatting support: Apply background colors dynamically using existing rules or measures. This would be particularly useful for status values such as On Track, At Risk, and Behind, making them appear as clear, compact badges. It would improve readability and provide a more polished appearance without requiring custom visuals or SVG workarounds.
Add Global Alignment Controls for Power BI Matrix Values and Headers
Please add a global alignment setting for Matrix visuals that allows users to apply the same alignment, left, center, or right, to all measure columns at once. This should apply to column headers, data values, subtotals, and grand totals. Currently, value alignment often has to be configured individually under Specific column, which is very time consuming for matrices with many measures or field parameters. A global alignment option would make matrix formatting much faster, more consistent, and easier to maintain.Case sensitive-insensitive option in Power BI
There should be an option in Power BI for the data in the columns to be either case sensitive or insensitive. When one deals with data involving client names or entity names, case sensitivity-sinsensitivity does pose a problem. There are ways in M query to avoid this, but Power BI should have an option for itself as a PBI feature.
Governed & Regulation for Publish to Web feature
Notifying certain group of individuals if there is any enhancements performed on the semantic model which already hold an active Publish to Web code in place. This ensure in having more security and avoid sensitive/Org confidential data exposed to external audiences. Log analytics to identifying the IP address/location/count of views for the PBI report that was hosted public using Publish to Web. Sensitive labels for Publish to Web generated reports that will restrict even the contributor or above workspace role individuals in changing the data/visuals in the report except for the desired allowed IDs (who can modify like privilege access). If the above points are not feasible, then at-least restricting the external audiences who are consuming the report via Publish to Web URL to only visualize the data projected in the visuals rather having any sort of data exposed that is present in the semantic model.
Access Variable Library in Semantic Models
Enable the Variable Library as a centralized location for storing all environment‑specific variables, allowing us to adjust them for promotion scenarios (e.g., from dev to prod) without relying on deployment pipelines. It would be ideal if semantic model parameters or data sources could reference a Variable Library, similar to how deployment pipelines handle variables today. When using CI/CD Option 1 — Git‑based deployments — it isn’t possible to hardcode environment‑specific values or data sources, since these differ across environments. Example: If I build a report in a dev workspace/branch that uses a dev data source, and then promote it to a prod workspace/branch via PR, I have no way to automatically switch the data source to the production version. I would need to submit an additional PR just to update the prod branch, resulting in the same report with different hardcoded sources.
