Sharepoint list item version number incorrect on submittal

%3CLINGO-SUB%20id%3D%22lingo-sub-1109993%22%20slang%3D%22en-US%22%3ESharepoint%20list%20item%20version%20number%20incorrect%20on%20submittal%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1109993%22%20slang%3D%22en-US%22%3E%3CP%3EHello!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20SharePoint%20List%20with%20versioning%20turned%20on%20and%20have%20noticed%20that%20when%20a%20new%20Sharepoint%20List%20Item%20is%20created%2C%20it%20is%20actually%20showing%20as%20Version%202.0%20instead%20of%20Version%201.0%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20any%20reason%20why%20a%20newly%20created%20Sharepoint%20Item%20(that%20has%20not%20been%20modified%20by%20anyone)%20would%20have%202.0%20as%20the%20version%20instead%20of%20the%20expected%201.0%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20screenshot%20below%2C%20you%20can%20see%20it%20was%20submitted%2C%20but%20then%20another%20version%20was%20created%20at%20the%20same%20time..%20not%20sure%20why%20this%20would%20happen%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F165461i9618FC49279BAB80%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22sharepoint-incorrect-version-on-create.PNG%22%20title%3D%22sharepoint-incorrect-version-on-create.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1109993%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1111827%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%20list%20item%20version%20number%20incorrect%20on%20submittal%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1111827%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F203961%22%20target%3D%22_blank%22%3E%40Brandon%20McGinnis%3C%2FA%3E%26nbsp%3Bwe%20have%20had%20this%20issue%20too%2C%20but%20only%20when%20the%20list%20item%20was%20copied%20using%20a%20workflow%20from%20a%20different%20library%20to%20start%20with.%20The%20source%20library%20versioning%20works%20fine%20but%20the%20destination%20library%20versioning%20is%20skewed%20like%20this%20and%20jumps%20versions%20ahead.%20We%20have%20not%20found%20a%20solution%20and%20regrettably%20just%20ignore%20it%2C%20which%20is%20obviously%20not%20a%20fix.%20I%20would%20be%20keen%20to%20know%20if%20you%20come%20up%20with%20a%20solution%20as%20opposed%20to%20a%20workaround.%20Best%20of%20luck.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1112462%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%20list%20item%20version%20number%20incorrect%20on%20submittal%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1112462%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F517569%22%20target%3D%22_blank%22%3E%40KateAtACNM%3C%2FA%3EI%20found%20that%20the%20item%20was%20actually%20triggering%20a%20rogue%20Flow%20and%20updating%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHopefully%20you%20find%20a%20solution!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

Hello!

 

I have a SharePoint List with versioning turned on and have noticed that when a new Sharepoint List Item is created, it is actually showing as Version 2.0 instead of Version 1.0

 

Is there any reason why a newly created Sharepoint Item (that has not been modified by anyone) would have 2.0 as the version instead of the expected 1.0?

 

In the screenshot below, you can see it was submitted, but then another version was created at the same time.. not sure why this would happen?

 

sharepoint-incorrect-version-on-create.PNG

 

2 Replies

@Brandon McGinnis we have had this issue too, but only when the list item was copied using a workflow from a different library to start with. The source library versioning works fine but the destination library versioning is skewed like this and jumps versions ahead. We have not found a solution and regrettably just ignore it, which is obviously not a fix. I would be keen to know if you come up with a solution as opposed to a workaround. Best of luck.

@KateAtACNMI found that the item was actually triggering a rogue Flow and updating it.

 

Hopefully you find a solution!