"Alias" for Shared actions instead of an "id"

If shared actions are used, every new shared action in a database gets a new id. The id is a number. Working with the shared actions in one database works fine. Image a second database which also uses shared actions. In the second database there are already 3 shared actions present. If i now copy all shared actions from the first database to the second via designer, all or some of the copied shared actions will get new ids. If i now copy a view (which owns shared actions) from the first database to the second and open it, all shared actions will be messed up - which is logical... If we would have the possibility to assign each shared action a "alias" or "programmatical name" (insted of the system-given number), the problem described above would be fixed.