key didn't match any rows in the table

[ssnegi1971]

Hi All,

I have imported a dataflow in Report Builder. There is a parameter filter defined.

When I run the report it returns data a few times but most times it errors out with message "key didn't match any rows in the table" for the same parameter value.

Please advise how to make it consistently return data from the dataflow.

Thanks in advance.

[v-hashadapu]

Hi @ssnegi1971 , Hope you're doing okay! May we know if it worked for you, or are you still experiencing difficulties? Let us know — your feedback can really help others in the same situation.

[v-hashadapu]

Hi @ssnegi1971 , hope you are doing great. May we know if your issue is solved or if you are still experiencing difficulties. Please share the details as it will help the community, especially others with similar issues.

[ssnegi1971 · Accepted solution]

Hi, Instead of dataflow we are now doing direct query to the database view. This is not giving the issue.

[v-hashadapu]

Hi @ssnegi1971 , Thanks for the update and the details. If you face any other issues, please feel free to start new posts in the community. We are always happy to help. 

[v-hashadapu]

Hi @ssnegi1971 , Thank you for reaching out to the Microsoft Community Forum.

The issue is most likely a mismatch between the parameter value and the dataflow’s key column. Even if the values look identical, the key column may include extra spaces, inconsistent casing or hidden characters that prevent a match. This is especially common in dataflows that weren’t explicitly cleaned.

To fix it, go into your dataflow and make sure the key column is consistently formatted, remove extra spaces and standardize the text. Then, ensure your report parameter uses the same format.

Also, check the timing. If your report runs while the dataflow is still refreshing, some expected rows may not yet be available, which can cause temporary mismatches. Always run the report after a successful refresh.

Finally, confirm in Report Builder that the parameter is properly mapped in the dataset, not pointing to the wrong field or using stale metadata. Once the formatting, timing and mapping are aligned, the report should return results reliably.

[ssnegi1971]

But I am able to get return data a few times but most time is gives key not found error.

[v-hashadapu]

Hi @ssnegi1971 , Thank you for reaching out to the Microsoft Community Forum.

What you're seeing is likely a timing issue caused by querying the dataflow while it’s still refreshing or not yet fully available. In Microsoft Fabric, dataflows don't offer snapshot isolation during refresh. If your report runs at the wrong moment, the key you're filtering on might not be present in the dataset yet, even though it appears at other times.

Confirm the dataflow has fully refreshed before running the report. You can check this in the dataflow’s refresh history within your workspace. If you’re scheduling the report, adjust its timing so it runs well after the dataflow refresh completes. This should eliminate the intermittent failures.

If this still happens when no refresh is taking place, the issue may lie in how the parameter is passed to the dataset in Report Builder, it might not always be binding correctly. Recreating the dataset and parameter mapping from scratch can rule out any hidden configuration problems. But from what I understand, this is most likely a refresh-related timing issue.

[Idrissshatila]

Hello @ssnegi1971 ,

I know this error to be an access or credentials issue, just make sure that there's access to read the current table with the logned in credentials.

[ajaybabuinturi]

Hi @ssnegi1971,

Wanted to let you knwo that this happens even when using the same parameter value, it works sometimes but fails at other times.

Here are the possible fixes and suggestions.

1. Dataflow Key Column Might Have Formatting Issues

Even if the value looks right, it might not match due to:

• Leading/trailing spaces
• Case sensitivity
• Hidden characters

What you can try:

• In your dataflow (Power Query), use transformations like Text.Trim(), Text.Upper() to clean the key column.
• Make sure the parameter value is in the same format as your key column.

2. Dataflow Might Not Be Fully Refreshed

Sometimes, the dataflow might be in the middle of a refresh or returning stale data.

Action:

• Check the refresh history of the dataflow in the Power BI service.
• Try running the report shortly after a successful refresh.

3. Dataset Parameter Mapping Issue

There may be a problem with how your parameter is linked in the dataset query.

Steps:

• In Report Builder, go to Dataset Properties --> Parameters and make sure the parameter is correctly mapped to the intended field.
• Also, double-check if the dataset is using the correct parameter and filtering as expected.

4.Report Builder Cache or Metadata Issue

Report Builder can cache schema or parameter values, which might cause inconsistent results.

Fix:

• Close and reopen Report Builder.
• Try deleting and recreating the dataset and parameter to clear any old bindings.
• You can also test in a new .rdl file to rule out local corruption.

5. Schema or Structure Changes in Dataflow

If the dataflow schema changed recently (column renamed, key removed, etc.), it can cause this error.

Suggestion:

• Open the dataflow and verify the key column still exists and contains the expected values.
• Check if data types are consistent and unchanged.

Thanks,
If you found this solution helpful, please consider giving it a Like👍 and marking it as Accepted Solution✔. This helps improve visibility for others who may be encountering/facing same questions/issues.