Omatic Cloud
131 results found
-
Ability to consider only a Segment or Tag in formulas where MC is the source
A couple of our Mailchimp lists are made up of both subscribers that are in Altru and subscribers that aren't. In addition, since OIC is unable to update organization records in Altru, we find that our Mailchimp-to-Altru formulas often contain records that can't possibly have a match in Altru. Therefore, it would be nice to be able to configure those formulas to consider only those Mailchimp subscribers with a specific Tag or that are in a specific Segment of the source Mailchimp list. We could then make sure that the Segment or Tag contains only those subscribers that could possibly…
0 votesThis is an interesting idea! We researched the possibilities in Mailchimp's API, and the only additional filtering we could provide (currently) is based on Interests. They do not allow filtering on segments or merge fields at this time. Would the Interest filtering be a suitable option for you? I can see how it may be beneficial to other organizations and how they use Interests, but I'm not sure if it works for the use case you described above. -
Highlight data differences in 1:N data grids
It would be helpful if data differences in fields used to find matching records were highlighted in the source record and possible matching records in 1:N data grids. This would help the user locate the most likely match for the source record more quickly. See the attached screenshot for an example of fields that would be highlighted in a formula where first name, last name, and Lookup ID are used to find possible matching records. Thank you for considering this request.
0 votes -
Enable Display of Mailchimp Status in summary field
The "Status" field in Mailchimp (subscribed, unsubscribed, cleaned, etc.) appears to be an option to display in summary fields but when added to a summary field it doesn't display anything. If this item could be displayed in summary fields that would be helpful because then you could see at a glance which records can and cannot be updated in Mailchimp (since it won't let Omatic Cloud update Cleaned records or re-subscribe unsubscribed records).
0 votesOmatic Cloud has been updated and you should be able to see the "status" field from MailChimp now in the summary field. Thanks for letting us know! -
Ability to map attribute data only if no matching Altru attribute found
We would like the ability to map fields such as Attribute Date and Attribute Comment only if a new Attribute is being added to an Altru record via an OIC formula. As it stands now, we are leaving the Attribute Date and Comment fields unmapped so they won't be overwritten when the formula finds a matching Attribute based on Attribute Category.
Say we have an attribute with a Category of "E-News Email List," a Value of "Yes," and a Start Date of 1/1/2019, which signifies to us that this person subscribed on or about 1/1/2019. The subscriber's record changes somehow…
0 votesWe are planning to add the ability to ignore incoming attribute data if the incoming data matches to existing fields that you would designate. We are not at this time going to enable independent field decisions for value/comment/date. Would you be able to track this data in two different attributes, so you could designate the updates independently by attribute? -
Alias ID Matching
Would like the ability to match on the Alias Value, as we are able to match to other External ID fields in other connectors.
0 votes -
Allow Groups filter to exclude a group instead of include
Thank you for implementing my idea about limiting the records processed in Mailchimp-sourced formula to just records in a certain Mailchimp interest group. More helpful to us than this would be the ability to exclude records in an interest group. This is because we do want the formula to include new records that were added to Mailchimp via a signup form, and those records would not be in the group in question yet (we are using this feature with a hidden group, so subscribers can't select it when signing up). Thank you for considering this feature enhancement. Bill
0 votes -
Discard/Ignore Records Below Certain Threshold
It would be really nice if we could ignore records below a certain threshold in both the 1:1 and 1:N matching and in all instances. The current feature in 1:N seems like a great idea, but it doesn't work. It will only ignore records below a certain threshold if there are records that are higher than that. For example, my threshold is set to 72% on one of my formulas. It doesn't work on 1:1, only 1:N. And it only works on 1:N when there is an 87% match that pulls in at the exact same time. Otherwise, all of…
0 votesWe have released a new feature to Omatic Cloud called Advanced Matching Settings. By prioritizing the search scenarios, Advanced Matching Settings can help reduce the number of records that are returned when searching the destination system. This feature will:
-Save time when sorting and reviewing records during routing.
-Reduce the number of API calls to your endpoint.
-Exclude unlikely matches if better matches are found.
You can learn more about setting up these settings in our User Guide: https://omatic-cloud.helpdocsonline.com/matching$advanced-matching-settings
-
Summary Fields grid update
Can a 'pop- up' message be generated when you press "delete" button in the actions tab of the data queue grid as sometimes, it can be pressed unintentionally and the pop up would help back out of those situations.
0 votes -
Ability to match relationships to existing records
My formula adds relationships as non-constituent records, rather than matching to an existing constituent record. We import a lot of relationships as an organization and it's important that they are linked to the existing constituent record in RE NXT! I've tried mapping the System Record ID, the constituent ID, the exact name, nothing gets through. We really need it for new constituent records from import, as well as updates to existing constituents.
0 votesThis feature has been released. Omatic Cloud now has the ability to search for both full constituents and non constituents when matching a relationship. You can find more information here: https://omaticsoftware.freshdesk.com/support/solutions/articles/28000023286-how-to-configure-and-process-related-records-in-raiser-s-edge-nxt -
Manually search for record to match to
I would like the ability to search RE NXT for a record when the right match isn't found - for example, someone uses a business name that doesn't exist in NXT, but I want to match to an existing record.
0 votes -
Matching and Scoring Logic
When triaging records with 1:N (many) matches, it would be nice if there would be a way to implement different tools to facilitate auto matching... * use fields for matching that are NOT mapped -- match on a custom field in the destination system that is NOT even in the source system... * use fields for triage (scoring) that are NOT mapped for data synch... - might want to apply a score on an updated date field but this field is not mapped. * scoring rules - there are other salesforce deduping tools that provide the ability to assign points…
0 votesWe have released a new feature to Omatic Cloud called Advanced Matching Settings. By prioritizing the search scenarios, Advanced Matching Settings can help reduce the number of records that are returned when searching the destination system. This feature will:
-Save time when sorting and reviewing records during routing.
-Reduce the number of API calls to your endpoint.
-Exclude unlikely matches if better matches are found.
You can learn more about setting up these settings in our User Guide: https://omatic-cloud.helpdocsonline.com/matching$advanced-matching-settings
In addition, you can match to records based on fields even if they are not mapped (including defined fields), as long as they are available in the specific endpoint for matching. If there are specific fields you are looking for that aren't available, feel free to create a new idea for those fields. When reviewing the grids, the summary review fields enable you to select which additional fields you would like…
-
Add option to match inactive Altru records
Due to how our Altru database was populated from Raiser's Edge, we have a lot of Inactive constituent records. When someone signs up for a program or membership and they have an existing inactive record, we set it back to active, but sometimes our Omatic formulas run before we get to that step. Then the formula doesn't find a match when indeed one actually exists. Therefore, the option to set formulas to match on inactive Altru records would be a welcome addition.
0 votesThanks Bill! We agree this would be a beneficial update and we plan to update the connector. -
Sync the "Commerce Identifier" field from Encompass
Need the commerce identifier field synced from Encompass via Omatic cloud connector.
0 votesThis has been implemented and released in the latest version of the Encompass Connector; you should see the fields available when remapping fields for existing formulas or creating new ones. -
Ability to "Add New" from the 1:1 and 1:Many Queues
The "Add New" button in the 1:1 and 1:Many queues is grayed out but we feel it's too restrictive. We would like the ability to add a new constituent from those queues.
0 votesAre you are mapping or have added a defined value of "true" in the "Edit if Matched" fields in your formulas? To prevent duplicates from being added in BBCRM, if the "Edit if Matched" field is mapped or defined with a value of "true" (or a similar, accepted value), the "Add New" action button is disabled. If the "Edit if Matched" fields are not mapped or are defined as "false," the "Add New" button will be enabled. If you'd like to check out more information on the "Edit if Matched" field, you can check out our solution entry here. I believe we mentioned the update to the 'Add new' button in a communication to your team in November or December 2021, but wanted to track in here that we've "unrestricted" the 'Add new' button on the 1:1 and 1:Many Needs Attention grids, regardless if a match was found. -
Add a Constituency to BBCRM Mapping Formulas
I would like to suggest the ability to bring in constituencies for new records in our BBCRM constituent revenue type.
0 votes -
RE NXT Allow Dates for Assigned Appeals to be in the future
We have run into an issue with OC where the Blackbaud Sky API will not allow us to import Assigned Appeals with Dates in the future. According to the support ticket "Blackbaud does not allow an appeal to be added to a constituent record through the Sky API with a date later than 2 days from the date it is being run." Assigned Appeal lists are often generated weeks in advance, and they should be able to be added to a constituent record whenever.
0 votesHi!
We have have worked with Blackbaud to prioritize resolution of this issue. They have confirmed that it is resolved. You should now be able to import Assigned Appeal Dates in the future.
Best,
Kristen
-
Adding Revenue Solicitor as mappable field.
Every donation form has a set of cross references, one data point is solicitor which is an internal CHLA Fundraiser (staff member) who is credited for the dollars raised, this info is invaluable for fundraising goals. It is not a custom field- all other labels are there except for this one.
0 votesI wanted to let you know that the Solicitor name field is being added to the Revenue / Payment / Donation object in the BBCRM Constituent Revenue endpoint. The field for Solicitor ID already existed, mainly for lookup, so now a solicitor name can be defined or mapped. This should be in the application in April 2022. -
A way for data grids to display unmapped fields
We would like for the grids to display unmapped fields such as suffix1 and suffix2 in the BBCRM production cell on the grid. This will help with identifying the right record. Many times we have Jr. and Sr. living in the same household or using the same email address.
0 votesSuffix data is available for BBCRM: https://support.omaticsoftware.com/support/solutions/articles/28000025000-what-fields-are-available-to-display-as-summary-fields-in-1-1-and-1-many-grids- If you aren't seeing it for some reason, please let us know! -
TeamRaiser Recurring Gifts
In Luminate Online, you have the option to allow sustainer gifts on TeamRaiser pages. The TeamRaiser formula (Luminate TeamRaiser Donations to BBCRM Constituent Revenue) cannot currently segment sustaining gift commitments for processing into CRM. Therefore, translations need to be made in order to apply recurring gift commitments only and NOT donations when fulfilling such business need. This becomes confusing because users must navigate through several gifts in queue, many of which are not sustainers. This idea is to build a formula type or functionality to accommodate the same functionality as the Luminate Sustainers to BBCRM Constituent/Revenue formula, but for TeamRaisers.
0 votesWe recently added a new formula type for Luminate Online TeamRaiser Sustainer gifts! -
Postal Code clean up options for Canadian Postal Codes
Currently omatic cloud doesn't allow Canadian postal code clean ups, adding space between the code (ie, from 1A12V2 to 1A1 2V2)
0 votesHi Amy,
We have added a CAN zip clean-up transform on our Omatic Cloud platform. If a string of 6 numbers come in, a CAN zip format option can be selected. Below is how the format is configured:
3 alphanumeric characters_3 alphanumberic characters, like ANA NAN
A = alpha
N = numeric
Thank you for your suggestion!
Chanel
- Don't see your idea?