SharePoint Create Item ignores some fields

[ABureaux]

1. List created in SharePoint
2. Field types are all "String"
3. I already deleted and re-added the Create Item task

I created a flow in Power Automate. First task is to parse JSON. I can see all my data in the returned data (see below for a sample).

(In the above image, I am specifically missing the four highlighted fields)

Next task is to take that raw data and dump it into my SP list. Within the Create Item task, I can see every field from my SP list, and  I assigned every field to its corresponding strings from the JSON response (see example below).

As mentioned, the four strings I have highlighted above get ignored by the Create Item task. When I test, there are no errors, but when I inspect the successful run, those four items are missing from the SharePoint's Create Item task. The image below is a snip from my test. Compare that to the image above: It skips from "INV investigation" to "INV Reoccurance" (the fourth missing field is located in a different spot within the SP list, so including it was too difficult).

Any ideas?

[poweractivate]

@ABureaux 

First, check and make sure the SharePoint Site URL in the Power Automate SharePoint Create Item Action is set to the correct Site and Library/List, rather than perhaps another copy of the Site, and/or Library/List, that had the columns not present there yet for example.

If you are sure the above is correct, then try this:

(If needed, or if you prefer, you can do the below steps on a Copy of the Flow just in case i.e. Save As... first):

1. Click on the three ellipses near Power Automate SharePoint Create Item Action, take a note of the name of the connection circled in red below in case.  Delete the SharePoint Create Item Action from Power Automate (using the "Delete" option indicated with a red box below), save the Flow and close the Flow.

2. Delete the SharePoint Connection(s)

3. Go into Power Automate and add the Create Item Action into the Flow.

4. It should ask you to sign in and create a new Connection - do as it says.

5. See if it stops skipping the columns now.

[ekarim2020]

As a test, what happens when you make those fields required within SharePoint. Does that help expose the error or some other underlying issue in the flow?

Ellis

[ScottShearer]

@ABureaux 

You might try this:

1. Create a SharePoint view that contains only the columns that you need
2. Specify that view in the Create item configuration 
   1. Click on Advanced options
   2. Select the view

[poweractivate]

@ABureaux 

In case that my previous post or none of the other posts worked for you, try to create a test "View" and place about 5 to 10 columns max in there as troubleshooting step. Then use in Power Automate the 'Limit columns by view' then select the "test View" that you created.

This troubleshooting step above might change the context - in case it worked, you could either go with it, or try and find out why it doesn't work without limiting the view. Please keep in mind that I believe Power Automate does not show an unlimited number of columns there for the fields, which is why this feature is there in case. If even after limiting the columns it still did not show those 4 specific columns, and you tried what I suggested from my previous post, please indicate here that even after you tried these things it still did not work for you.

Before doing this part above, and right , try those steps I gave as well, possibly after creating that View as well but before selecting the view from Power Automate, in case. In general the steps I gave  before about deleting and recreating the connection, should not be necessary on a regular basis -  those are just some troubleshooting steps as well.

[ABureaux]

Thank you everyone for the responses!

@poweractivateCorrect and tried. No luck 😞

@ekarim2020I will try this in the off hours. I would guess that it causes the flow to fail though

@ScottShearerBecause the initial response I get (from Survey123) is rather large and difficult to sort through. In some cases, as a result of how the "search" feature works, it is almost impossible to find a specific value. The Parse JSON makes this task very easy by comparison. Below is how the raw response looks from Survey123. To search for something, you need to type all of the leading HTML tags rather than "Reason for..." (in this particular example). Some questions have a lot of text formatting, so you cant see any identifying text in the drop-down 😞 Hence the Parse JSON

Not sure why I didn't think to try this sooner, but I just tried using "Initialize Value" and "Set Value" immediately after the Parse JSON. Again, I could see my responses in the Parse JSON, but my Set Value came back NULL. I swapped from the Parse JSON to the initial response and now my values are now visible... No idea why this is happening. Doesn't appear to be a SP problem, but rather a problem with the Parse JSON task.

Comparing these missing values to the couple hundred other values I am getting, there are no differences in the data type or how the Parse JSON was set-up (I only used value type "NULL" for my "Generate from Sample").

[ScottShearer]

@ABureaux 

You might try this:

1. Create a SharePoint view that contains only the columns that you need
2. Specify that view in the Create item configuration 
   1. Click on Advanced options
   2. Select the view

You may be running into some type of list threshold issue.

[ekarim2020]

One last thing to try: use Save As to make a new copy of your flow and then test this new version:

Remember to turn off the original flow, and then turn on the new flow before testing.

Sometimes, for unknown reasons flows exhibit unexplained behaviour that does not make sense or makes them run very slowly. There could be some corruption in the flow that we cannot see but exists behind the scenes. I've had to do this few times to "fix" some of my flows. I've also recommended that some users on the forum to do the same - which did fix the problem for some when everything else they tried else failed to resolve their issue.

Ellis

[ABureaux]

Good to know. I'll give this a shot as well. Thank you!

[sadingle]

I had the same issue, what I did to solve it was to create another "Parse JSON" above the old step, run the flow to generate the schema from the Filter array and delete the old "Parse JSON" step.

The new mappings looked completely different after the re-parse even though all fields have spaces as seen below:

OLD:

NEW: