Hi Dono
That's a good point actually and the only way you can get rid of those is to get rid of them in BFD3's key map page which is very quick easy, Sonar's piano role will update to match BFD3's key mapping.
I strongly recommend getting to grips with BFD3's key map page.
I tend to like my drums laid out to the old general midi standard with kick at the bottom and then snare, hats, toms and cymbals above. It is a pain though and whether you use drum maps or just let sonar's piano role update it still requires mapping to get it how you want it.
Even though sonar's piano roll updates according to the midi map it doesn't mean you won't have to make changes
if you add or remove kit pieces.
Another thing you should be aware of is that when you add a new kit piece in BFD3 it won't automatically map it for you so that's another reason you'll need to get to grips with BFD3's key map page.
I think it would be great if BFD3 did that, and I think I may have suggested this as a feature request but was told it was extremely difficult to do or something.
The thing is there is only one keymap for BFD3 which is supposed to cover all the stock kits and their potential articulations. Key maps are created on a per kit basis, sometimes presets will have their own keymaps but generally not. That's why you have to do it your self at some point.
It's one of the most complex areas of vst drums and obviously the more articulations and kits you have the more complex it becomes, there are a lot of keyboard drummers out there who need to map kit pieces to the way they play so it needs to be flexible.
Incidentally, the template I posted was for the purpose of routing and I hadn't realised that the keymap had been ignored.
Steve