Use of IN and && in a Conditional Caluclation
Hello, I have a calculation I've been using for a while with success. First we're checking if the sum of a column is greater than 9, based on the contents of another column. And if so, a division calculation is made to give a percent. Case SummaryCivil InitialFinal = IF(CALCULATE(SUM(CASELOAD_DATA_FILTERED[QUANTITY]), CASELOAD_DATA_FILTERED[CASE_AGE_ACTION] IN {"District Summary Civil Without Jury DemandDisposed within 126 days, no jury", "District Summary Civil Without Jury DemandDisposed after 126 days, no jury", "District Summary Civil Without Jury DemandPending over 126 days, no jury"} ) > 9, DIVIDE(CALCULATE(SUM(CASELOAD_DATA_FILTERED[QUANTITY]), CASELOAD_DATA_FILTERED[CASE_AGE_ACTION] IN {"District Summary Civil Without Jury DemandDisposed within 126 days, no jury"}), CALCULATE(SUM(CASELOAD_DATA_FILTERED[QUANTITY]), CASELOAD_DATA_FILTERED[CASE_AGE_ACTION] IN {"District Summary Civil Without Jury DemandDisposed within 126 days, no jury", "District Summary Civil Without Jury DemandDisposed after 126 days, no jury", "District Summary Civil Without Jury DemandPending over 126 days, no jury"})) ) However, stakeholders have asked that we add another condition to the calculation, so instead of doing this based on the contents of the CASE_AGE_ACTION column, we want to base it off of the contents of CASE_AGE_ACTION and another column CASE_TYPE_Code. So I've tried adding an && statement. Case SummaryCivilLLT InitialFinal = IF(CALCULATE(SUM(CASELOAD_DATA_FILTERED[QUANTITY]), CASELOAD_DATA_FILTERED[CASE_AGE_ACTION] IN {"District Summary Civil Without Jury DemandDisposed within 126 days, no jury", "District Summary Civil Without Jury DemandDisposed after 126 days, no jury", "District Summary Civil Without Jury DemandPending over 126 days, no jury"} && CASELOAD_DATA_FILTERED[CASE_TYPE_CODE] IN {"LT"} ) > 9, DIVIDE(CALCULATE(SUM(CASELOAD_DATA_FILTERED[QUANTITY]), CASELOAD_DATA_FILTERED[CASE_AGE_ACTION] IN {"District Summary Civil Without Jury DemandDisposed within 126 days, no jury"} && CASELOAD_DATA_FILTERED[CASE_TYPE_CODE] IN {"LT"}), CALCULATE(SUM(CASELOAD_DATA_FILTERED[QUANTITY]), CASELOAD_DATA_FILTERED[CASE_AGE_ACTION] IN {"District Summary Civil Without Jury DemandDisposed within 126 days, no jury", "District Summary Civil Without Jury DemandDisposed after 126 days, no jury", "District Summary Civil Without Jury DemandPending over 126 days, no jury"} && CASELOAD_DATA_FILTERED[CASE_TYPE_CODE] IN {"LT"}))) My problem is this isn't returning anything. Does anyone have any insight on to what I'm missing about how an && works (or doesn't work) with an IN statement? Or alternative suggestions? Thank you!
Incremental refresh - deletion
as per my understanding the "Detect data changes" option will only compare the last refreshed date with maximum of modifieddate in the incremental period selected which is 3 days as shown below higlighted and it does not check same for the historical partition which is 2 months window from 1st Aug 2026 to 24th Oct 2026 hence it can only refresh only records lies between 25th Oct 2026 and 27th Oct 2026 and can never refresh records between 1st Aug 2026 to 24th Oct 2026 even if there is a modification happen between 1st Aug 2026 to 24th Oct 2026, is this understanding correct?
Power BI Service Returning Different Results Than Desktop After Refresh
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } Hi all, I have a Power BI report where the calculations and visuals are fully validated in Power BI Desktop, but after publishing and refreshing the semantic model in Power BI Service, the results change despite the underlying source data appearing to be identical. What I've verified The report calculates correctly in Desktop. The semantic model is refreshed successfully in Power BI Service. Source totals match between Desktop and Service. Relationships are active and functioning. Diagnostic measures return the expected values in Desktop. The same diagnostic measures can also return the expected values in Service. The issue A measure that calculates a monthly ratio (Cost ÷ Volume) returns the expected values in Desktop, but after refresh in Power BI Service the same visual displays different monthly values. What's particularly confusing is: The overall totals reconcile correctly. The underlying source totals reconcile correctly. The discrepancy only appears in the monthly breakdown. Service returns the same incorrect monthly values consistently after refresh. Republishing a freshly refreshed PBIX restores the expected values. A subsequent semantic model refresh in Service causes the monthly values to change again. Additional observations We tested diagnostic measures separately and confirmed: Numerator values are correct. Denominator values are correct. Benchmark months reconcile correctly in Desktop. The semantic model contains the correct overall totals. The issue appears only after Service refresh and only affects the monthly allocation of values. Question Has anyone encountered a scenario where: Desktop calculations are correct, Service refresh succeeds, overall totals remain identical, but monthly allocations differ between Desktop and Service after refresh? Are there any known issues related to: Service refresh evaluation differing from Desktop, date grouping or hierarchy evaluation, semantic model refresh behaviour, stale visual metadata, report-to-semantic-model binding, or Excel/SharePoint sourced data being interpreted differently during Service refresh? Any troubleshooting suggestions would be greatly appreciated as we've verified the calculations extensively in Desktop and the issue appears isolated to how the refreshed model behaves in Power BI Service.
"We could not evaluate this query due to invalid or missing credentials" with Business Central
Hello everyone, I recently started receiving the following error when refreshing a Power BI Desktop report connected to Dynamics 365 Business Central Online: "We could not evaluate this query due to invalid or missing credentials." Environment: Power BI Desktop (latest version) Data source: Dynamics 365 Business Central Online Using the standard Dynamics 365 Business Central connector Authentication: Organizational Account No custom APIs or OData feeds Query contains only the Source step Has anyone recently experienced the same issue with the Dynamics 365 Business Central connector? I have also noticed reports from other users mentioning intermittent credential failures with the Business Central connector, and it appears Microsoft may already be investigating a broader issue. Any guidance or confirmation would be appreciated. Thanks!
How to Add a Fourth Filter Condition in Power BI?
Hi everyone, I have an existing visual-level filter, Addititves_Types, with three OR conditions: Flyash, GGBFS, and Microsilica. I need to add a fourth condition for P (LNP – Natural Pozzolan), but I can’t find the option to add another condition. Could someone please explain how to add a fourth OR condition? I’ve attached a screenshot of my current filter settings. Thanks!Power BI Desktop MySQL Connection Error: “The requested value 'None' was not found”
Hello everyone, I'm experiencing an issue when trying to connect Power BI Desktop to a MySQL database, and I'm looking for help identifying the cause and finding a solution. My environment: Power BI Desktop: 64-bit, version 2.157.1354.0 (August 2026) MySQL Connector/NET: 26.7.0 Issue: When I select the MySQL database connector, enter the server address and database name, and click OK, Power BI displays the following error: The requested value 'None' was not found. The connection works normally from another MySQL client, so the database server is accessible and I can connect to it outside Power BI. I have also checked Power BI's Data Source Settings. There is an existing entry for the MySQL server, and the authentication method is set to Database (MySQL username and password). Additionally, I checked the registered .NET data providers in Windows PowerShell, and MySql.Data.MySqlClient appears in the list. So far, I have not cleared the saved credentials, reinstalled the connector, or made any administrative changes to the computer. My questions: Could this error be caused by an incompatibility between Power BI Desktop and MySQL Connector/NET 26.7.0? Is there a recommended Connector/NET version for this version of Power BI Desktop? Could this be related to the MySQL connector's authentication settings, driver registration, or SSL configuration? Is there a way to obtain more detailed error logs to identify the root cause? I would appreciate any suggestions or troubleshooting steps that could help resolve this issue without requiring unnecessary changes to the computer's configuration. Thank you for your help!
Databricks Metric Views in Power BI: Validation of Measure Aggregation with Partial Queries
Hi everyone, I am testing the consumption of Databricks Metric Views in Power BI Desktop using the Databricks connector as part of a proof of concept. The objective is to validate measure calculations and understand how Metric Views behave when consumed through different Power BI connectivity approaches, particularly Import and DirectQuery. Test Scenario I am working with an existing Databricks Metric View that defines business measures related to work order management. As part of the testing, I am comparing the following approaches: Consuming the full Metric View in Power BI. Querying the same Metric View using a subset of dimensions and measures. Comparing the results returned by Databricks with the results displayed in Power BI. Validating measure aggregation, particularly the Work Order Release Percentage. When consuming the full Metric View, the results work as expected in my testing. However, when consuming a partial output of the same Metric View, I observe differences in the results displayed in Power BI. I would like to understand whether this behaviour is expected or whether there are any documented limitations associated with this approach. SQL Query Used for the Partial Metric View The following query selects the customer name and three measures from the existing Metric View. SELECT Customer Name AS customer_name, MEASURE(Released Work Orders) AS total_released_work_orders, MEASURE(Release Eligible Work Orders) AS total_release_eligible_work_orders, MEASURE(Work Order Release Pct) AS work_order_release_pct FROM <catalog>.<schema>.<metric_view_name> GROUP BY Customer Name ORDER BY Customer Name; The query returns the released work order count, eligible work order count, and Work Order Release Percentage for each customer. Results Validation I am comparing the output of this query in Databricks with the corresponding results displayed in Power BI. Expected behaviour: The business measures should produce consistent results when the same dimensions, filters, and aggregation context are applied in both Databricks and Power BI. Observed behaviour: The results displayed in Power BI differ from the corresponding Databricks results in this partial-query scenario. I have included screenshots of the Databricks output and the Power BI output for comparison. I would like to determine whether the difference is related to Metric View measure evaluation, aggregation semantics, the SQL query used, the Power BI connector, or the storage mode. Questions I would appreciate guidance on the following: Is there any documented limitation when consuming a subset of dimensions and measures from an existing Databricks Metric View in Power BI? Can selecting a subset of dimensions and measures affect how Databricks MEASURE() expressions are evaluated or aggregated? Are Metric View measures expected to preserve their defined calculation and aggregation logic when queried through a partial SQL query and consumed in Power BI? Can the behaviour differ between Import and DirectQuery modes when consuming Metric Views through the Databricks connector? Is there a recommended approach for exposing a subset of Metric View dimensions and measures to Power BI while preserving the intended business calculation logic? Would a wrapper view be appropriate in this scenario? Is this expected behaviour or a documented limitation, or could it indicate a potential issue with Metric View query execution or the Power BI connector? Additional Information I can provide the full and partial SQL queries, relevant Metric View measure definitions, Power BI storage modes, and sample Databricks and Power BI results to help reproduce the issue. Has anyone encountered similar behaviour when consuming Databricks Metric Views in Power BI? Any clarification on the expected behaviour, relevant documentation, or recommended troubleshooting steps would be appreciated. Thank you for your time and guidance. Regards, Bhuvana
Combining Two Power BI Dashboards into One Report
Hello, I currently have two separate Power BI dashboards/reports, each connected to its own data source. I don't need to merge or combine the underlying data sources. What I'm trying to achieve is having copy the pages with my visualizations so users can access everything in one place. Is there a way to bring the pages/visuals from one report into another without having to rebuild them manually or merge the datasets? Ideally, I'd like to keep the existing data connections and simply consolidate the reporting experience. Has anyone done this before, and what would be the recommended approach? Thanks!
