locked
SharePoint queries do not load due to empty person fields RRS feed

  • Question

  • Hi
    I am trying out the Power Query tool and I have also tried out Power BI for the same purpose.

    My problem exist with person/group columns in SharePoint. When trying to load data from SharePoint lists with person/group columns and the lists has at least one item with an empty person field, I get an error. Always on this type of column which is almost never mandatory. It seems the query tool wants to have data but these columns are optional in SharePoint.

    Here´s an example of the error I get. Any ideas on what to do?

    DataSource.Error: We couldn't parse OData response result.  Error: A null value was found for the property named 'readaccess_othersId', which has the expected type 'Collection(Edm.Int32)[Nullable=False]'. The expected type 'Collection(Edm.Int32)[Nullable=False]' does not allow null values.
    Details:
        DataSourceKind=SharePoint
        DataSourcePath=http://teams.domain.com/team/myteam/mysubsite/_api/Web/Lists(guid'6a8ba542-0f12-4873-b5af-37c989b9f15a')/Items


    Thanks Gunnar


    Gunnar Reyr Sigurðsson SharePoint Consultant Computer Science B.Sc.

    Wednesday, December 9, 2015 11:13 AM

Answers

  • Hi Gunnar,

    This is a known bug with SharePoint that may be fixed in the future. One way to work around the issue is to change make the connector use older SharePoint APIs, which don't have this bug. The older APIs, unfortunately, have other known bugs and will present data slightly differently. You'll have to check to make sure that this is a good work around for you.

    = SharePoint.Tables("http://teams.domain.com/team/myteam/", [ApiVersion = 14])

    Tristan

    • Proposed as answer by Tristan St-Cyr Wednesday, December 9, 2015 10:16 PM
    • Marked as answer by gunnarreyr Friday, December 11, 2015 2:34 PM
    Wednesday, December 9, 2015 10:16 PM

All replies

  • Hi Gunnar,

    This is a known bug with SharePoint that may be fixed in the future. One way to work around the issue is to change make the connector use older SharePoint APIs, which don't have this bug. The older APIs, unfortunately, have other known bugs and will present data slightly differently. You'll have to check to make sure that this is a good work around for you.

    = SharePoint.Tables("http://teams.domain.com/team/myteam/", [ApiVersion = 14])

    Tristan

    • Proposed as answer by Tristan St-Cyr Wednesday, December 9, 2015 10:16 PM
    • Marked as answer by gunnarreyr Friday, December 11, 2015 2:34 PM
    Wednesday, December 9, 2015 10:16 PM
  • Thank you.

    Gunnar Reyr Sigurðsson SharePoint Consultant Computer Science B.Sc.

    Friday, December 11, 2015 2:34 PM