Forum Discussion
Cannot find the resource for the request $metadata
Good Evening All
First post so I am hoping you will all help me where you can!
I have inherited a lovely Power BI dashboard which has been working successfully pointing to our pre-production SharePoint 2013 on-prem site. The developer was a contractor who has since left. After leaving, the customer signed off on the dashboard and the underlying application on SharePoint.
The application was then copied across to our production SharePoint 2013 on-prem environment using Sharegate. I now need to change the Power BI report to point to the new site. This seems super straight forward, so i did the following:
- Edit Queries > Data Source Settings
- Chose the SharePoint datasource and Change Source
- I changed the url from our pre-prod site to the prod site
- Close and Apply
Whilst applying the query changes I get the above error.
"SharePoint: Request failed (404): The remote server returned an error: (404) Not Found. (Cannot find the resource for the request $metadata.)
When i go back and change the datasource to the pre-prod url it is absolutely fine.
Has anyone ever seen this. It is really delaying to roll out of the application solution to production for the customer.
Thanks in advance - all help is majorly appreciated.
Cassy
- Anonymous7 years ago
Symptom: You got an error when you are trying to change the SharePoint site from UAT to production
Cause: The API version mismatch
Resolution: Change the API version in each table from 15 to 14
6 Replies
- parry2k
Super User
Anonymous can you try to create a sample report and connect to new production share point environment and see if that works, if yes use that connection string (url) and use it for in the old report. Just a suggestion. It will also help to debug further.
- AnonymousNot applicable
Hi
Thanks for the suggestion. When i create a new project and use the same url it connects and loads no problem whatsoever.
Thanks
Cassy
- v-yuta-msft
Community Support
Hi cassy_freeman,
Please check if the sharepoint site url is valid when connecting to your resource.
Regards,
Jimmy Tao
- AnonymousNot applicable
Hi
Thank you - it is correct.
Thanks
Cassy
- AnonymousNot applicable
Does anyone have any other ideas?
- AnonymousNot applicable
Symptom: You got an error when you are trying to change the SharePoint site from UAT to production
Cause: The API version mismatch
Resolution: Change the API version in each table from 15 to 14