Remap Variables and Conditions

Remap Variables & Conditions

Cleanup ⚡ tab → Project Analysis group

Remaps one or many variables to another variable, or one or many condition tags to another condition tag, in all topics, snippets, TOCs and targets — the fast way to consolidate duplicated variable sets or merge overlapping condition tags. Definitions in .flvar/.flcts files are left untouched.

To remap variables or conditions

1. On the Cleanup ⚡ tab, in the Project Analysis group, click Remap Variables & Conditions.
2. Choose Variables or Conditions at the top of the window.
3. The left list shows every variable/condition actually in use in your topics, snippets, TOCs and targets. Select one or more entries to remap from.
4. In the right list, select the single entry to remap to.
5. Click Remap Variables / Remap Conditions and confirm — the dialog lists exactly what will be remapped.

What happens

• Only the files that actually use the selected tokens are touched. They are backed up to a ZIP archive (in your configured backup folder) and checked out of source control first.
• Matching is exact-token: remapping Primary.A never touches Primary.AB.
• Condition lists are de-duplicated — remapping onto a tag the element already carries collapses to a single entry.
• A result dialog lists every changed file, and reminds you which old definitions are still present in your .flvar/.flcts sets — the tool deliberately never deletes definitions; remove them by hand when you are ready.

Notes

• Variables in TOCs and targets are matched in their [%=Set.Name%] form; in topics and snippets via MadCap:variable elements.
• Conditions set on images or in .props files, and condition expressions inside target build settings, are not remapped.
• There is no dry run and no in-app undo — the ZIP backup is your safety net.
• Use Analyze Condition Use and Export Variable Data to survey what is in use before consolidating.