Every time there's a Luminate constituent update and the constituent record contains accented characters, the fields containing those characters are sent to the RELO plugin as an update, even if those fields haven't been updated. We are then forced to either process or reject those changes. I've attached screenshots to demonstrate the issue I'm referring to.

This behaviour greatly increases the number of constituent updates sent to the RELO plugin, as well as our workload. It also clogs up the RELO pipeline that is limited to 500 constituent updates at a time, the remainder being queued until the earlier "updates" are processed. We're an organization with a very large database, so our backlog often goes over the 500 constituent update limit.

RELOAccents1.jpg

RELOAccents2.jpg

RELOAccents3.jpg

Attachments Open full size