Import Customization files for Environment Specific Constants

I would also like to know if there is a way to do this (my guess is that there is not a way currently). My use case is that for things such as reference IDs, we duplicate the current value within the Description field for added visibility.

Same use case for me. But having only the value changed using an IC file leaves the Description field unchanged, which is not what you would want. We've had to stop duplicating the text in both fields just for that reason.

Same here - for my recent batch, I just set the description as "Value = (ES)", where formerly it would have been more like "Value = 3" etc. "(ES)" designating "environment specific", and at least in this way I have an easy way to find any such constants as a group later on.

Side note: it would probably be a good idea to indicate such items within the project-specific naming convention for constants, except in my project there are many that are long since carved in stone and therefore it wouldn't really work out.

Same here - for my recent batch, I just set the description as "Value = (ES)", where formerly it would have been more like "Value = 3" etc. "(ES)" designating "environment specific", and at least in this way I have an easy way to find any such constants as a group later on.

Side note: it would probably be a good idea to indicate such items within the project-specific naming convention for constants, except in my project there are many that are long since carved in stone and therefore it wouldn't really work out.