Imports to update constituents are overwriting user-defined constituency

Is anyone using imports to update constituents, and are you experiencing any issues with the process overwriting user-defined constituency codes that already existed on the record? Assuming BB has yet to effectively address this situation for your organization, how have you handled it in terms of a work-around in the meantime?
  • Guest
  • Jun 29 2015
Organization Name (Please enter full organization name)
Reported Version
  • Attach files