User Profile
mohit_sakhare
Resolver II
Joined 11 months ago
User Widgets
Contributions
Re: Converting calculated column into parameter
Hi, A calculated column won’t react to a parameter change because it’s only evaluated at refresh time. To make DaysInMarket update dynamically when Parameter 2 changes, you need to convert it into a measure and compute First/Last dates using a row-level condition (based on the parameter), then return the value only for the “last date” row (same behavior as your column). Here’s a working pattern: 1) Create a row-level pass/fail measure (parameter-driven): Pass Threshold := VAR Threshold = SELECTEDVALUE('Parameter 2'[Parameter Value], 0) VAR PrevDate = CALCULATE( MIN('Work'[Date]), ALLEXCEPT('Work', 'Work'[ConsolidatedID]) ) VAR InitialMileage = CALCULATE( MIN('Work'[Mileage]), ALLEXCEPT('Work', 'Work'[ConsolidatedID]), 'Work'[Date] = PrevDate ) VAR CountRowsCID = CALCULATE( COUNTROWS('Work'), ALLEXCEPT('Work', 'Work'[ConsolidatedID]) ) VAR Dif = ABS( MAX('Work'[Mileage]) - InitialMileage ) RETURN IF( CountRowsCID > 1 && Dif <= Threshold, 1, 0 ) 2) Replace the calculated column with this measure: DaysInMarket := VAR CurrentDate = SELECTEDVALUE('Work'[Date]) VAR ValidRows = FILTER( ALLEXCEPT('Work', 'Work'[ConsolidatedID]), [Pass Threshold] = 1 ) VAR FirstDate = MINX(ValidRows, 'Work'[Date]) VAR LastDate = MAXX(ValidRows, 'Work'[Date]) RETURN IF( NOT ISBLANK(CurrentDate) && CurrentDate = LastDate, DATEDIFF(FirstDate, LastDate, DAY), 0 ) This will now recalculate dynamically whenever the DaysInMarket parameter/threshold changes. It works best in a table/matrix where Work[Date] is in the visual (so the measure can identify the “last date” row).395Views0likes0CommentsRe: Power BI REST API returns PowerBIEntityNotFound for dataset with upstream
Hi, What you’re hitting is not a permissions problem — it’s a limitation of the ExecuteQueries REST API with composite / upstream models. Your Dataset B is PbixInCompositeMode and has upstreamDatasets (i.e., it’s a composite model that depends on another semantic model). In these scenarios, the ExecuteQueries REST endpoint can fail with “PowerBIEntityNotFound” even when the dataset exists and the caller is a workspace admin. This aligns with other reported cases where ExecuteQueries works for import models, but fails once a model becomes composite / DirectQuery over another semantic model. A few important points: The ExecuteQueries API has several limitations (and service principal scenarios have additional limitations such as RLS/SSO restrictions). Composite models introduce extra security/lineage requirements (permissions across all participating models) and, in practice, REST ExecuteQueries is not reliable/unsupported for composite models even though XMLA works. Recommended workarounds: Query Dataset A instead (the upstream/import model) via ExecuteQueries, since that’s the part the REST API supports reliably. Continue using the XMLA endpoint for Dataset B (since you confirmed it works) — XMLA is generally the more robust option for programmatic querying at scale. If you must use REST ExecuteQueries, consider restructuring so Dataset B is not composite (i.e., avoid “dataset over dataset” / upstream dependency). So, bottom line: Dataset B being a composite model with upstream datasets is the reason you’re getting PowerBIEntityNotFound via REST, while XMLA still succeeds.942Views1like0CommentsRe: Key pair auth to Snowflake
Hi, Yes, Power BI Service does support Snowflake Key Pair authentication, but it must be configured correctly in the Service (under Data source credentials / Manage connections and gateways). If it works programmatically but not in Power BI, it’s usually due to one of the following: The private key format is not what Power BI expects (typically PKCS#8 PEM format). The private key is encrypted and the passphrase is not entered correctly. The RSA public key registered in Snowflake does not match the private key being used. The account URL / user / role / warehouse differs from what was tested programmatically. If a gateway is involved, the credentials must be configured on the gateway datasource in the Service (not just in Desktop). Regarding your second question: At this time, setting Snowflake Key Pair credentials via Power BI REST API is not fully supported for automation scenarios. While there are REST APIs for updating gateway datasource credentials, Key Pair authentication for Snowflake generally still requires manual configuration in the Power BI Service UI. If you can share the exact error message and whether you’re using a gateway or a cloud connection, it would help narrow down the issue further.2.5KViews1like0CommentsRe: Microsoft Text Slicer(preview) is not synchronizing the filter across the pages properly
Hi, This is a known limitation of the new Text Slicer (Preview). While it syncs correctly in Power BI Desktop, the sync behavior is not fully supported in Power BI Service yet. Even if Sync slicers is enabled, the value applied in the Text Slicer does not propagate across pages after publishing. Key points: The Text Slicer is still marked Preview Feature parity between Desktop and Service is incomplete Slicer synchronization across pages in Power BI Service is not guaranteed for preview visuals This is not a configuration issue on your side. Workarounds: Use the classic slicer if cross-page sync in Service is required Or duplicate the Text Slicer on each page (manual workaround) Track the issue and raise it via Power BI Ideas / Support, as this requires a Service-side update from Microsoft Bottom line: Until the Text Slicer exits preview and is fully supported in the Service, sync slicers across pages will be unreliable after publish.736Views1like0CommentsRe: Direct Query issue with Snowflake
Hi, You’re not doing anything wrong — this is a known issue/regression with Snowflake in DirectQuery in recent Power BI Desktop versions. Even if you only click Navigate, Power BI automatically adds a hidden metadata/type-detection step, and that step uses an operation not supported in DirectQuery, which immediately triggers the error. This happens with both Snowflake connector v1.0 and v2.0, and only in DirectQuery (Import works fine). Workarounds that usually help: Use the Snowflake connector Advanced options and provide an explicit SQL statement (for example, SELECT * FROM schema.table) instead of navigating tables. Disable Auto-detect column types (File → Options → Data Load), then reconnect. As a check, design in Import mode and then switch to DirectQuery. Bottom line: this is a Power BI Desktop behavior, not a Snowflake or model issue, and it needs a fix from Microsoft.1.7KViews2likes0CommentsRe: how to use redshift driver 2.x from powerbi saas
This is a known limitation and it’s not related to your gateway being outdated. When Power BI Service connects to Amazon Redshift through the on-premises data gateway, the ODBC driver version is controlled by the connector implementation, not by Power BI Service settings or the gateway version itself. Even with the latest Jan 2026 gateway, the native Amazon Redshift connector still uses the ODBC 1.x driver, which is why Redshift logs show: Amazon Redshift ODBC Driver 1.5.14.1017 At the moment: You cannot upgrade or force Power BI Service to use ODBC 2.x. Installing the Redshift ODBC 2.x driver on the gateway machine does not guarantee it will be used by the native Redshift connector. This requires a Microsoft update to the Redshift connector, not a gateway configuration change. Available options today: Use the generic ODBC connector and configure a DSN that explicitly uses Redshift ODBC 2.x (supported workaround, with some feature trade-offs). Use an alternative ingestion pattern (e.g. export from Redshift to S3 / lake and consume from there). Wait for Microsoft to update the native Redshift connector to support ODBC 2.x. In short, this is a platform limitation rather than a misconfiguration. Given AWS’s June 2026 timeline, using the generic ODBC connector with ODBC 2.x is currently the safest workaround.4.2KViews1like3CommentsRe: Azure Map Visual - No cluster bubble count number other than circle. Loss of relative size for squar
Hi, This is expected behavior and a current limitation of the Azure Maps visual in Power BI, not something you’re doing wrong. The cluster count label is only rendered for the Circle marker shape. When you switch the marker type to Square, Icon, or other shapes, Power BI does not render the cluster count text, and you also lose the visual size context that circles provide. Why this happens Cluster labels are part of the built-in circle cluster renderer Non-circle shapes are treated as symbol layers, which don’t support text overlays for cluster counts The visual doesn’t currently expose any option to: Enable labels for non-circle shapes Customize cluster label behavior per marker type So when you toggle from Circle → Square/Icon, the clustering still happens, but: The count label disappears The visual cue for relative cluster size is lost Is there a workaround? Unfortunately, no supported workaround inside the Azure Maps visual today. Your options are: Stick with Circle markers if cluster counts are required Or disable clustering and rely on individual markers Or build a custom visual (or use a different map visual) if labeled clusters with non-circle shapes are a hard requirement576Views1like0CommentsRe: Power BI Report Server with custom authentication error Power Bi Desktop
Hi, You didn’t miss a config setting — this is a product limitation. When Power BI Desktop saves/publishes to Power BI Report Server, it does a backend call to the Report Server REST API (for example GET /api/v2.0/ServiceState). That call only supports Integrated Windows authentication. With a Custom/Forms auth setup, the REST call returns 401, which is exactly what you’re seeing in the RSPortal logs. So: ✅ Portal login (Logon.aspx) works ✅ Report Builder works (because it can prompt / handle credentials differently) ❌ Power BI Desktop publishing fails with “Unexpected error occurred” because Desktop can’t complete the REST authentication flow when the server is using custom forms auth (cookie-based). What you can do Use Windows Integrated authentication for PBIRS (supported path). If you must keep custom auth, you’ll likely need to revert/enable Windows auth for the report server endpoint used by Desktop. Workaround: Save the PBIX locally, then upload it through the PBIRS web portal after logging in (if your portal allows uploading PBIX). This bypasses Desktop’s “Save to Report Server” authentication path. Ensure you’re using Power BI Desktop (optimized for Report Server) that matches your PBIRS version, but note this won’t solve the custom-auth limitation — it’s just a compatibility requirement. Bottom line Power BI Desktop cannot publish to PBIRS using Custom/Forms authentication. The 401 on /api/v2.0/ServiceState confirms that Desktop is blocked by the authentication mode.5.9KViews0likes0CommentsRe: SELECTEDVALUE on Field Parameter VALUE, not COLUMN
Hi — in Power BI field parameters don’t expose a “give me the current row value of the selected column” function. SELECTEDVALUE() on the parameter table can tell you which field (name) is selected, but DAX cannot dereference a column reference dynamically and return its value (there’s no “dynamic column pointer” you can evaluate). So if you want Val1/Val2/Val3 from whichever column is selected, you’re basically limited to one of these patterns: Option 1 (most common): SWITCH mapping Yes, it’s the standard answer: map the selected parameter item to the underlying column/measure using SWITCH(). Option 2 (cleaner at scale): use Measures in the field parameter + a Calculation Group Instead of putting columns in the field parameter, create measures (one per field) and build the parameter on those measures. Then use a calculation group with SELECTEDMEASURE() to apply common logic without repeating it 20 times. This reduces hard-coding and is much more maintainable. Bottom line: ➡️ No, you can’t directly retrieve the selected column’s value from a field parameter without mapping (because DAX doesn’t support dynamic column evaluation). ➡️ For 20+ fields, the best practice is field parameters over measures + calculation groups, or fall back to a SWITCH(). If you share whether those 20 fields are numeric measures or text columns, I can suggest the cleanest structure (and a template that avoids repeating logic).868Views1like0CommentsRe: AWS Costs via Azure Cost Management Connector into Power Bi
Hi, This is a known limitation of the Azure Cost Management Power BI connector. Even though AWS costs can be imported and viewed inside the Azure Cost Management portal, the Power BI Azure Cost Management connector only supports native Azure billing scopes (subscriptions, resource groups, billing accounts, management groups). It does not expose the AWS–Azure integrated cost data through the connector’s API endpoint. In other words: Azure Portal → Cost Management shows AWS costs Azure Cost Management API → Power BI connector returns Azure-only data This is not a configuration issue — it’s a product gap. Why this happens The AWS integration stores data in Azure Cost Management as a linked billing dataset, but it is not published through the Cost Management Query API that Power BI uses. The connector simply can’t see it. Microsoft documents the AWS integration mainly for: Portal reporting Exports Cost analysis UI Not for Power BI API consumption. What are your options? Option 1 — Use Cost Management Exports (recommended) In Azure Cost Management: Configure Exports to export the combined Azure + AWS cost data to: Azure Storage Azure Data Lake Then in Power BI: Use ADLS Gen2 / Blob Storage connector Read the exported CSV/Parquet files Build your AWS + Azure reporting from there This is Microsoft’s supported enterprise pattern. Option 2 — Pull AWS costs directly from AWS Use: AWS Cost and Usage Report (CUR) to S3 Or AWS Cost Explorer API Then load that into: Azure Data Lake / Fabric Or directly into Power BI This gives more control and better granularity than Azure’s AWS integration. Bottom line There is no way today to see AWS costs via the Azure Cost Management Power BI connector. If you need AWS + Azure cost reporting in Power BI, you must use Exports or AWS-native data sources. This is a platform limitation, not a misconfiguration.489Views0likes0Comments
Data Privacy
Microsoft Fabric Community and Privacy
To learn more about how we manage your data, please review the Microsoft Fabric Community Data Privacy guide.