When working with reference fields, it is really important to
String fields typically aren't any thing to get too worked up over, but I've discovered a couple of cool tips on dealing with string fields in Service-now.com that might benefit somebody else at some point.
One common problem I encounter with Service-now deployments has to do with the sharing of a field between many tables extended off of the same parent table. Because the Task table and the Configuration Item table make heavy use of extended tables this is where I see the problem most often. What is the best way to make changes to a shared field for the table that I'm working on, but not impact other tables that may be using the same field?
