Forum Discussion
SharePoint Source Evaluating won't load
- 1 year ago
This is a fairly common issue and typically isn't directly related to the SharePoint source itself, but rather to mismatches between the data types in your source files and Power BI's automatically inferred data types.
To resolve this issue, try the following steps:
-
Disable Power BI's automatic data type detection:
In Power Query, disable automatic detection and manually assign the appropriate data types, especially numeric and date columns. -
Inspect date fields carefully:
Verify that all date fields have consistent and correct formatting. If irregularities exist, correct them directly in the source data. -
Check for whitespace or special characters:
Look closely for hidden whitespace or special characters within numeric or date fields, as these can prevent proper type conversions. -
Use 'Keep Errors' to diagnose problematic rows:
In Power Query, right-click the problematic column and select "Keep Errors". This will isolate rows causing the conversion errors. You can then either fix these rows directly in your source or remove them if they’re not necessary. -
Review transformation steps in Power Query:
Sometimes, an earlier transformation step (such as merges, expands, or value replacements) can cause errors that manifest in later steps. Check each step individually to pinpoint the exact cause.
Important: After applying these steps, ensure you validate the fixes on the entire dataset—not just the preview of the first 1000 rows—since issues may occur only deeper in the data.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
-
This is a fairly common issue and typically isn't directly related to the SharePoint source itself, but rather to mismatches between the data types in your source files and Power BI's automatically inferred data types.
To resolve this issue, try the following steps:
-
Disable Power BI's automatic data type detection:
In Power Query, disable automatic detection and manually assign the appropriate data types, especially numeric and date columns. -
Inspect date fields carefully:
Verify that all date fields have consistent and correct formatting. If irregularities exist, correct them directly in the source data. -
Check for whitespace or special characters:
Look closely for hidden whitespace or special characters within numeric or date fields, as these can prevent proper type conversions. -
Use 'Keep Errors' to diagnose problematic rows:
In Power Query, right-click the problematic column and select "Keep Errors". This will isolate rows causing the conversion errors. You can then either fix these rows directly in your source or remove them if they’re not necessary. -
Review transformation steps in Power Query:
Sometimes, an earlier transformation step (such as merges, expands, or value replacements) can cause errors that manifest in later steps. Check each step individually to pinpoint the exact cause.
Important: After applying these steps, ensure you validate the fixes on the entire dataset—not just the preview of the first 1000 rows—since issues may occur only deeper in the data.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
I have a data set wich consists of a text file which is download from the mainframe.
A fiscal year has about 1.5 million records. The main query gets to about 955 MB and just hangs. The main query has between 7.5 and 8 million records. I have tried filtering out a fiscal year's worth of data but it still fails. I dont undertand why the source source (reference) just hangs.