Power BI Report Builder not showing the same result as in semantic

[rinoyaohari]

Hi,

I need help in Power BI Report Builder, I have create a report, and also setup the parameters inside, when i tried to show the data, it didnt show the expected result. Somehow some of the row are missing even though they fulfilled the report parameters.

for the dataset, I took the data from Google BigQuery and put them into semantic.

Below I put the screenshot of the expected result and the result I got from the report builder. If anyone knows what is wrong with my query or parameters, please help me, thanks !

[v-sgandrathi]

Hi @rinoyaohari,

we haven't heard back from you regarding our last response and wanted to check if your issue has been resolved.

Should you have any further questions, feel free to reach out.
Thank you for being a part of the Microsoft Fabric Community Forum!

[v-sgandrathi]

Hi @rinoyaohari,

As we have not received a response from you yet, I would like to confirm whether you have successfully resolved the issue or if you require further assistance.

Thank you for your cooperation. Have a great day.

[v-sgandrathi · Accepted solution]

Hi @rinoyaohari,

Thank you for the detailed update. Since the missing rows are only an issue in Report Builder and not when using the same filters in the semantic model, the problem is likely with how the dataset query is executed in Report Builder, not in BigQuery or the semantic model itself. This is often due to parameter mapping, strict DAX filtering, or hidden dataset-level filters.

First, check the parameter mapping in Dataset Properties -- Parameters. Even if your dates in BigQuery and the semantic model are date-only (00:00:00), Report Builder treats DateTime parameters strictly. For example, if you pass an end date like 30/06/2021, it interprets it as 2021-06-30 00:00:00, which can exclude records from that day. To fix this, update the parameter expression to:
=DateAdd("d", 1, Parameters!ToSystemDate.Value)
This adjustment makes sure the final day is included and often resolves discrepancies between Power BI and Report Builder.

Next, preview your dataset without any filters. Remove or widen parameter filters to see if the SKL-01 rows appear. If they do, the issue is with parameter mapping. If not, review the generated DAX in the Query pane. Report Builder may apply strict equality filters, especially on text fields, so small differences like extra spaces or case inconsistencies can cause rows to be excluded. Power BI Desktop handles these differences automatically, but Report Builder does not.

Lastly, confirm that there are no hidden dataset-level or tablix-level filters. Sometimes, imported datasets bring filters that aren’t visible in the visual layer. Check Dataset Properties -- Filters and make sure there are no extra filters applied. Also, verify that RLS or workspace permissions are not limiting rows for the credentials used in Report Builder. 

Thank you.

[rinoyaohari]

Hi, thank you for replying, i was looking at your suggestion and i have come to this.

1. The date thrown from Big Query into semantics and into my report dataset is formatted only to date, and when i check on the time , it is already set to 00:00 for all data.

2. the SUPPLIES was not shown in the report but on the dataset all the items should've the SUPPLIES value, both in SKL-01 and SKL-02, and Yes i have tried Select All, but still the SKL-01 is missing from my report.

3. I tried looking to my Tablix and there is not filters on it too.

FYI, I have tried opening my semantic, and then goes to Transform data, tried the same filter on the columns and the data showing up fine, maybe you have any more ideas on why the data is not shown on my report?

Thanks Again.

[Sandip_Palit]

The issue is almost certainly caused by how the DAX query in Report Builder handles Date/Time parameters or Strict Filtering on Null values.

Here is the step-by-step solution to fix it.

1. The "End of Day" Time Issue
In your parameter screenshot, the To System_Date is set to 6/30/2021.

The Problem: When you pass a date like 6/30/2021 to the query, the semantic model treats it as 2021-06-30 00:00:00 (midnight).

The Consequence: Any transaction that happened on June 30th after midnight (e.g., at 10:30 AM) is technically greater than the parameter value, so it gets filtered out.

The Solution: You need to adjust the dataset query or the parameter to include the full day.

How to fix it in Report Builder:

Go to your Dataset Properties in Report Builder.

Go to the Parameters tab.

Find the parameter for ToSystemDate.

Instead of mapping it directly to the report parameter [@ToSystemDate], change the expression to add one day: =DateAdd("d", 1, Parameters!ToSystemDate.Value)

Alternatively, inside your query logic, change the operator from <= (Less than or Equal) to < (Strictly Less Than) the next day.

2. Strict Filtering on "Blank" Values
Looking at your screenshots, the "Expected" image shows Inventory Transfers at the bottom. The "Actual" result seems to be missing these specific rows.

The Problem: The query designer in Report Builder generates DAX that is very strict. You are filtering by Item_Group = "SUPPLIES".

The Trap: In many ERP systems, transaction types like "Inventory Transfers" or "Adjustments" might not have the Item_Group column populated (it might be Null or Blank). Power BI Desktop visuals often show these as "(Blank)", but the strict DAX query generated by Report Builder will simply exclude any row where Item_Group is blank because it doesn't match "SUPPLIES".

How to fix it: Check your data source. Do the missing rows (Inventory Transfers) actually have "SUPPLIES" in the Item_Group column? If they are blank, you must either:

Fix the data in BigQuery to ensure those rows have the correct Group.

Or, update the parameter in Report Builder to "Select All" (including Blanks) and filter visually in the table instead.

3. Check for Hidden "Tablix" Filters
Sometimes the data is actually being retrieved by the query, but the table (Tablix) in Report Builder is hiding it.

Click on the gray handle of your Table (Tablix) in the design view.

In the Properties pane (or right-click -> Tablix Properties), look at the Filters tab.

Ensure there are no extra filters applied there that might be accidentally hiding specific rows.

If this explanation and solution resolve your issue, please like and accept the solution.