The unmapped section within FolderDiff represents two possible scenarios. Files that appear in this section are either files within the scope of the diff path but not the client mapping, or files that are still in the have table but no longer in the scope of the client mapping.
Files within the scope of the diff path, but not in the scope of the client mapping
Consider the following client view mapping:
If you select "//depot/main/..." as the directory to diff, then all
files under "//client/main/..." get diffed, not just the files under "//client/main/qt/...".
P4V displays this output in a single hierarchy, which can seem confusing and misleading. For example:
This is always the way this output is displayed in P4V, even though the user clicks on //depot/main
/ and only //depot/main/qt
is mapped in the client.
FolderDiff, however, displays the hierarchy like the client view mapping, which means that top level directories look more like the client mapping:
Files that fall outside this mapped scope, appear in the unmapped files section. In the case of the above tree, //depot/bin/...
appears in the unmapped section.
To avoid this problem, you should always select the diff at the lowest folder of the mapping that you have, for example choosing "//depot/main/qt/..." instead of "//depot/main/..."
Files that are in the have table, but no longer in the client mapping
This can happen when a user changes their client mapping and does not sync. These files appear in the unmapped section of Folderdiff.
To fix this problem, you can either change your client view so these files are back within the client mapping or simply run a full sync to reconcile the have table.