sharepointpowerbipowerquery

Importing SharePoint Data into PowerBI

I am linking PowerBI to our SharePoint based case management system. If I use [ApiVersion = 15], I can see the subsite I need, but when I import it into PowerQuery it will not have all the columns.

Using ApiVersion = 15

On the other hand, if I use [ApiVersion = 14], I can see the subsite twice, the second time with a 0 added at the end of the name (CaseLog and CaseLog0). The missing columns are now available in the subsite with the 0 at the end of the name.

Using ApiVersion = 14

Though the ApiVersion 14 solution seems to work, and I am able to import all the data needed and design my report in PowerBI, I am curious to understand what's going on.

Thanks to anybody who can explain me what's going on.

Solution
    1. API Version 15

    This version is used in newer SharePoint environments (SharePoint Online, and later).

    When you query your SharePoint site with ApiVersion = 15, you see the correct subsite (CaseLog), but not all columns are available. This is likely due to how SharePoint structures and optimizes data retrieval in the modern API, possibly hiding certain metadata or complex field types.

    1. API Version 14 (SharePoint 2010 Compatibility Mode)

    This version is based on an older SharePoint API (SharePoint 2010). When you use ApiVersion = 14, two versions of the subsite appear:

    CaseLog: This is the same as in API v15, but it still may not expose all columns.

    CaseLog0: This seems to be an alternative reference to the same data but exposes additional columns.

    The presence of CaseLog0 suggests that the older API version is surfacing a different internal representation of the list, possibly related to how SharePoint handled list views or indexed lists in older versions.

    Possible Reasons for CaseLog0 Appearing:

    SharePoint may be storing different views or indexed versions of the same list and exposing them differently depending on the API version.

    The 0 suffix is sometimes used when there are duplicate references to the same resource, possibly due to legacy compatibility.

    Older APIs may interact differently with complex SharePoint lists, especially those with hidden/system columns.

    As long as the data is correct in CaseLog0, using API v14 is a valid workaround. However, keep in mind that Microsoft may deprecate API v14 in the future.