cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
jay2703
Regular Visitor

Person or Group not showing in Output

I have a Flow that runs when a File is Created or Modified in a SharePoint Library. I've created a condition statement against fields in the Library. One of the condition fields is if Assigned To is Equal to Null (Person or Group field). When I run my flow, the condition always shows False. When I looked at the Output, the Assigned To field does not show up. In the Get File Properties step prior to the condition, I have it set to "Use all columns (Do not limit)" Why isn't this field showing up. Is there an issue with Person or Group fields in Condition Statements?

1 ACCEPTED SOLUTION

Accepted Solutions

It should show up. Did you add it after you added action file properties? May be you can remove the action and add again and see if that fixes the issue... I have Submitted By as People picker and it works perfectly fine.. See below...

 

sometimes all the properties may not be displayed and there is a more button that opens them. Please check that...

Please remember to Mark this as answer if this resolved the issue.

 

 

PrasadAthalye_0-1597425332912.png

 

 

Please Like and Mark this as Answer if it resolves your Issue.

Power Automate Community

View solution in original post

4 REPLIES 4
PrasadAthalye
Super User
Super User

Can you please upload flow picture?

 

Also I am not sure if you are using Workflow Tasks list because you are saying Assigned to. Typically, people picker control provides more columns and you can check DisplayName property if thats possible. Example below..

 

PrasadAthalye_0-1597423771392.png

 

Please Like and Mark this as Answer if it resolves your Issue.

Power Automate Community

The Assigned To is a custom field that I created in the SharePoint Library. 

 

jay2703_1-1597424100705.png

The condition is simple, It's actually the Get File Properties that is failing. 

 

jay2703_0-1597424016617.png

 

The Assigned To field is not showing up in the File Properties. 

Here is the Output Body:

{

  "@odata.etag": "\"2\"",

  "ItemInternalId": "162",

  "ID": 162,

  "Title": "1111",

  "Group_x0020_In_x0020_Work": {

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

    "Id": 0,

    "Value": "(1) Core Planning"

  },

  "Group_x0020_In_x0020_Work#Id": 0,

  "Status": {

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

    "Id": 1,

    "Value": "In-Work"

  },

  "Status#Id": 1,

  "Part_x0020_Number": "1111",

  "Part_x0020_Qty": 1,

  "Quote_x0020_Due_x0020_Date": "2020-08-14",

  "Part_x0020_Due_x0020_Date": "2020-08-21",

  "Editor": {

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

    "Claims": "i:0#.f|membership|email@company.com",

    "DisplayName": "Name, My",

    "Email": "Email@company.com",

    "Picture": "https://company.sharepoint.com/sites/tcs/Engineering/Tool/_layouts/15/UserPhoto.aspx?Size=L&AccountN...",

    "Department": "Engineering",

    "JobTitle": "Engineer"

  },

  "Editor#Claims": "i:0#.f|membership|email@company.com",

  "Modified": "2020-08-14T14:29:00Z",

  "Created": "2020-08-14T14:28:17Z",

  "Author": {

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

    "Claims": "i:0#.f|membership|email@company.com",

    "DisplayName": "Name, My",

    "Email": "Email@company.com",

    "Picture": "https://company.sharepoint.com/sites/tcs/Engineering/Tool/_layouts/15/UserPhoto.aspx?Size=L&AccountN...",

    "Department": "Engineering",

    "JobTitle": "Engineer"

  },

  "Author#Claims": "i:0#.f|membership|email@company.com",

  "OData__DisplayName": "",

  "{Identifier}": "POD%2bTool%2bQuotes%252fTest%2bFile%2b1.xlsx",

  "{IsFolder}": false,

  "{Thumbnail}": {

  },

  "{Link}": "https://company.sharepoint.com/sites/tcs/Engineering/Tool/POD%20Tool%20Quotes/Test%20File%201.xlsx?d...",

  "{Name}": "Test File 1",

  "{FilenameWithExtension}": "Test File 1.xlsx",

  "{Path}": "POD Tool Quotes/",

  "{FullPath}": "POD Tool Quotes/Test File 1.xlsx",

  "{IsCheckedOut}": false,

  "{VersionNumber}": "2.0"

}

 

 

It should show up. Did you add it after you added action file properties? May be you can remove the action and add again and see if that fixes the issue... I have Submitted By as People picker and it works perfectly fine.. See below...

 

sometimes all the properties may not be displayed and there is a more button that opens them. Please check that...

Please remember to Mark this as answer if this resolved the issue.

 

 

PrasadAthalye_0-1597425332912.png

 

 

Please Like and Mark this as Answer if it resolves your Issue.

Power Automate Community

View solution in original post

I have the "Use all columns (Do not limit)" checked in the Advanced Get File Properties. The Library I'm using has existed as is for a number of years. I am trying to recreate an existing SharePoint Designer flow since it is being discontinued. I will try removing the File Properties step and reinsert it. 

 

I appreciate you taking the time to look at this.

 

Thanks!!

Helpful resources

Announcements
UG GA Amplification 768x460.png

Launching new user group features

Learn how to create your own user groups today!

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

M365 768x460.jpg

Microsoft 365 Collaboration Conference | December 7–9, 2021

Join us, in-person, December 7–9 in Las Vegas, for the largest gathering of the Microsoft community in the world.

Top Solution Authors
Top Kudoed Authors
Users online (1,149)