The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends September 15. Request your voucher.
I have created custom risk fields in PWA to accomodate our corporate risk register. I would like to bring these into Power BI for analysis. However, when running the OData query in Power BI, the custom fields are not visible in the risk table. The standard fields are, just not the custom. What am I missing here?
I have done as other posts suggest: re-published the project, etc.
Solved! Go to Solution.
Hi @jcrum_stewart,
I understand the concern regarding custom risk fields not appearing in Power BI through the standard OData connection from Project Web App (PWA). This behaviour is expected because the OData feed exposed by PWA does not include custom fields associated with the Risks list. These custom fields are actually stored in the SharePoint Risks list on each individual project site, not in the PWA reporting schema.
To resolve this issue, the recommended approach is to connect Power BI directly to the SharePoint Online site where the risks are maintained. You can do this by using the "SharePoint Online List" connector in Power BI. Simply navigate to one of your project sites via PWA, copy the site URL (not the list URL), and use that in Power BI to establish a connection. Once connected, select the "Risks" list from the navigator pane. This will allow you to retrieve all the standard and custom columns defined in that list, including your corporate risk register fields.
Glad I could assist! If this answer helped resolve your issue, please mark it as Accept as Solution and give us Kudos to guide others facing the same concern.
Thank you for using Microsoft Fabric Community Forum.
Hi @jcrum_stewart,
I understand the concern regarding custom risk fields not appearing in Power BI through the standard OData connection from Project Web App (PWA). This behaviour is expected because the OData feed exposed by PWA does not include custom fields associated with the Risks list. These custom fields are actually stored in the SharePoint Risks list on each individual project site, not in the PWA reporting schema.
To resolve this issue, the recommended approach is to connect Power BI directly to the SharePoint Online site where the risks are maintained. You can do this by using the "SharePoint Online List" connector in Power BI. Simply navigate to one of your project sites via PWA, copy the site URL (not the list URL), and use that in Power BI to establish a connection. Once connected, select the "Risks" list from the navigator pane. This will allow you to retrieve all the standard and custom columns defined in that list, including your corporate risk register fields.
Glad I could assist! If this answer helped resolve your issue, please mark it as Accept as Solution and give us Kudos to guide others facing the same concern.
Thank you for using Microsoft Fabric Community Forum.
Hi @jcrum_stewart,
Since we haven't heard back from you yet, I'd like to confirm if you've successfully resolved this issue or if you need further help?
If you've already resolved the issue, you can mark the helpful reply as a "solution" so others know that the question has been answered and help other people in the community. Thank you again for your cooperation!
If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you.
Hi @jcrum_stewart,
We haven’t heard from you on the last response and was just checking back to see if your query was answered.
Otherwise, will respond back with the more details and we will try to help .
If our response has addressed your query, please accept it as a solution and give a ‘Kudos’ so other members can easily find it. Please let us know if there’s anything else we can do to help.
Thank you.
Hi @jcrum_stewart,
I wanted to follow up on our previous suggestions regarding the issue. We would love to hear back from you to ensure we can assist you further.
If our response has addressed your query, please accept it as a solution and give a ‘Kudos’ so other members can easily find it. Please let us know if there’s anything else we can do to help.
Thank you.