Incomplete loarding data after importing dataset

dofrancis3​ ,

The "List may be incomplete" warning doesn't mean your data failed to load. Power Query builds that filter list from a preview of the first 1,000 rows only. When you click Close & Apply, all rows are loaded.

If you need the full list in the filter box: click Load more in the dropdown, which appears next to the warning. You can also set the status bar at the bottom to "Column profiling based on entire data set".

If data is really missing in the report, check these:

1. Filters you applied by accident. In your first screenshot, Indicator Logframe Entity has unchecked items, so a filter step is removing those rows. Look in Applied Steps for a "Filtered Rows" step and delete it or correct it.
2. Rows with errors. A data type change, such as text converted to a number or date, can create errors. Check for a "Removed Errors" step, and look for red bars in View → Column quality.
3. Relationships. If key values don't match between tables, for example because of extra spaces or different text case, visuals show blanks or drop rows. Use Trim and Clean on key columns and check the relationship.
4. Visual or page filters. Check the Filters pane in the report.
5. Check the counts. In Table view, compare the row count shown at the bottom with the row count in the source file. If they match, all data was loaded, and the problem is filters or relationships.

Hi dofrancis3​,

The message in your screenshot does not necessarily mean that the imported dataset is missing rows.

What Power Query is telling you is that the filter dropdown has reached its preview limit for distinct values. Your second screenshot confirms this with the message:

Limit of 1000 values reached.

So the dropdown is only showing part of the distinct values available in that column. The remaining values can still exist in the underlying table even though they are not listed in the filter menu.

I would verify this by checking the actual row count and distinct count rather than relying on the dropdown list.

For example, in Power Query you can temporarily create a reference query and use:

Table.RowCount(Source)

or for a specific column:

List.Count(List.Distinct(Source[Record ID]))

If those counts match what you expect from the source, then the data has loaded correctly and the warning only relates to the filter-value preview.

You can also use Text Filters, Number Filters, or the search box to filter for a value that is not currently visible in the dropdown instead of scrolling through the list.

So I would first confirm the row count before changing the import logic. Based on the screenshots, this looks much more like a filter-list display limit than incomplete dataset loading.

AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.

“List may be incomplete” refers to the filter dropdown. Power Query initially lists up to 1,000 distinct values there. That warning alone doesn’t indicate that rows were skipped during import.

Pick one project that’s missing from the report. In Power Query, use Text Filters > Equals and type its exact name. This lets you check for it even if it isn’t listed in the dropdown. Remove that temporary filter after testing.

If the project is missing from the final Power Query step, check whether it exists at the first step that shows your data, then look for the step where it disappears. If it’s present in Power Query and in Table View after Close & Apply, check the report filters and the relationship used by the visual.