Forum Discussion

JorisVoorn's avatar
JorisVoorn
Microsoft Employee
5 years ago
Solved

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

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 ...
Need Help
  • Anonymous's avatar
    Anonymous
    5 years ago

    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

     

Anonymous's avatar
Anonymous
Not applicable
5 years ago

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's avatar
Anonymous
Not applicable
5 years ago

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

 

Thanks!

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

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

    • jnickell's avatar
      jnickell
      Helper V
      5 years ago

      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's avatar
        Anonymous
        Not applicable
        5 years ago

        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.