Please submit all product enhancement ideas below. We welcome your feedback; your ideas will be reviewed by the Product Manager that oversees the development of that part of the product on an ongoing basis and updated with its current status monthly based on our product planning process. Ideas you submit could help us shape features currently in development or grow our repository of requirements for our next big enhancement. Thank you for taking the time to share your thoughts and expertise with us.
If you believe you are experiencing a defect please contact Support.
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.