Forum Discussion
Error message trying to retrieve Projects table (POL) using OData Flux in Excel / Power Query
- Oct 21, 2022
Hello Paul_Mather ,
After much googling I was finally able to resolve the issue.
At the beginning of this week my team and I did a clean up of the custom project fields that we use in Project Online. Turns out that there are certain specific words that can cause issues with the OData flux, such as "Project", "Category" etc...
Basically you have to be careful when naming the custom fields, as some words are reserved in some way:This was the post I found that was helpful: https://techcommunity.microsoft.com/t5/project-support-blog/project-online-using-reserved-custom-field-names-breaks-odata/ba-p/361488
I should have realised it was something to do with the fields as the issue appeared a day after we did that clean up in Project Online.
Really appreciate your help with this! Hopefully this can be useful for other people running into the same issue in the future.
Have a great day.
Best,
Camila
Hello Paul_Mather ,
Unfortunately it is not loading any data when entering that new URL. Here is what I get:
However, I can see my project list without any issues when accessing the following URL:
https://({tenantName}.sharepoint.com/sites/construction-pwa/Projects.aspx
Any ideas?
Appreciate the help!
Thank you!
Best,
Camila
Hi Camila_IB ,
I've just noticed the site in not in English, try this:
https://{tenantName}.sharepoint.com/sites/construction-pwa/_api/ProjectData/Projets
Paul
- Camila_IBOct 21, 2022Copper Contributor
Hi Paul_Mather ,
I actually tried that yesterday as well. I thought it could be that, but it gives me the same result:
Thanks,
Camila
- Paul_MatherOct 21, 2022MVP
Hello Camila_IB ,
This is what I was expecting to see, that endpoint (projets) is giving an error, that is why you are not getting the data in Excel. Going direct to the API in the browser ruled out Excel causing the issue. You will need to raise a support ticket to Microsoft via your Office 365 tenant asking them to resolve the data error that is causing the Projets endpoint to error.
Paul
- Camila_IBOct 21, 2022Copper Contributor
Hello Paul_Mather ,
After much googling I was finally able to resolve the issue.
At the beginning of this week my team and I did a clean up of the custom project fields that we use in Project Online. Turns out that there are certain specific words that can cause issues with the OData flux, such as "Project", "Category" etc...
Basically you have to be careful when naming the custom fields, as some words are reserved in some way:This was the post I found that was helpful: https://techcommunity.microsoft.com/t5/project-support-blog/project-online-using-reserved-custom-field-names-breaks-odata/ba-p/361488
I should have realised it was something to do with the fields as the issue appeared a day after we did that clean up in Project Online.
Really appreciate your help with this! Hopefully this can be useful for other people running into the same issue in the future.
Have a great day.
Best,
Camila