Unanswered

Read Project Online enterprise custom fields (ECF) with Flow

(0) Share

Report

Posted on by FastTrack

Hello,

I am able to update a Project Online enterprise custom fields (ECF) with Flow using "Send HTTP to SharePoint", but I am not able to read them and use them for further actions in Flow...

Here is how I am updating:

Update Custom Field (thanks to @Anonymous)

Categories:

Building flows

I have the same question (0)

All responses (8)

Answers (0)

v-bacao-msft on at

Like (0)

Report

Hi @FastTrack ,

What is the data format of the response of this action, JSON or XML?

If it's JSON, you could use Parse JSON action to parse the properties contained in the response and reference these property values.

Please check this blog and for more details on the use of the Parse JSON action:

http://johnliu.net/blog/2018/6/a-thesis-on-the-parse-json-action-in-microsoft-flow

If the format of the returned data is XML, please provide sample data so that we could provide the appropriate expression according to the specific format.

In addition, you could also refer to this similar thread to get the corresponding data:

https://powerusers.microsoft.com/t5/General-Flow-Discussion/Parse-XML-using-Microsoft-Flow/td-p/114920

Best Regards,

Was this reply helpful? Yes No
FastTrack 96 on at

Like (0)

Report

@v-bacao-msft
I am a Project Manager and not a Programmer so I have no clue what you are talking about...
The Flow I got from another user lets me update an Enterprise Custom Field viea SharePoint Http request, and now I want another flow to read an ECF and fields like "Resource Name", which are not yet implemented for Flow yet...

Was this reply helpful? Yes No
POLFlowGuy 4 on at

Like (0)

Report

You would use the action "Send an HTTP request to SharePoint". Enter in your base PWA site URL in the Site Address. The method would be GET. The URL would be: _api/ProjectData/Projects(guid'<ProjectId>') *Note, sub the <ProjectId> with the GUID of the ProjectId you want or get it dynamically using List Projects and then use the output. Add headers of Accept to be application/json;odata=nometadata and Content-Type of application/json;odata=nometadata.
Resources would use: _api/ProjectData/Resources(guid'<ResourceId>')
Tasks would use: _api/ProjectData/Tasks(guid'<TaskId>')

Run the flow initially to test it and view the results. Then you'd probably want to get the results in the body of the output and then copy to your clipboard. Then use a 'Parse JSON' action and use the 'Generate from Sample' button and paste in the schema. You'll then have access to all the fields in the dynamic content for other operations.

Was this reply helpful? Yes No
POLFlowGuy 4 on at

Like (0)

Report

Resources would be the same thing using _api/ProjectData/Resources(guid'<ResourceId>')

Was this reply helpful? Yes No
TomasSys 6 on at

Like (0)

Report

Hi, I am already using this for some time for Projects, but now I would like to do so for Tasks. I tried your recipe, but always get this error:

{
"odata.error": {
"code": "",
"message": {
"lang": "en-GB",
"value": "The number of keys specified in the URI does not match number of key properties for the resource 'ReportingData.Task'."
}
}
}

Would you by any chance know, where the problem is?

Thank you very much in advance

Tasks Html reques...

Was this reply helpful? Yes No
LaelLeeH 91 on at

Like (0)

Report

Hi,
Did you find a solution to this? What were the keys that were required?
Regards
Lael

Was this reply helpful? Yes No
TomasSys 6 on at

Like (1)

Report

Hi, somehow this worked for me. My custom field's name is in the red rectangle.

Tasks custom fiel...

Was this reply helpful? Yes No
LaelLeeH 91 on at

Like (0)

Report

Brilliant. Thank-you. Works like a charm

Was this reply helpful? Yes No