Answered

Asana Get project by ID doesn't work

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

The Asana option of "Get Project by ID" serves no purpose since you apparently can't get the Project Info from any trigger except "When a Project is created".

I have a flow that triggers when a Task is created and I have to specify the project by name in the dropdown, but I can't then act on the the Project Name/ID using dynamic fields.

Categories:

Using connectors

I have the same question (0)

All responses (3)

Answers (1)

v-alzhan-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @Anonymous ,

The Project ID column in the "Get Project by ID" action require a Project ID, and we could get the Project ID from the trigger "When a Project is created".

we could only enter the correct Project ID in the Project ID column in the "Get Project by ID" action.

Best regards,

Alice

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

I have the trigger "When a task is created" that seems to provide all of the necessary data, but Flow isn't seeing that data as available.
There is other information I would like to use from this that is clearly available and simply not mapped.

Was this reply helpful? Yes No
Verified answer

JatinSanghvi Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!
Since the project IDs, are not yet defined in the schema of the trigger response, you will need to parse the JSON response from trigger explicitly. Below I have copied screenshot of a Flow that enlists business phones of each user. You can build a similar Flow to suit your requirement.
Add a New Step -> Built-in -> Control -> Apply to each action. Set 'Select an output' field to 'data' for Asana.
Within the 'Apply for each' action, add New -> Built-in -> Data Operations -> Parse JSON action.
Set the 'Content' field to 'Current Item'.
For 'Schema', click 'Generate from sample', use one of the child items within 'data' array' of the trigger response that you posted above. Once the schema is auto-generated, you can remove properties from the schema definition that you are not going to use.
Add another 'Apply for each' action within the first 'Apply for each' action. This time select 'projects' of 'Select an output' field.
Within the inner loop, you will be able to fetch the individual project properties and operate on them.
Let me know if this works.

Was this reply helpful? Yes No