'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Retrieve Project Online Custom Field Values in Power Automate
Question details
The user needs to retrieve the actual values of Project Online custom fields and project dependencies using Microsoft Power Automate, rather than just the internal field names.
- Product
- Microsoft Power Automate
- Device & OS
- not provided
- Scenario
- Building an automated workflow to extract detailed project data, including custom fields and task dependencies, from Project Online.
- Observed behavior
- Power Automate successfully returns the Project Online custom field names but fails to return their corresponding data values.
Ensure you have the appropriate administrative permissions in Project Online and an active premium license for Power Automate if you plan to use custom HTTP connectors.
Consult the Microsoft Power Automate Community
Because Project Online custom field retrieval often requires complex OData queries or REST API calls, the official recommendation is to consult specialized community experts.
Advanced integrations between Project Online and Power Automate frequently fall outside the scope of standard connector capabilities. Engaging with specialists in the official community is the most effective way to resolve unique dependency and custom field issues.
Go to the official Microsoft Power Automate Community at powerusers.microsoft.com.
Use the search bar to look for 'Project Online Custom Fields' or 'Project Dependencies' to see if a similar workflow challenge has already been solved.
If you cannot find a solution, post a new question detailing your specific connector setup, OData query, and the exact custom fields you are trying to pull.
Use SharePoint HTTP Request for Custom Fields
Bypass standard connector limitations by directly querying the Project Server REST API.
Looking for a Lightweight Alternative to Microsoft Office?
While Power Automate and Project Online handle complex enterprise workflows, for your daily documentation, spreadsheets, and presentations, WPS Office offers a free, fast, and highly compatible alternative to Microsoft Office.
- 1. Download the Installer: Visit the official WPS Office website and click the free download button for your operating system.
- 2. Install WPS Office: Run the downloaded installer and follow the simple on-screen instructions to set up the suite.
- 3. Open Your Office Files: Launch WPS Office and immediately open your existing Microsoft Office files without worrying about formatting issues.
Frequently Asked Questions
Why are my Project Online custom fields showing up as GUIDs instead of values?
Custom fields in Project Online are often stored internally with unique identifiers (GUIDs). You may need to use an OData `$expand` or `$select` query in your API call to retrieve the human-readable text values associated with those GUIDs.
Can I get project dependencies using standard Power Automate connectors?
The standard Project Online connector in Power Automate has limited support for dependencies. You typically need to use SharePoint HTTP requests to query the Project Server REST API for complex task links and dependency tracking.
Where can I find the internal names for my Project Online custom fields?
You can find the internal names by navigating to PWA Settings > Enterprise Custom Fields and Lookup Tables in Project Online, or by querying the `/CustomFields` REST API endpoint directly.
