Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Power Automate - Building Flows
Unanswered

BUGS - No longer able to get ID or value of SharePoint lookup column

(0) ShareShare
ReportReport
Posted on by 498

I had a flow that was working, but will no longer return all of the columns in a SharePoint list. 

The Scope ID column is available in Dynamic content and its settings URL ends in Field=Scope.

jiwhite_1-1690487293811.png

But, when I try to run the flow and get the ID or value of the column using various connectors.

 

jiwhite_0-1690487221872.png

The trigger output does not contain Scope, even after deleting the trigger and recreating it.

 

 

 

{
"headers": {
"Transfer-Encoding": "chunked",
"Retry-After": "21600",
"Vary": "Origin,Accept-Encoding",
"X-NetworkStatistics": "0,525568,0,0,50287346,0,525568",
"X-SharePointHealthScore": "3",
"X-MS-SPConnector": "1",
"X-SP-SERVERSTATE": "ReadOnly=0",
"DATASERVICEVERSION": "3.0",
"SPClientServiceRequestDuration": "1013",
"SPRequestDuration": "1013",
"X-DataBoundary": "NONE",
"X-1DSCollectorUrl": "https://mobile.events.data.microsoft.com/OneCollector/1.0/",
"X-AriaCollectorURL": "https://browser.pipe.aria.microsoft.com/Collector/3.0/",
"SPRequestGuid": "a7de7fe2-1056-4f5f-90a5-f84120f7f044",
"request-id": "a7de7fe2-1056-4f5f-90a5-f84120f7f044",
"MS-CV": "4n/ep1YQX0+QpfhBIPfwRA.0",
"Strict-Transport-Security": "max-age=31536000",
"X-FRAME-OPTIONS": "SAMEORIGIN",
"Content-Security-Policy": "frame-ancestors 'self' teams.microsoft.com *.teams.microsoft.com *.skype.com *.teams.microsoft.us local.teams.office.com teams.microsoftonline.cn *.powerapps.com *.yammer.com *.officeapps.live.com *.office.com *.stream.azure-test.net *.microsoftstream.com *.dynamics.com *.microsoft.com onedrive.live.com *.onedrive.live.com securebroker.sharepointonline.com;",
"MicrosoftSharePointTeamServices": "16.0.0.23912",
"X-Content-Type-Options": "nosniff",
"X-MS-InvokeApp": "1; RequireReadOnly",
"Timing-Allow-Origin": "*",
"x-ms-apihub-cached-response": "true",
"x-ms-apihub-obo": "false",
"Cache-Control": "max-age=0, private",
"Date": "Thu, 27 Jul 2023 17:04:51 GMT",
"Location": "https://flow-apim-msmanaged-na-centralus-01.azure-apim.net/apim/sharepointonline/shared-sharepointonl-5eb43cd1-d4f1-4b3f-af12-1f25792409b4/datasets/https%253A%252F%252F ... /tables/c3278fbb-355f-4d02-8c1a-50d4a72348a2/onupdateditems?view=1507723d-8bae-40a1-94ec-ed58b97820ed&triggerstatecl=MTszO2MzMjc4ZmJiLTM1NWYtNGQwMi04YzFhLTUwZDRhNzIzNDhhMjs2MzgyNjA3NDI4ODE2MDAwMDA7MTc4ODkzNzI2MA%3d%3d",
"P3P": "CP=\"ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo OUR SAMo CNT COM INT NAV ONL PHY PRE PUR UNI\"",
"X-AspNet-Version": "4.0.30319",
"X-Powered-By": "ASP.NET",
"Content-Type": "application/json; charset=utf-8",
"Expires": "Wed, 12 Jul 2023 17:04:51 GMT",
"Last-Modified": "Thu, 27 Jul 2023 17:04:51 GMT",
"Content-Length": "2530"
},
"body": {
"@odata.etag": "\"5\"",
"ItemInternalId": "329",
"ID": 329,
"Title": "Archive NA-FFEM-QC-AZ PM Records",
"Lead": {
"@odata.type": "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
"Id": 18,
"Value": "Janine White"
},
"Lead#Id": 18,
"Importance": 0,
"IsObjective": {
"@odata.type": "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
"Id": 1,
"Value": "0 - No"
},
"IsObjective#Id": 1,
"Priority": {
"@odata.type": "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
"Id": 2,
"Value": "2 - Medium"
},
"Priority#Id": 2,
"SImpact0": {
"@odata.type": "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
"Id": 1,
"Value": "0 - No"
},
"SImpact0#Id": 1,
"CImpact": {
"@odata.type": "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
"Id": 5,
"Value": "0 - None"
},
"CImpact#Id": 5,
"field_8": 0,
"field_9": 0,
"StatusLookup": {
"@odata.type": "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
"Id": 1,
"Value": "1 - Idea"
},
"StatusLookup#Id": 1,
"field_5": 0,
"Notify": {
"@odata.type": "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
"Id": 2,
"Value": "1 - Yes"
},
"Notify#Id": 2,
"Status_x003a__x0020_Status": {
"@odata.type": "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
"Id": 1,
"Value": "Idea"
},
"Status_x003a__x0020_Status#Id": 1,
"Status_x003a__x0020_Status_x0020": {
"@odata.type": "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
"Id": 1,
"Value": "1.00000000000000"
},
"Status_x003a__x0020_Status_x0020#Id": 1,
"Lead_x003a__x0020_Name": {
"@odata.type": "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
"Id": 18,
"Value": " ... "
},
"Lead_x003a__x0020_Name#Id": 18,
"{Identifier}": "Lists%252fQuality%2bProjects%252f329_.000",
"{IsFolder}": false,
"{Thumbnail}": {
"Large": null,
"Medium": null,
"Small": null
},
"{Link}": "https:// ... /_layouts/15/listform.aspx?PageType=4&ListId=c3278fbb%2D355f%2D4d02%2D8c1a%2D50d4a72348a2&ID=329&ContentTypeID=0x010013C97D3A68BFC848A860A946FB92B6530004747C6512477D4192A44A134CBE652A",
"{Name}": "Archive NA-FFEM-QC-AZ PM Records",
"{FilenameWithExtension}": "Archive NA-FFEM-QC-AZ PM Records",
"{Path}": "Lists/Quality Projects/",
"{FullPath}": "Lists/Quality Projects/329_.000",
"{HasAttachments}": false,
"{VersionNumber}": "5.0",
"{TriggerWindowStartToken}": "MTszO2MzMjc4ZmJiLTM1NWYtNGQwMi04YzFhLTUwZDRhNzIzNDhhMjs2MzgyNjA3NDA4ODEzMDAwMDA7MTc4ODkzNzA2Mw==",
"{TriggerWindowEndToken}": "MTszO2MzMjc4ZmJiLTM1NWYtNGQwMi04YzFhLTUwZDRhNzIzNDhhMjs2MzgyNjA3NDI4ODE2MDAwMDA7MTc4ODkzNzI2MA=="
}
}

 

 

 

