Error: The property 'DefaultSensitivityLabelForLibrary' does not exist on type 'SP.List'

[JorisVoorn]

Since today I am facing error on Dataflow which was previously working without any issues. IT is dataflow which is consolidating multiple excel files stored st sharepoint and which currently returns below statement.

Error: Data Source Error : DataSource.Error: We couldn't parse OData response result. Error: The property 'DefaultSensitivityLabelForLibrary' does not exist on type 'SP.List'. Make sure to only use property names that are defined by the type. DataSourceKind = SharePoint DataSourcePath = """. RootActivityId = 82fcbe72-7a90-44d4-afa7-6afc9dac2f40.Param1 = DataSource.Error: We couldn't parse OData response result. Error: The property 'DefaultSensitivityLabelForLibrary' does not exist on type 'SP.List'. Make sure to only use property names that are defined by the type. DataSourceKind = SharePoint DataSourcePath = """ Request ID: d485d693-916f-a993-5171-f1d861011038.

Any idea what might be problem?

Thank you in advance

BR

Pavel

[Anonymous]

I am running into this issue with a couple reports. Our company just enabled Sensitivity Labels for everyone, I had been piloting these, so strange that am running into this issue. I have several other reports pulling from SharePoint lists, and/or .csv files stored in SharePoint Online sites.

On two reports, am getting the same error:

We couldn't parse OData response result. Error: The property 'DefaultSensitivityLabelForLibrary' does not exist on type 'SP.List'. Make sure to only use property names that are defined by the type.

I have set a sensitivity label on the Team site, SPO site behind it and Power Bi report (and downstream). Same label accross the board, but my data fails to refresh on the published report and in Power Bi desktop. Maybe I need to wait a little longer since the labe was applied to the whole SPO site? 

[Anonymous]

Try Re-indexing the SharePoint list that stores the files you are pushing. That should resolve the problem for those 2 files. After re-indexing wait for 15 -30 mins.

[Anonymous]

Re-indexing the list and doc library where the csv files are in. Will update with results, later this morning.

Thanks!

[Anonymous]

Re-indexing the list and doc library seems to have done the trick. Thanks!

[jnickell]

@Anonymous How did you  monitor the progress of your re-index. I tried re-indexing the doc library and haven't been able to get the PS module to work so I can monitor a reindex that way.  

I waited about an hour and a half I think tried to refresh the dataflow and it failed with the Defaultsensitivitylabel error again.

[Anonymous]

I did not monitor it, honestly (also a SharePoint admin at my Company), don't know top of my head a way to monitor a site re-index/crawl. I have had our Microsoft Mission Critical support engineer do that for me before while on some other troubleshooting calls. 

All three report refreshes that were failing with that error eventually refreshed correctly...but one of those reports that was set to refresh around noon today per the schedule...failed again with the same error. I just manually refreshed it and it worked....

I think there has to be some bug going on...everything looks correct, same "General" label applied to the Team, SPO site behind the Team, Power Bi dataset, and downstream. Only thing that does not have a label are the .csv files, which we know you can't label.

I have a few other people in my org running into the same issue. If it continues, am going to open a cas with Microsoft to investigate further.

[jnickell]

I opened a ticket with PowerBI earlier. Couldn't take the call when the tech called and haven't heard back yet.  He pointed me to this thread 🙂 to try and address it. 

We haven't yet deployed sensitivity labels, and all but maybe one or two files in this document library are CSVs.  On top of that it did refresh fully without issue when I switched the API version to 14, then failed when I switched it back to 15.  I haven't re-tried the 14 version yet.  

[Anonymous]

Yeah, you might be onto something in regards to the API version...weird thing is that I have been under the Sensitivity Labels test policy for a while. We did enable it for all of our org ealier this week, but labels/policy settings pretty much the same as our test policy. 

I think re-indexing helped, the more docs you have on the library/list you re-index, the longer it will take. 

The moment I start get more complaints I'll open a case, but will keep checking this thread to see what MS tells you on your case.

[jnickell]

MS didn't give me any direction during our troubleshooting session, but I left everything "in place" over the weekend with no net changes and while I had a hiccup on a different Sharepoint list (not document library) based dataflow, the document based dataflow that got me here on Friday had no issues over the weekend.  

The list based dataflow only errored on Saturday morning and was fine Sunday and Monday morning.

[jnickell]

I started running into this issue this morning. All the files are CSV files and to my knowledge no "sensitivity labels" have been applied in our environment.

At first (today) it looked like it was API limiting based on the error messages I was getting were about not being able to get contextinfo about files (didn't notice if it was same file every time or different).

Same dataflow had been working fine for months, Yesterday I removed one of the tables in the dataflow, but I am not remembering any other changes I made to the dataflow.  

[jnickell]

I switched my source query from API version 15 to API version 14 and was able to complete a dataflow refresh.  

Switching it back to API version 15 failed, but with a different error message. 

Error: DataSource.Error: Web.Contents failed to get contents from 'https://xxxxxx.sharepoint.com/sites/yyyy/_api/web/getfilebyserverrelativeurl('/sites/analytics/Share...' (429): Request ID: c7aaf62d-981f-6d14-dded-a1492c355650 Activity ID: 6467f206-44db-4ef3-85e5-0c7aa1e06303

[Anonymous · Accepted solution]

I ran into the same problem. I was pulling Excel files from SharePoint in a dataset and publishing it on Power Bi Service. I changed the Sensitivity label on excel files and it worked.

thanks.

Yogesh