software:squirrel:version_history
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| software:squirrel:version_history [2026/01/10 16:48] – support@smikar.com | software:squirrel:version_history [2026/01/10 17:42] (current) – support@smikar.com | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| This page explains how **version history is handled by Squirrel** when files are archived and later restored back into SharePoint. | This page explains how **version history is handled by Squirrel** when files are archived and later restored back into SharePoint. | ||
| - | It is intended | + | It is intended to explain |
| ---- | ---- | ||
| Line 9: | Line 9: | ||
| ==== 🎯 Overview ==== | ==== 🎯 Overview ==== | ||
| - | When Squirrel archives a file, the file and its available SharePoint versions are stored securely in Azure Blob Storage. When a user restores | + | When Squirrel archives a file, the file and its available SharePoint versions are stored securely in Azure Blob Storage. When a file is restored, Squirrel rebuilds the version chain in SharePoint so that the file can continue to function as a normal SharePoint document. |
| The restore process is designed to preserve version history and associated metadata as closely as possible, while operating within the constraints of Microsoft 365 and SharePoint’s versioning model. | The restore process is designed to preserve version history and associated metadata as closely as possible, while operating within the constraints of Microsoft 365 and SharePoint’s versioning model. | ||
| Line 23: | Line 23: | ||
| * File content is written back into SharePoint. | * File content is written back into SharePoint. | ||
| * Version-level metadata such as author and modified timestamps are applied where supported. | * Version-level metadata such as author and modified timestamps are applied where supported. | ||
| - | |||
| - | The objective is to reconstruct the version chain so that historical changes remain visible and traceable inside SharePoint. | ||
| ---- | ---- | ||
| Line 42: | Line 40: | ||
| Because this behaviour is ultimately controlled by Microsoft 365, exact stamping results may vary in some environments. | Because this behaviour is ultimately controlled by Microsoft 365, exact stamping results may vary in some environments. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== 🕒 Timestamps, Dates, and Timezones ==== | ||
| + | |||
| + | During restore, Squirrel attempts to apply original created and modified timestamps back onto files and versions where supported. | ||
| + | |||
| + | Because SharePoint and Microsoft 365 store and display timestamps using internal UTC values and tenant or user locale settings, administrators may observe minor differences in how dates and times appear before and after a restore. | ||
| + | |||
| + | These differences can include: | ||
| + | |||
| + | * Time values appearing shifted due to timezone or regional settings. | ||
| + | * Display formatting differences in SharePoint views or version history. | ||
| + | * System-generated timestamps associated with the restore operation itself. | ||
| + | |||
| + | The restore process does not rewrite historical events, but timestamp presentation and final write operations remain subject to Microsoft 365 platform behaviour. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== 🏷️ SharePoint Metadata Capture ==== | ||
| + | |||
| + | In addition to version history, Squirrel is designed to capture and restore SharePoint file metadata where supported by the platform. | ||
| + | |||
| + | This includes both standard and custom library columns. During archive and restore, Squirrel attempts to preserve values for commonly used SharePoint field types, including: | ||
| + | |||
| + | * Single line of text | ||
| + | * Multiple lines of text | ||
| + | * Choice | ||
| + | * Number | ||
| + | * Date and Time | ||
| + | * Person or Group | ||
| + | * Currency | ||
| + | |||
| + | Because SharePoint allows a wide variety of custom column types and configurations, | ||
| + | |||
| + | The objective of the Squirrel metadata process is to preserve business-relevant metadata wherever technically possible, while operating within Microsoft 365 and SharePoint platform constraints. | ||
| ---- | ---- | ||
| Line 49: | Line 83: | ||
| SharePoint supports both **major** and **minor** versions. Minor versions are often hidden in the user interface, but they still exist internally. | SharePoint supports both **major** and **minor** versions. Minor versions are often hidden in the user interface, but they still exist internally. | ||
| - | If the most recent change to a file before archiving was a minor version, the following | + | The following |
| * SharePoint rebuilds the historical version chain. | * SharePoint rebuilds the historical version chain. | ||
| Line 66: | Line 100: | ||
| ---- | ---- | ||
| - | ==== 🔍 What Administrators Should Expect | + | ==== 🔍 Following a restore |
| - | After a restore, | + | After a restore, |
| * A newly created top version representing the restored file. | * A newly created top version representing the restored file. | ||
| Line 74: | Line 108: | ||
| * Previously hidden minor versions becoming visible. | * Previously hidden minor versions becoming visible. | ||
| * Version timestamps and authors populated where supported by SharePoint. | * Version timestamps and authors populated where supported by SharePoint. | ||
| - | |||
| - | This is normal SharePoint behaviour when a file is programmatically rebuilt and does not indicate loss of history. | ||
| ---- | ---- | ||
software/squirrel/version_history.1768024137.txt.gz · Last modified: 2026/01/10 16:48 by support@smikar.com