Forum Discussion
AI - Text Analytics Not Showing when Published to Report
- 2 years ago
Hello. The issue has been resolved. For those wondering, it is currently tied to how the source data is loaded to PowerBI. For our particular case, our source data resided in an Excel file that is stored in a SharePoint document library. Based on guidance from PowerBI content creators (thank you folks for your work), the option used to connect to the Excel file (not my choice for a data source, but you work with what the company is comfortable with) is Web, and provide the URL to the Excel file.
In Power Query, under Advanced Editor, (File menu option) the first line appears as (site, directory, and file name changed to protect the innocent?):
Source = Excel.Workbook(Web.Contents("https://inoffice.sharepoint.com/sites/SharePointLibrary/DocumentLibrary/Directory/SubDirectory/SourceExcelFile.xlsx"), null, true),The fix is to change your data source from Web to SharePoint (see below what the update is to the Source line in Advanded Editor (Power Query).
Source = SharePoint.Files("https://inoffice.sharepoint.com/sites/SharePointSite", [ApiVersion = 15]),From there, you simply filter the relevant row in the loaded dataset to get your Source File Excel. In our case, as this is SharePoint, the column that was filtered was the native SharePoint library "Name" column. After that it's the usual steps in Power Query to obtain the content of your data and tehen call on the AI Text Analytics functions. You publish, and voila... all visuals in the published report can now show the results of the AI Text Analytics functions (we have sentiment!).
All this was identified with the awesome help of a Microsoft Support Engineer (who I would love to give a shout out to, but not sure what the rules are here). The next step is to explore why a simple Web connection to an Excel file prevents the AI features to display in published reports. The preliminary thought is that it has to do with privacy settings.
I hope this will be useful to someone also perplexed as to where all their sentiment has gone when using an Excel data source (before MS applies some sort of fix). Not sure if one marks your own response to your own question as the "Accepted Solution". Thanks all and happy BI'ing.
Hello future folks/peeps - if you are also inquiring as to why published reports in PowerBI are not showing the results of AI Text Analytics - this may be the thread for you. I did receive a response back from our PowerBI Service Admin, who indicated that all the "settings" to allow AI features were on. Next step is to set a call with Microsoft Support for them to evaluate. I have no clue how to do that, but apparently we have someone who has the 411 and correct connections/spellcasting magic to conjure MS support. Will reply to this thread with any updates.
These are the Capacity Settings shared by our PowerBI Service Admin, in case it helps.
Hello. The issue has been resolved. For those wondering, it is currently tied to how the source data is loaded to PowerBI. For our particular case, our source data resided in an Excel file that is stored in a SharePoint document library. Based on guidance from PowerBI content creators (thank you folks for your work), the option used to connect to the Excel file (not my choice for a data source, but you work with what the company is comfortable with) is Web, and provide the URL to the Excel file.
In Power Query, under Advanced Editor, (File menu option) the first line appears as (site, directory, and file name changed to protect the innocent?):
Source = Excel.Workbook(Web.Contents("https://inoffice.sharepoint.com/sites/SharePointLibrary/DocumentLibrary/Directory/SubDirectory/SourceExcelFile.xlsx"), null, true),
The fix is to change your data source from Web to SharePoint (see below what the update is to the Source line in Advanded Editor (Power Query).
Source = SharePoint.Files("https://inoffice.sharepoint.com/sites/SharePointSite", [ApiVersion = 15]),
From there, you simply filter the relevant row in the loaded dataset to get your Source File Excel. In our case, as this is SharePoint, the column that was filtered was the native SharePoint library "Name" column. After that it's the usual steps in Power Query to obtain the content of your data and tehen call on the AI Text Analytics functions. You publish, and voila... all visuals in the published report can now show the results of the AI Text Analytics functions (we have sentiment!).
All this was identified with the awesome help of a Microsoft Support Engineer (who I would love to give a shout out to, but not sure what the rules are here). The next step is to explore why a simple Web connection to an Excel file prevents the AI features to display in published reports. The preliminary thought is that it has to do with privacy settings.
I hope this will be useful to someone also perplexed as to where all their sentiment has gone when using an Excel data source (before MS applies some sort of fix). Not sure if one marks your own response to your own question as the "Accepted Solution". Thanks all and happy BI'ing.