This is a major issue

If I configure a compare between two schemas, with field restrictions, and where clauses, save it as a profile, and copy to a new file, those settings all get clobbered when I try to configure the same compare between two different schemas/instances.

Even if the setup as is definitely applies to these new targets, the tool reexamines the table structure, and enables everything, tossing all my configs, even when I don't want it to. I'm sure this was envisioned as a helpful 'feature', but it's needless. It's destroying my work, and could have been accomplished with a "refresh schema" button or something.

The only way I have right now to retarget a project is to edit the XML file by hand. And it's not a few places. There db owner is embedded in 1198 places throughout the .dco file, in my case.

Even with such a feature, it should be smarter, retaining the settings selected, where still applicable, but first things first.