Nothing was deleted from your machine. Your original per-profile values are still recorded in the Windows registry, and the steps below show you how to read them back and reapply the ones you want. What changed is that the application now applies one value rather than one per profile.
What changed, and what happened to your settings
These settings are no longer stored on individual profiles:
When you first launched 26.6, Draftable carried these values across from your default profile only, and only where you had not already customised the equivalent application-wide setting. Values saved on any other profile were left in place but are no longer applied.
That is why a pattern you had saved on a custom profile, for example a “Changed Pages Only” profile that saved files as
CPO Redline - ..., appears to have disappeared. It has not been applied since the upgrade, but it is still recorded.
Step 1: Read your original profile settings
Your pre-26.6 profiles are stored as a single block of JSON in the registry. Draftable never writes to this value after the upgrade, so it stays exactly as it was.1
Open Windows PowerShell
Press the Windows key, type
PowerShell, and open Windows PowerShell. You do not need to run it as an administrator, because the value is stored under your own user profile.2
Print your original profiles
Paste the command below and press Enter. It only reads from the registry and changes nothing.This prints the full JSON for every profile you had before the upgrade.
3
Pull out just the filename patterns (optional)
If you only want the filename pattern for each profile, this command lists them as a table:The output looks something like this:
If the command returns nothing, there is no legacy profile data on this machine. That is expected on a fresh install, on a new machine, or where profiles were only ever delivered by Group Policy. Group Policy profiles are unaffected by all of this and continue to be applied by your administrator.
What the JSON fields mean
Within each profile in the output, these are the fields that correspond to the settings that moved:Step 2: Translate the token syntax
Filename tokens changed shape in 26.6. Before 26.6 they were written as long names in square brackets, for example[modified document name]. From 26.6 they are short names in curly braces, for example {modifiedName}.
Draftable still recognises the old square-bracket tokens when it builds a filename, so a pattern pasted in unchanged will produce the right result. The Filename pattern field and its live preview are built around the new tokens, though, so we recommend converting your pattern rather than pasting the old one in. Use this table:
Any free text in your pattern, such as
CPO Redline - , carries across exactly as it is.
Using the example above, CPO Redline - [modified document name] becomes CPO Redline - {modifiedName}.
Step 3: Reapply the pattern
1
Open the filename setting
In Settings, select Opening & Saving Files under the Files group, then find the Filename pattern field in the Output Filename section.
2
Enter your pattern
Type your free text and use the token buttons beneath the field to insert each token. The buttons insert the correct curly-brace token for you, so there is no need to type the braces by hand.
3
Check the preview
The Preview line beneath the buttons shows a sample filename built from your pattern. Confirm it reads the way you expect before closing Settings.
Getting distinct filenames with one pattern
Because there is a single pattern per machine, you can no longer attach a different filename to each profile. Where the distinction you need is between output types, the{outputType} token does the job automatically. It resolves to the label for the output being produced: Redline, Changed Pages Only, Tracked Changes, Side By Side, Departures Table or Changes Report.
A single pattern of:
Changed Pages Only - Contract for a Changed Pages Only export and Redline - Contract for a standard redline, with no manual step and no profile switching.
{outputType} covers differentiation by output type. It cannot insert arbitrary literal text tied to one specific profile, and it cannot distinguish two profiles that produce the same output type. If that is what your team needs, please get in touch and tell us how your profiles are set up, so we can record the use case with our product team.Notes for administrators
- The legacy per-profile data is a REG_SZ value named
RedlineProfilesunderHKCU:\Software\Draftable\RedlineProfiles. Draftable reads it as a recovery source and never writes to it, so it is safe to back up or copy between machines before an upgrade. - From 26.6, profiles are written to a separate value,
RedlineProfilesV3, under the same key. Clearing that value does not remove the legacy data. - The application-wide filename pattern is stored as
OutputFilenamePatternGlobalunderHKCU:\Software\Draftable\Frontend, and can be set centrally through Group Policy in the usual way. - On a machine-wide or roaming setup, run the recovery command as the user whose patterns you are recovering. The legacy value is per user.

