The work around that I figured out was the following:
Take a certain softsynth (SampleTank 3), as opposed to many different synths, like I used to do, and make maps for each "section" of drums. For instance ST3 - Kicks, ST3 - Snares, ST3 - Toms, ST3 - Cymbals, etc. This way if it disappears for whatever reason, which it will, when you need to use it again, you obviously know how to map it because the channel output #'s remain the same. Also, what's cool about using this approach is you can use a LOT more samples for each "section". So, here's an example.
In ST3 I set it up where I assign ALL 16 chs to my favorite drum kits, and that, more than likely, will give you more than enough samples for each "section". Then, create the maps and use whatever channels you need to assign to whatever, and however many samples you need for kicks, snares, toms, cymbals, etc. Now, the only drawback is if you use the Sonar Step Sequencer then you'll only be able to use one section at a time; so essentially, you CAN'T use Sonar's Step Sequencer. However, I DO believe that SampleTank has it's own step sequencer, as do quite a few other software synths.
So, until the developers at Sonar decide to AT LEAST take this OUT of the Preferences, and do MANY other updates, I'm afraid this is what we're stuck with.
BaDumpBump...PSSHH!
KC