web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / BUGS - No longer able ...
Power Automate
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.

Categories:
I have the same question (0)
  • abm abm Profile Picture
    32,865 Most Valuable Professional on at

    Hi @jiwhite 

     

    The error is related to your Lookup column 'Scope' the way you retrieving via HTTP request.

     

    In $select you have to specify which columns you need to retrieve from lookup column and use expand with your lookup column name. For example, your lookup (Scope) list has several columns like Title, Category and you need Title and Category, then your query string should be as follows:

     

    $select=Scope/Title,Scope/Category&$expand=Scope

     

  • wskinnermctc Profile Picture
    6,519 Moderator on at

    What type of columns are "Scope Id", "Notify Id", "Priority Id" in your SharePoint list. Are these lookup columns?

     

    Are you using lookup columns on a SP List which lookup from multiple other lists?

     

    I see some things name "field_8" or "field_9" for columns, do these columns not have full names or were they made using an Excel table upload?

     

    I think your issues are coming from columns that aren't named very well so they are hard to find. And the difference between Id of a lookup column and the Value of a lookup column. 

  • jiwhite Profile Picture
    498 on at

    Yes, they are lookups to other lists.  The only one that is not working is Scope. I originally transferred an Excel sheet to SharePoint, then renamed columns, including in Settings. I go to the URL in settings to find the SharePoint name of columns, for example, Supplier Impact is SImpact0. However, Scope is completely missing when it runs, but it was functional before, and I can select the field through Dynamic content, but it fails when it runs.

  • jiwhite Profile Picture
    498 on at

    I added the HTTP request because I was hoping to work around whatever was causing the field to be missing in the trigger. I know that triggers don't pass all the fields all the time, especially extra values from lookups.  Doing Get Item for the trigger record, then trying to get Scope Id from that using Dynamic content also fails. I didn't care if I I got all the info associated.  I was just trying to get the Scope Id to do another Get Item to the Scopes list.

  • jiwhite Profile Picture
    498 on at

    For example, this

    jiwhite_1-1690504665666.png

     

    also fails with the error, "The 'inputs.parameters' of workflow operation 'Get_Scopes_item' of type 'OpenApiConnection' is not valid. Error details: The resolved string values for the following parameters are invalid, they may not be null or empty: 'id'"

     

    jiwhite_0-1690504538268.png

    Even though I selected the Scope ID from Dynamic content, it's null.

  • jiwhite Profile Picture
    498 on at

    Also, if I use Co-Pilot to try to get all the columns, Scope is missing from the list of columns it recognizes.

    jiwhite_2-1690506029584.png

    even though it is in the columns in the list settings.

    jiwhite_3-1690506119136.png

    How is this possible when there are no advanced options and no custom trigger settings? Multiple columns are missing. It's like there's a completely different list being looked at, but when I make a change in an item in the list, the flow is triggered and Scope is just the first columns that fails. I think that something corrupted the flow and I have no way of fixing it other than creating it again from scratch, which is a huge waste of time.

  • abm abm Profile Picture
    32,865 Most Valuable Professional on at

    Hi @jiwhite 

     

    Thanks for your reply. Could you please double click (List Settings > Columns> the Column Scope  and check the URL where it shows field=Scope. You sure its column name is Scope. Yes I can see the Display name is Scope. If you renamed then it must be under the old name. Could you please post a screen shot of the url.

     

    Thanks

  • jiwhite Profile Picture
    498 on at

    The field name is Scope in the URL.

    jiwhite_0-1690559280596.png

    Also, the ID in the dropdown list for the trigger matches the table ID in the URL.

    jiwhite_0-1690559658197.png

    It appears that the flow is accessing an old version of the definition of the list somehow. I've already tried deleting the trigger, then adding it again to try to force it to get the current metadata. The flow was working before, then started failing without me editing the flow, so something changed in the cloud.

     

    I was able to create a new flow that has access to Scope without failing.

    This:

    jiwhite_4-1690560345408.png

    Runs fine:

    jiwhite_3-1690560325895.png

    I'd just like to force the old flow to refresh its definition.

  • abm abm Profile Picture
    32,865 Most Valuable Professional on at

    Hi @jiwhite 

     

    Thanks for your screenshot. Yes the internal name is correct. Could you create a new flow just that trigger and add a compose action step below. Run the flow and see if that Scope filed is returning or not? Once that done I will tell you the next steps.

     

    Thanks

  • jiwhite Profile Picture
    498 on at

    The new flow has no problem with Scope.

    jiwhite_0-1690561308088.png

     

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

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 501 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 323 Moderator

#3
abm abm Profile Picture

abm abm 237 Most Valuable Professional

Last 30 days Overall leaderboard