In the type palette document in the sequence editor, select the sequence file with your custom data type in it, Ctrl+c to copy it, then go to the MyTypes.ini file, go to the custom data type section and do Ctrl+v to paste. You can edit it's version number using the properties dialog box on the custom data type (look in the version tab).
Once you have saved mytypes.ini, you can redistribute it to others at your company or with a deployment as needed. Or put it in source code control.
What is likely happening is that, since the station option is set to a model different from the one with your modified type in it, if both your modified type's model gets loaded and the station model gets loaded, there is a conflict. At edit time it is probably resolved automatically by choosing the highest version, at runtime that is not possible if the newer version is loaded second since you can't modify a global type while an execution is running.
Another reason why you might now get a conflict, even at edit time is if your type is marked as modified (always causes a conflict if this is the case), or if you've changed the station option for Allow Automatic Type Conflict resolution to one of the two strictests settings (neither is currently the default).
Hope this helps,
-Doug
