Dynamic Content not pulling through information from Sharepoint list

[Criptop]

Hi All,

I have a SharePoint list which is populated through a Power Apps form. I have a flow set up so that when an item is created, it sends a confirmation email to the person who completed the form (the Requestor):

Note that the "To" field is populated with dynamic content - Created By Email. This works fine. 

The form on Power App automatically captures the current user (field is called "Requestor's_Name"), and that user's manager (field is called "Requestor's_Manager"), and stores the information as Person fields in the sharepoint list:

I would like to populate the above email with information such as "Requestor's_Manager DisplayName" which is available through dynamic content. However, when the email is sent the information is blank. So the last line on the email above will read "An email has been sent to your manager, ,......". Why is this information not being pulled through?

I would also like to use this information later in the flow by sending an approval to the manager's email by entering dynamic content "Requestor's_Manager Email" into the approval Assigned To field:

but because the information is not pulled through, it doesn't work.

Similarly, if I was to change "Created By Email" to "Requestor's_Name Email" in the Send an Email step above:

The flow fails because the information is blank, therefore the "To" field of the Send an Email step is null. What is stopping this information being pulled through?

Thanks in advance

[abm]

Hi @Criptop 

Have a look on the person field 'Requestor's_Manager' values using flow run history.

It should return something like this

[
{
"@odata.type": "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
"Claims": "i:0#.f|membership|ajith.madathil@spinhope.com",
"DisplayName": "xxxxx",
"Email": "xxxx.xxxxx@xxxxx.com",
"Picture": "https://xxxxx.sharepoint.com/_layouts/15/UserPhoto.aspx?Size=L&AccountName=xxxxx.xxxxx@spinhope.com",
"Department": "Contractor Department",
"JobTitle": "Solution Architect"
}
]

Add a Parse JSON step to iterate each values from this.

Thanks

[Criptop]

Hi @abm,

Thank you for your reply. I obtained the respective code you described for 'Requestor's_Manager':

{

  "@odata.type": "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",

  "Claims": "i:0#.f|membership|xxxxxxx@xxxxxx.com",

  "DisplayName": "xxxxxxx",

  "Email": "xxxxxxxxx@xxxxxxx.com",

  "Picture": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.aspx?Size=L&AccountName=xxxxxxxxxxxxxxx@xxxxxxxxxxxxxx.com",

  "Department": "xxxxx",

  "JobTitle": "xxxxxxxxxxxxxxx"

}

After wathcing @RezaDorrani's very helpful YouTube video on data operations, I added a Parse JSON step to the flow.  For the content field, I used the field 'Requestor's_Manager' and I used the above code to generate a schema using the 'Generate from sample' function which generated this schema:

{

    "type": "object",

    "properties": {

        "@@odata.type": {

            "type": "string"

        },

        "Claims": {

            "type": "string"

        },

        "DisplayName": {

            "type": "string"

        },

        "Email": {

            "type": "string"

        },

        "Picture": {

            "type": "string"

        },

        "Department": {

            "type": "string"

        },

        "JobTitle": {

            "type": "string"

        }

    }

}

However, when I ran it, I got this error message:

Can you please advise what I should do? Or can you please direct me to any tutorials or articles that could provide more information?

Thanks

[abm]

Hi @Criptop 

Look on the property called 'content' and there is no value hence its failing. Its a data quality issue from your end.

Check the flow history and check the above property.

Thanks

[Criptop · Accepted solution]

Hi, for anyone seeing this in the future, this is what I did to solve the problem:

1. I removed the apostrophe in the fields such as “Requestor’s_Name”, “Requestor’s_Manager” etc in the SharePoint List
2. Deleted and re-added the data connection to the SharePoint List in my PowerApp
3. Deleted and rebuilt the form in my PowerApp that captures the data for the SharePoint List (including linking it to the ‘new’ SharePoint list data connection)
4. I deleted the very first step of the Flow, the SharePoint action “when an item is created” and replaced it with a new “when an item is created” step and connected it to the SharePoint list
5. Went through every step in my flow and replaced the dynamic references to the old first step with new dynamic references to the new first step.

When doing this, I was able to use dynamics references to refer to, for example, “Requestors_Email”, “Requestors_Manager” etc as required without any Parse JSON, Compose or Select steps. This makes the flow more straightforward and intuitive. The flow now works as expected.