Get Items return error

(2) Share

Report

Posted on by RG-20092028-0

Hi there,

I've built a task using Power Automate which automatically process a Microsoft Forms submission.

I've been using Get Items in some cases to verify if a certain value received from a Microsoft Forms field has already been inserted within a SharePoint List.

So far it's always been acting correctly.

On a testing phase to ensure that all branches of the task is correctly working, I've got an error when the Get Items is supposed to return at least one item.

The Filter Query is as simple as comparing the Title value of SharePoint List Items against the value received from the Microsoft Form field.

When it returns zero item, the Get Items works perfectly, but when return an item I receive this error:

ResponseSwaggerSchemaValidationFailure. The API 'sharepointonline' returned an invalid response for workflow operation 'Get_items_–_Request_to_Update' of type 'OpenApiConnection'. Error details: 'The API operation 'GetItems' is missing required property 'body/value/0/field_7'.'

I previously just tested a different Get Items in a different branch, which essentially does the same exact thing, and it had no error returning an item, but now that I received this error once, the Get Items that worked correctly is not working anymore. Note that the Filter Query receives the expected value.

Anyone can help with this?

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (1)

Suggested answer

Michael E. Gernaey 53,227 Super User 2025 Season 2 on at

Like (2)

Report

Hi

So its pretty straight forward, your schema says you should have a property called field_7 for each returned item

However the item that is being returned does NOT have it.

Can you please for through your List, and specifically look at each field until you find one called field_7.

Now I have to tell you, to do this is a pain, because field_7 is the internal name, telling me that someone created the List by importing data, where it will NOT name the internal name of a list column the same as it was in the source.

For instance, you have a field called FOO (its what you typed in the Label for naming it), when it was created, the back end called it foo as the internal name.

If someone exports data and imports it to a new sharepoint, it will NOT name it foo, it will name it fieldXXXXX based on the order it creates the columns

So field 7 is probably the 6index or 7index of the fields.

So thats why its doing it. if you want to share your list, look at how many columns there are and go to the list settings, and see if you click on EACH of the columns, when it goes to that column property page, the URL will have its name at the end of the URL

Find the one named field_7 (which I doubt you will find), but we need to start there to verify its there (as it clearly says its not)

Was this reply helpful? Yes No
Verified answer

RG-20092028-0 32 on at

Like (0)

Report

Hi FLMike,

Thank you very much for your response, I knew field_7 was the key to my problem, but I was wondering why it was referring to a field in which I never made any changes at all since all I did was tests with the flow.

I verified all the fields and found the field referring to field_7 which exists in the list, bizarre in my opinion.

However, when I saw which field was field_7, I decided to look into it before answering back, and realized it was a mandatory field, and when I built the list there was missing data in some records for that specific field.

So I simply added "N/A" to all the blank fields, and then ran the flow in all the different branches and it's working fine.

I appreciate your insight on the matter, which sent me looking in the right direction to fix the issue.

Have a good week

Was this reply helpful? Yes No