Update site column without affecting version

%3CLINGO-SUB%20id%3D%22lingo-sub-1022234%22%20slang%3D%22en-US%22%3EUpdate%20site%20column%20without%20affecting%20version%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1022234%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20it%20possible%20to%20update%20a%20documents%20site%20column%20information%20without%20affecting%20the%20version%20number%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20part%20of%20a%20compliance%20requirement%20to%20add%20metadata%20to%20a%20document%20without%20changing%20the%20version%20number%20during%20the%20initial%20file%20upload%20and%20site%20column%20population.%20When%20you%20upload%20a%20new%20file%20you%20get%20version%201.%20Update%20site%20column%20information%20and%20you%20get%20version%202.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOther%20approaches%20and%20feedback%20are%20welcome.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENorm%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1022234%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDocument%20Library%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1023109%22%20slang%3D%22en-US%22%3ERe%3A%20Update%20site%20column%20without%20affecting%20version%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1023109%22%20slang%3D%22en-US%22%3EUnfortunately%20the%20answer%20is%20no%2C%20as%20soon%20as%20you%20upate%20metadata%20for%20a%20document%20a%20new%20version%20is%20going%20to%20be%20generated%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1023111%22%20slang%3D%22en-US%22%3ERe%3A%20Update%20site%20column%20without%20affecting%20version%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1023111%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20reply%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F60%22%20target%3D%22_blank%22%3E%40Juan%20Carlos%20Gonz%C3%A1lez%20Mart%C3%ADn%3C%2FA%3E.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20wonder%20if%20the%20%22PowerApps%20integration%20with%20SharePoint%20libraries%20%5Broadmap%20ID%3A%2057303%5D%22%20update%20can%20help%20to%20maintain%20version%201%20of%20the%20document%20when%20uploaded%20and%20the%20metadata%20populated%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20not%20a%20%22submission%2Fupload%20form%22%20using%20PowerApps%20might%20be%20the%20way%20to%20go%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20again.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENorm%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1023114%22%20slang%3D%22en-US%22%3ERe%3A%20Update%20site%20column%20without%20affecting%20version%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1023114%22%20slang%3D%22en-US%22%3E100%20%25%20sure%20the%20scenario%20is%20the%20same...SPO%20is%20the%20one%20that%20defines%20the%20rules%20here%20so%20no%20matter%20from%20where%20you%20are%20adding%20the%20metada%2C%20a%20new%20version%20is%20going%20to%20be%20generated%20when%20you%20update%20it%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1023116%22%20slang%3D%22en-US%22%3ERe%3A%20Update%20site%20column%20without%20affecting%20version%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1023116%22%20slang%3D%22en-US%22%3E%3CP%3EOh%20so%20no%20way%20to%20treat%20the%20initial%20upload%20and%20metadata%20population%20as%20a%20single%20transaction%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENorm%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1023426%22%20slang%3D%22en-US%22%3ERe%3A%20Update%20site%20column%20without%20affecting%20version%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1023426%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F111382%22%20target%3D%22_blank%22%3E%40Norman%20Young%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F60%22%20target%3D%22_blank%22%3E%40Juan%20Carlos%20Gonz%C3%A1lez%20Mart%C3%ADn%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWouldn%60t%20it%20be%20possible%20even%20if%20we%20write%20custom%20code%20to%20upload%20the%20attachment%20and%20metadata%3F%20to%20mark%20as%20V1%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1023480%22%20slang%3D%22en-US%22%3ERe%3A%20Update%20site%20column%20without%20affecting%20version%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1023480%22%20slang%3D%22en-US%22%3ENo%2C%20same%20situation...in%20the%20end%20you%20are%20just%20uploading%20the%20file%20so%20SPO%20is%20going%20to%20generate%20a%20new%20version.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1024011%22%20slang%3D%22en-US%22%3ERe%3A%20Update%20site%20column%20without%20affecting%20version%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1024011%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20replies%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F60%22%20target%3D%22_blank%22%3E%40Juan%20Carlos%20Gonz%C3%A1lez%20Mart%C3%ADn%3C%2FA%3E%26nbsp%3Band%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F453843%22%20target%3D%22_blank%22%3E%40O365Developer%3C%2FA%3E.%20I%20appreciate%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENorm%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1024456%22%20slang%3D%22en-US%22%3ERe%3A%20Update%20site%20column%20without%20affecting%20version%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1024456%22%20slang%3D%22en-US%22%3E%3CP%3EI%20worked%20around%20the%20issue%20by%20creating%20a%20%22drop%20off%22%20document%20library%20that%20has%20content%20approval%20turned%20on.%20On%20approval%2C%20and%20after%20metadata%20population%2C%20Power%20Automate%20copies%20the%20file%20to%20the%20destination%20document%20library%20as%20version%201.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20sure%20there%20are%20other%20approaches%20but%20this%20is%20what%20I%20came%20up%20with.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENorm%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
MVP

Hello All,

 

Is it possible to update a documents site column information without affecting the version number?

 

This is part of a compliance requirement to add metadata to a document without changing the version number during the initial file upload and site column population. When you upload a new file you get version 1. Update site column information and you get version 2.

 

Other approaches and feedback are welcome.

 

Thanks!

 

Norm

8 Replies
Unfortunately the answer is no, as soon as you upate metadata for a document a new version is going to be generated

Thanks for the reply @Juan Carlos González Martín

 

I wonder if the "PowerApps integration with SharePoint libraries [roadmap ID: 57303]" update can help to maintain version 1 of the document when uploaded and the metadata populated?

 

If not a "submission/upload form" using PowerApps might be the way to go,

 

Thanks again.

 

Norm

100 % sure the scenario is the same...SPO is the one that defines the rules here so no matter from where you are adding the metada, a new version is going to be generated when you update it

Oh so no way to treat the initial upload and metadata population as a single transaction?

 

Thanks.

 

Norm

@Norman Young @Juan Carlos González Martín 

 

Wouldn`t it be possible even if we write custom code to upload the attachment and metadata? to mark as V1?

No, same situation...in the end you are just uploading the file so SPO is going to generate a new version.

Thanks for the replies @Juan Carlos González Martín and @O365Developer. I appreciate it.

 

Norm

I worked around the issue by creating a "drop off" document library that has content approval turned on. On approval, and after metadata population, Power Automate copies the file to the destination document library as version 1.

 

I'm sure there are other approaches but this is what I came up with.

 

Thanks.

 

Norm