Import GeoFence changes string value which causes Field Enricher to not work

Discussion created by jgrayson-esristaff Employee on Jul 29, 2013
Latest reply on Aug 15, 2013 by TStiles-esristaff
Import GeoFence changes string values by adding underscores for spaces (and other characters) which then causes the GeoTagger to add new field with a string value that the Field Enricher (from the same Feature Service that was used to import the geofences) to not work because the field values no longer match.  Any suggestions on how to workaround this issue?