Forum Discussion
Adding New List Item - SharePoint Goes Crazy!
What used to happen:
- Navigate to my list. Click "New"
- Fill out all the fields in the form. Click Save
- Item is saved to the list
What started happening today:
- Navigate to my list. Click "New"
- Fill out the first field in the form
- SharePoint automatically saves a new line item in the list at that point with just the first field I just filled out populating it.
- Fill out the second field of the form.
- SharePoint saves a separate line item automatically with just the first and second field populated.
By the time I've filled out that one form, for one list line item and click "Save" SharePoint has created 12 separate new line items in the list - One for every field I filled out.
Any ideas?
Chris, it sounds like you are using a modern list in SharePoint Online? What exactly type of list are using? This is not the behavior I see for NEW items. I have a new modern list, I click New, as I complete my different fields I see no "saved" message and half-way through if I click Cancel no item is visible.
Editing is where things differ. If you click on the Title column to the view form in the details pane, you can click into a field and edit it, and as you move into another field it was save and show "Saved" with a checkmark. Or you click Edit All and take the entire form into edit mode which does NOT save changes per field. Can you confirm your list details?- 2nd report I've seen of this today. If no workflows are involved or flows based on item added / item modified triggers then I would submit a ticket to Microsoft.
As a work around for the lists you can do CUstomize powerapps forms for it, leave the defaults and do File > Save > then publish to introduce a powerapp form that works similar to the previous forms where you can save in one go around and not per column.SargentSynergy see post here: https://techcommunity.microsoft.com/t5/SharePoint/List-not-working-When-adding-item-it-saves-then-creates-multiple/m-p/239626#M21068
Have some screenshots of reproducing issue and powerapp work around (not realistic for larger environments), but also if you haven't make sure to get that ticket in!