The HTTP request fails with the error, "The query to field 'Scope' is not valid. The $select query string must specify the target fields and the $expand query string must contains Scope.
clientRequestId: df57b37d-634c-4ed0-9415-0c322bb27100
serviceRequestId: a8b0caa0-806a-4000-141d-81499bfee7f4"

Using Get Item to get the record, then trying to read the field is also wrong.

  • jiwhite Profile Picture
    498 on at
    Re: BUGS - No longer able to get ID or value of SharePoint lookup column

    Existing items run the flow if the run is resubmitted, but new items fail to get the correct version of the list.

  • jiwhite Profile Picture
    498 on at
    Re: BUGS - No longer able to get ID or value of SharePoint lookup column

    Here is another thread started by @Grace-msk where multiple people have responded that existing flows are suddenly not working: Gettign BadRequest passed-in field "DynamicPropert... - Power Platform Community (microsoft.com)

  • jiwhite Profile Picture
    498 on at
    Re: BUGS - No longer able to get ID or value of SharePoint lookup column

    Here is an example today of another person, @WhatsHisName , reporting an old flow that is suddenly not looking up data correctly because the flow run doesn't match the code: Sharepoint GetFileItems Action failing for some re... - Power Platform Community (microsoft.com)

  • jiwhite Profile Picture
    498 on at
    Re: BUGS - No longer able to get ID or value of SharePoint lookup column

    This is not a new implementation.  Some lists were originally created using Excel upload months ago and I created flows to handle the data. 

    • Renaming a field is just changing the human readable label for column, which has another Id.  Changing the label shouldn't make a difference.
    • The problem is not that I can't get the related values from the Scopes table.  The problem is that the Scopes Lookup column is not available when the flow runs even though it is selectable in the flow.  When I originally brought the data over months ago, this was not an issue. The system has been in use since that time.  The Scope Lookup column was available and the values were retrieved seemlessly. Yesterday, the error started happening without changing anything in the structure of the list or the flow.  This is not an error that I created. I was just looking for a way to force the flow to get the correct version of the list that uses Scopes as a Lookup.  Other columns are also missing.
    • This should have nothing to do with how the lists were created.  If it does, then Microsoft has changed something without notice that is not backwards compatible.
  • jiwhite Profile Picture
    498 on at
    Re: BUGS - No longer able to get ID or value of SharePoint lookup column

    The original data was in Excel files.  If that's not a reliable way to create SharePoint lists, then Microsoft shouldn't enable it. Also, the data in the Settings doesn't match what is being sent to the flow.  That's also a Microsoft syncing problem somewhere. The system is transmitting corrupted data in a way I have no control over. I have to start from scratch.

  • jiwhite Profile Picture
    498 on at
    Re: BUGS - No longer able to get ID or value of SharePoint lookup column

    I have thousands of records that need to be maintained and migrated. It was working fine, then something changed in the system without me changing anything, and it's an intermittent issue.  When something suddenly breaks and I haven't changed the code in months, I'm not the cause of the issue. I didn't create the problem, Microsoft did.

  • wskinnermctc Profile Picture
    6,517 Super User 2025 Season 1 on at
    Re: BUGS - No longer able to get ID or value of SharePoint lookup column

    Why not try it correctly from creating blank lists instead of Excel uploads. Seems more appropriate to troubleshoot instead of saying the system isn't working.

     

    What you built isn't working, 

  • wskinnermctc Profile Picture
    6,517 Super User 2025 Season 1 on at
    Re: BUGS - No longer able to get ID or value of SharePoint lookup column

    I'd delete all of the SP Lists and Flows and start completely new creating blank lists without uploading the Excel files.

     

    It is going to keep causing problems even if you fix this, there will be something later on that will pop up. 

     

    Another thing that might be causing an issue is that ScopeId is a field for a list item is already in the system, so every item on every list has a ScopeId field. So it might be having an issue as that information is transferred across lists from lookups. 

  • jiwhite Profile Picture
    498 on at
    Re: BUGS - No longer able to get ID or value of SharePoint lookup column

    At this point, I'm just going to move the data to an enterprise SharePoint instead of Lists and tell people the system isn't working until the migration is complete.

  • abm abm Profile Picture
    32,488 Most Valuable Professional on at
    Re: BUGS - No longer able to get ID or value of SharePoint lookup column

    Hi @jiwhite 

     

    How about your second flow you did? Try running both and see. Let me know the results.

     

    Thanks

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Michael Gernaey – Community Spotlight

We are honored to recognize Michael Gernaey as our June 2025 Community…

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 566 Super User 2025 Season 1

#2
David_MA Profile Picture

David_MA 516 Super User 2025 Season 1

#3
stampcoin Profile Picture

stampcoin 492