Since it’s possible to have many Generic Remote Maps, double check that you didn’t create more than one by accident, and are just looking at an empty one.
It also might be that whatever links you made in the map were for a plugin or track that’s not loaded yet?
For instance…say you built a link to move the Resonance Filter of a Retrologue instance, then later you open a project that doesn’t have Retrologue loaded, it doesn’t point anywhere until you load an instance of Retrologue…so it’s temporarily ‘unassigned’ (or it might show some odd series of numbers).
Same for tracks…say you bound things to automate the CuBase mixing console for 16 tracks…but you’ve only loaded 8 tracks…the second 8 will be unassigned until you make more tracks.
Note, if you use more than one instance of a plugin…those multiple plugin increments progress as well. I.E. You might have a CC bound to control resonance in the first instance of Retrologe, yet in the same map have a control bound to control cutoff in a second or third instance of Retrologue. So, if you’ve only got one instance loaded…stuff pointing to other instances will be unassigned until you load up more instances of Retrologue. If you have NO instances loaded, then it’ll all be unassigned until you load up the plugin.
Finally, it’s not a bad idea to export dated copies of your maps from time to time…particularly after making some pretty big changes. It’s not a bad idea to export a copy in the Project folder as well…because who knows what you might change when working with a different project? Or…what happens if you open the project a year from now, and want to be able to pick up where you left off…
As for needing to ‘export’ a map to solidify and remember the changes, I don’t find that to be the case for me. Clicking apply and OK is all I’ve needed to do…and these Device settings become part of my main DAW configuration…it does NOT save/load/change with individual projects…such settings stick with a particular CuBase configuration.