Preserve review context before replacing a file

Record review context before uploading a new file version, preserve page or playback anchors, and distinguish earlier-version comments afterward.

Last reviewed

Comments survive a new version upload, but an anchored comment continues to describe the version that was current when the anchor was created. Record the decision before replacing content so later readers can separate old feedback from the new file.

Four-step map for summarizing a review, noting its version context, uploading replacement content, and separating earlier comments from the current file.
The map shows the handoff between a version-bound discussion and a later upload. Open full-size screenshot.

What an anchor stores. A top-level PDF comment can keep a page number of 1 or greater. Audio and video comments can keep a whole-millisecond position starting at 0. Dosya also records the current version number with that anchor. Replies do not carry their own anchors.

Steps

  1. Open the current file version and choose Comments. Navigate to the relevant page or playback position before focusing the new-comment field; focusing media commentary pauses playback while capturing the position.
  2. Summarize what was approved, what remains open, and what the replacement is expected to change. Mention an eligible reviewer if the handoff needs attention.
  3. Send the comment and use its page or time control to verify the location. Keep the comment under 5,000 characters and limit mentions to 20.
  4. Upload the replacement through the file’s version workflow only after the context is visible in the thread.
  5. Reopen Comments on the new version. When an anchored comment belongs to an earlier revision, Dosya labels it vN; selecting it reports Comment was left on vN rather than pretending the old position belongs to the current bytes.
  6. Add a fresh current-version comment if the new document or media needs a new anchor. Editing the old message cannot move its original version anchor.
Launch review.pdf thread beside FILE DETAILS, used to preserve review decisions before a replacement version is uploaded.
The screenshot demonstrates where reviewers can leave durable context while checking the file identity and properties. Open full-size screenshot.

What remains and what changes. Uploading a version does not delete the existing discussion. The old comment text, author, time, and version anchor remain. Page numbers and media positions may no longer describe the same visual content in the replacement, so readers should follow the vN marker rather than infer equivalence.

If context is missing. Check that you posted to the correct file ID before uploading. If the old version comment was deleted, it cannot be restored through comment history; write a new message that explicitly identifies the earlier version and source of the recovered information.

Expected result

The replacement becomes the current file version while the prior review remains readable and visibly associated with its original vN context. New feedback can use a new current-version anchor.

Was this helpful?

Loading helpfulness results…

Voting saves a necessary ballot cookie for up to 180 days so you can change your answer.

Questions and replies

Ask about the steps in this guide. Questions are reviewed before publication.

Keep account details, credentials and private files out of public questions. Use private support for those.

Loading questions…

    Sign in to your Dosya account to ask a question.

    Check the outcome before you retry

    Use these shared checks when a task needs a second look.