The problems with MIDI in Sonar never end.
I can't even explain this one, but I inserted a bunch of track templates, and now all my drum maps are gone for other tracks!  WHAT?

What kind of Templates ?
If we are going to do surgery, we are going to need a little more info .
 
I would take a wild guess and say it is a midi track that contained a drum map.
Im not sure about you, but here my midi drum maps open with my Drum track templates.

Hi Chuck,
 
They were created in projects with drum maps, but these softsynth track templates do not point to them.  I think it is just grabbing all drum maps from the project it is created in.  
 
Thanks,
Adam

I wish I could pin point the exact cause Adam.
To be honest, I cant recall if a Midi Track Template will retain "Custom Drum Maps" or Drum Map presets that come with Sonar.
 
I'd like to see a revamp done on Drum Maps and Track Templates to be honest.
Drum Maps could use a better UI and Track Templates could use an overhaul in the Pre/Post usage.
Example: It would be nice to be able to use a Track Template on an already established track
Vs. just being able to use a Track Template on a new track.

I can verify now and I will create a bakers bug report.
instrument track templates carry over AND REPLACE all drum maps from whatever project they were created in.  NOT GOOD.  
 
Yea I agree with you, drum maps especially.  Re-do the entire thing.  

I ran into this also and spent a lot of time trying to figure out why this was happening. Essentially the track templates are also saving drum map info. The trick is to insert a track template and delete all the drum maps and save the track template again. Now when you insert that track template, it doesn't alter the drum maps at all
 
My template has about 4 drum maps in them, using this method, the same drum maps in my template are still there and no port settings are lost. When re-saving a track template - always delete all the drum maps before save.
 
What was happening to me, when I’d insert from a track template, is not only was the drum map assigned to the wrong drum map, but there was a huge list of 99 drum maps, mostly all blank. In drum map manager you can delete these blank drum maps one at a time to make the list more manageable.
 
Also when I would select the correct drum map all the post assignments were messed up and I’d need to redo them. You can select the top one and go to the end of the list and hold shift and it will select all the key assignments, then when you choose your port, hold control-shift and it will choose the port assignments for every single one. This saves time.
But using my method you don’t have to go through all of this the drum maps won’t be altered.
 
I also found another workaround when this happens. Don’t’ choose your drum maps from the list even if you find it, but instead choose “new drum map” and then choose your drum map. this time the port assignments won’t be messed up.
 
 

That's all great info fellahs, thanks.  I always wondered why the sudden profusion of drum maps from nowhere.  I pretty much only use the one custom map I created so I should be able to do a little housekeeping on my projects now.

This has been a problem for a long time. The drum map system needs an overhaul.