Forum Discussion
O365 Content OData errors
Hi Jakuza,
Current content pack only avaliable on power bi service.
>>A supported MIME type could not be found that matches the content type of the response. None of the supported type(s)
In addition, the error message also told that is a not supported type.
Regards,
Xiaoxin Sheng
This link says we can connect using ODATA Feed.
As mentioned in this link, We should be able to connect to O365 Adoption Content Pack through Power BI desktop using OData.
Or by using PBIT file. But I am getting the below error for both these approaches.
>>A supported MIME type could not be found that matches the content type of the response. None of the supported type(s)
In addition, the error message also told that is a not supported type.
What is the way to customize this report if we need to join this data with other data sources. Please suggest.
I'm getting exactly the same error and I need to do customizations as per the support article.
Is there someone who can start considering this an issue and provide us with the required support by investigating the error?
- A solution to this issue has NOT been provided. Please remove the SOLVED label from your reply and provide support for this issue.
Microsoft provides instructions on how to access data through PBI Desktop at https://support.office.com/en-us/article/Customize-the-Office-365-Adoption-content-pack-9b76065f-29b9-4b89-8059-c5f9db9ddbf6?ui=en-US&rs=en-US&ad=US .as well as at https://community.powerbi.com/t5/Integrations-with-Files-and/Access-O365-Adoption-Content-Pack-API-Programatically/m-p/409937#M16996
However, this solution does not work and results in the errors mentioned in the other messages in this discussion.
Thank you!Go to datasource and change the permission to "organizational account" that worked for me :)
make sure you log in with organizational account that is admin for some product e.g. exchange admin, skype for business admin, global admin etc.
Solved it for me as well with updating the data source connection, had used the pbit file earlier without issue and it worked, but suddenly got this error for a new tenant, didn't think to check the data source settings, but that was the issue :-)
