Home

Content Search on SharePoint and OneDrive referencing the wrong Modified date

%3CLINGO-SUB%20id%3D%22lingo-sub-236429%22%20slang%3D%22en-US%22%3EContent%20Search%20on%20SharePoint%20and%20OneDrive%20referencing%20the%20wrong%20Modified%20date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-236429%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20O365%20Content%20Search%20against%20content%20in%20SharePoint%20or%20OneDrive%2C%20the%20Created%20field%20data%20is%20accurate%2C%20but%20the%20Last%20Modified%20date%20is%20referencing%20the%20date%20the%20document%20itself%20was%20last%20modified%20prior%20to%20migration%20in%20SharePoint%2FOneDrive%2C%20not%20the%20date%20last%20modified%20in%20SharePoint%2FOneDrive%2C%20which%20is%26nbsp%3Breset%20on%20upload.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20leads%20to%20results%20like%20the%20one%20below%2C%20where%20the%20modified%20date%20is%20well%26nbsp%3B%3CSTRONG%3Ebefore%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Ethe%20Created%20date!%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20310px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F43619i954AEACEA2158AF8%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22modified.PNG%22%20title%3D%22modified.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EThis%20is%20a%20problem%20because%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1)%20retention%20and%20destruction%20policies%20created%20in%20the%20Security%20and%20Compliance%20Center%20and%20applied%20against%20SharePoint%2FOneDrive%20will%20respect%20the%20last%20modified%20date%20displayed%20in%20those%20systems%20(we%20have%20tested%20this%20and%20confirmed%20with%20Microsoft).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2)%26nbsp%3BTherefore%20the%20Content%20search%20is%20not%20able%20to%20generate%20reports%20of%20pending%20content%20to%20be%20disposed%20of%2C%20or%20content%20that%20may%20be%20disposed%20of%2C%20in%20the%20case%20of%20existing%20or%20potential%20policies%20that%20hinge%20on%20date%20last%20modified.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E3)%20This%20is%20especially%20problematic%20because%20the%20modified%20date%20of%20a%20document%20is%20reset%20in%20SharePoint%20and%20OneDrive%20if%20uploaded%20or%20dragged%20using%20the%20browser%2C%20but%20is%26nbsp%3B%3CSTRONG%3Enot%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eupdated%20if%20uploaded%20using%20the%20OneDrive%20Sync%20Client%20in%20Windows%20Explorer%2C%20resulting%20in%20variable%20conditions%20across%20different%20sites%20and%20OneDrive%20accounts.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20way%20to%20generate%20reports%20against%20the%20actual%20SPO%2FOneDrive%20date%20modified%20value%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-236429%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOneDrive%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-733638%22%20slang%3D%22en-US%22%3ERe%3A%20Content%20Search%20on%20SharePoint%20and%20OneDrive%20referencing%20the%20wrong%20Modified%20date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-733638%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F137385%22%20target%3D%22_blank%22%3E%40snyderdavida%3C%2FA%3E%2C%3C%2FP%3E%3CP%3Ethe%20column%20AA%2C%20is%20this%20the%20result%20from%20the%20library%20or%20is%20it%20from%20search%3F%3C%2FP%3E%3CP%3EWhen%20it%20comes%20from%20search%2C%20there%20is%20a%20possibility%20to%20change%20the%20order%20in%20crawled%20properties.%20Reference%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fsposupport%2F2018%2F01%2F27%2Fdifferences-between-the-created-or-modified-date-in-search-results-compared-to-listlibrary-view%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.technet.microsoft.com%2Fsposupport%2F2018%2F01%2F27%2Fdifferences-between-the-created-or-modified-date-in-search-results-compared-to-listlibrary-view%2F%3C%2FA%3E%3C%2FP%3E%3CP%3Echeers%2C%3C%2FP%3E%3CP%3EDennis%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
snyderdavida
Occasional Contributor

In O365 Content Search against content in SharePoint or OneDrive, the Created field data is accurate, but the Last Modified date is referencing the date the document itself was last modified prior to migration in SharePoint/OneDrive, not the date last modified in SharePoint/OneDrive, which is reset on upload.

 

This leads to results like the one below, where the modified date is well before the Created date!

modified.PNG

This is a problem because:

 

1) retention and destruction policies created in the Security and Compliance Center and applied against SharePoint/OneDrive will respect the last modified date displayed in those systems (we have tested this and confirmed with Microsoft).

 

2) Therefore the Content search is not able to generate reports of pending content to be disposed of, or content that may be disposed of, in the case of existing or potential policies that hinge on date last modified.

 

3) This is especially problematic because the modified date of a document is reset in SharePoint and OneDrive if uploaded or dragged using the browser, but is not updated if uploaded using the OneDrive Sync Client in Windows Explorer, resulting in variable conditions across different sites and OneDrive accounts.

 

Is there a way to generate reports against the actual SPO/OneDrive date modified value?

 

1 Reply
Highlighted

Hi @snyderdavida,

the column AA, is this the result from the library or is it from search?

When it comes from search, there is a possibility to change the order in crawled properties. Reference https://blogs.technet.microsoft.com/sposupport/2018/01/27/differences-between-the-created-or-modifie...

cheers,

Dennis