Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Prepared a Direct Query version of a Power BI report using the Desktop app, and saved it as a new report name. Then published this report to the Power BI service. The publishing action correctly detected the database gateway. Unfortunately, the report as presented by the service does NOT agree 100% with the desktop version of the report. The majority of the data appears correct, but one data column (a color-coded status indicator) does not populate and present correctly. 😞 Is there some limitation with conditional formatting by rules in Direct Query mode, of which I'm not aware?
Solved! Go to Solution.
Answering my own issue. The data source is an Oracle 12c database. The issue arises because the query was comparing a TIMESTAMP value WITH TIME ZONE to a DATETIME value. In the desktop app, this comparison of differing field types did not cause any presentation issues. In the web/service version, it is critical. Comparing apples to apples resolved this issue. 🙂
Answering my own issue. The data source is an Oracle 12c database. The issue arises because the query was comparing a TIMESTAMP value WITH TIME ZONE to a DATETIME value. In the desktop app, this comparison of differing field types did not cause any presentation issues. In the web/service version, it is critical. Comparing apples to apples resolved this issue. 🙂
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.