Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreJoin the FabCon + SQLCon recap series. Up next: Power BI, Real-Time Intelligence, IQ and AI, and Data Factory take center stage. All sessions are available on-demand after the live show. Register now
Hi,
with api 14 with code below, it is missing LGU+ contents in the folder.
let
Source = SharePoint.Contents("https://nokia.sharepoint.com/sites/korea-pmo-pbi-data-repository", [ApiVersion = 14]),
#"Documents" = Source{[Name="Documents"]}[Content],
#"KR Cell Status" = #"Documents"{[Name="KR Cell Status"]}[Content],
wherease, api 15, it is not missing any.
The reason I tried it with 14 was I heard 14 might not missing all the contents and better, but not sure.
My SP site was created in 2023. Should I keep using api version 15?
let
Source = SharePoint.Contents("https://nokia.sharepoint.com/sites/korea-pmo-pbi-data-repository", [ApiVersion = 15]),
#"Shared Documents" = Source{[Name="Shared Documents"]}[Content],
#"KR Cell Status" = #"Shared Documents"{[Name="KR Cell Status"]}[Content],
Solved! Go to Solution.
Hi @Anonymous ,
Thanks for the detailed explanation and screenshots — they really help clarify the issue.
What you're seeing is actually a known behavior difference between API version 14 and 15 in the SharePoint.Contents function.
Even though some sources suggest API 14 might be more stable, in practice:
Stick with API version 15 — especially since your site is relatively new and you're seeing complete results with it. Unless you have a specific legacy compatibility requirement, API 15 is the safer and more future-proof choice.
Let me know if you want help optimizing your query structure or filtering specific folders dynamically.
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
This response was supported by AI for translation and text editing.
Hi @Anonymous ,
Thanks for the detailed explanation and screenshots — they really help clarify the issue.
What you're seeing is actually a known behavior difference between API version 14 and 15 in the SharePoint.Contents function.
Even though some sources suggest API 14 might be more stable, in practice:
Stick with API version 15 — especially since your site is relatively new and you're seeing complete results with it. Unless you have a specific legacy compatibility requirement, API 15 is the safer and more future-proof choice.
Let me know if you want help optimizing your query structure or filtering specific folders dynamically.
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
This response was supported by AI for translation and text editing.
Check out the April 2026 Power BI update to learn about new features.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
| User | Count |
|---|---|
| 48 | |
| 40 | |
| 38 | |
| 20 | |
| 16 |
| User | Count |
|---|---|
| 68 | |
| 67 | |
| 30 | |
| 26 | |
| 26 |