The current behavior for mapping an inbound constituent to a group in Emma creates one row per Emma group on the mapping page and you set a defined value of "true" for the group you want to map to. This is problematic when you have a large number of groups (thousands) as the page becomes very long.
A better solution would be to have a row in the mapping table for "Group" with the ability to either define a group name or map to an incoming CRM field. The latter would also enable you to reduce the number of CRM queries needed by using a query output field for the group name, enabling a single CRM query to manage multiple Emma groups.
Matt, thank you for submitting this idea for Omatic Cloud! I'm writing to let you know we've implemented this idea as of this week.
When mapping fields, you will now see three new sections:
We appreciate your input and please reach out if you have questions.