Getting Planner Checklists in flow

[Fusion]

Hey guys I have been just made aware that I need to be able to get the Checklists that come when another user creates a new Planner Task. 

I have a flow that sends an email that gets printed but when my team put the phone number and pickup time in the checklist area there is no way to get this information in the email.

When I use Get Details all that is shown is the Title and Description. 

Any help would be very appreciated 

[v-yamao-msft · Accepted solution]

Hi @Fusion ,

I have made a test and I found that checklist could not be returned using a dynamic content directly.

There is similar request on Flow Ideas Forum, please feel free vote the idea at here:

https://powerusers.microsoft.com/t5/Flow-Ideas/Planner-get-more-details-from-a-task-in-planner-e-g-C...

Best regards,

Mabel

[shtryler]

I struggeled with a similar task for a few days, but in the end i managed to extract all the information from the tasks and the checklist items with the help of this weird trick 😉: http://johnliu.net/blog/2017/11/foreach-property-in-microsoftflow-json-with-xpath-microblog

The process does need a few steps but in the end it isn't too comlicated.

You start by getting the task details and parsing the result in JSON:

Parse JSON: (Get all the data from the taskdetails, way more than the dynamic content offers)

Content: body('Get_task_details')?['body']

(You can generate the schema from a sample task body or just use mine: https://pastebin.com/Y0ddkS9w)

Parse JSON checklist: (Seperate the checklist JSON from the task data for easyer handling)

Content: body('Parse_JSON')?['checklist']

(Schema can also be created from a sample checklist item, or use this: https://pastebin.com/4eNTtJ67)

The problem isthat the checklist items are not actually called "checklistItem" in the raw JSON but are individually named with their id. This is why we need to do the trick from the post mentioned above, where we turn the JSON into XML, get the checklist item id's from the XML, and then parse the JSON again with the id.

Compose JSON checklist root element: (Add a root Element, necessary for proper XML)

Inputs: {"root": body(Parse_JSON_checklist'')}

Compose JSON as XML nodeset:

Inputs: xpath(xml(outputs('Compose_JSON_checklist_root_element')), '/root/*')

Select array of checklist item ids from xml

From: outputs('Compose_JSON_as_XML_nodeset')

Map: xpath(item(), 'name(/*)')

Now we have an iterable array of the checklist item id's (or something resembling them) with wich we can proceed to parse the JSON data of each checklist item.

Apply to each checklist item:

Output('Select_array_of_checklist_item_ids_from_xml')

Compose checklist item id: (the id's com back a bit scrambled, this can be fixed with an easy string operation)

Input: substring(replace(items('Apply_to_each_checklist_item'), '_', ''), 4, 5)

Parse JSON checklist item: (Finally! This operation gives us all the data of the current checklist item)

Content: body('Parse_JSON_Checklist')?[outputs('Compose_checklist_item_id')])

(I guess the schema shuld be clear by now, but just in case 😉: https://pastebin.com/C6C19VYw)

The "Parse JSON checklist item" now gives you everything you need as dynamic content.

Hope this helps 😊

[Woody999]

This is really helpful but your final schame url is no longr valid - https://pastebin.com/C6C19VYw

any chance you still have this available?

Thanks.

[Woody999]

Never mind - worked it out myself.

Really excellent solution. I wouldn't have been able to achieve this without your post so thanks!

{

    "type": "object",

    "properties": {

        "@@odata.type": {

            "type": "string"

         },

        "isChecked": {

                "type": "boolean"

        },

        "title": {

                "type": "string"

        }

    }

}