View Categories

Bringing Existing Content Into the Tracker

1 min read

You can add older or external content to the tracker, but the system does not support CSV imports or automated uploads. The safest way to bring existing data in is controlled copy and paste.

What You Can Paste In #

You can paste rows directly into Content_Log, including only the fields you want, such as:

  • Title
  • Platform
  • Type
  • Status
  • Product (optional)
  • URL
  • Notes

Avoid pasting into system columns (ItemID, Version, Active, VersionDate, LastUpdated, SnapshotPeriod, ChangeNote, ChangeType).

What the System Fills Automatically #

After pasting and running repair tools, the tracker will generate:

  • ItemID
  • Version number
  • Active status
  • VersionDate
  • LastUpdated
  • SnapshotPeriod
  • ChangeNote (“Initial version”)
  • ChangeType (“0 – New”)

These system fields initialize when the row is fully recognized by the script.

After You Paste #

Run the following tools to correct formatting and restore system behavior:

  1. Content Tools → Admin → Setup / Repair Sheet
  2. Content Tools → Admin → Constrain Active Checkboxes
  3. Content Tools → Admin → Normalize Active Column
  4. If dropdowns disappear, run Refresh Options

If rows still show missing system fields after this, run:
Content Tools → Admin → Generate System Fields for Selected Rows
(This fills in all required system values without touching your content.)

Handling Older Content with Dates #

If your legacy data includes VersionDate but not LastUpdated, run:
Sync LastUpdated to VersionDate
This ensures dashboards and snapshots use consistent dates.

Limits to Be Aware Of #

Pasted legacy content will not:

  • Rebuild past version history
  • Populate the Revisions log retroactively
  • Link older versions together
  • Interpret custom version numbers
  • Bring in past change notes or ChangeTypes

The tracker starts clean history from the moment you paste the latest version.

Best Practice #

For large migrations, paste only the current version of each item.
Then use Create New Version and Archive Selected Item going forward.
This gives you a clean, consistent version history from the point of adoption onward.

Shopping Cart