Omatic Cloud
269 results found
-
Allow matching on fuzzy address formats
Incoming address may be the same as existing, but with different format. We do not want to overwrite the existing address with one that has an incorrect address format and be constantly doing data clean up to correct. Need an option to only update address if it is different from existing address by a percentage. If it is 90% the same, then don't update address. OR it should give value update option, as it does if incoming title is different
66 votes -
Allow all custom questions in a single formula for Classy connector
If "include custom questions" setting is checked, all questions must match identically across campaigns to be in the same formula, resulting in many formulas needing to be processed separately. Allow ability to include all custom questions, regardless of matching to be mapped in a single formula.
8 votes -
Ability to Schedule Formula to do Refund Pulls in Classy to Update Opportunities in Salesforce.
We need the ability to pull Refunds from the Transactions Connector on a Scheduled basis. Currently, this would have to be a manual run because when a formula is scheduled it only pulls based on the created date not the Refunded date.
2 votes -
Add ability to only add certain mapped fields to new records
We would like to be able to decide specific criteria only applicable for new records added, not existing. Similar to applying default settings to new records in Importomatic.
Examples:
-Add addressee/salutation styles to new records
-Only add constituent code to new record
-Only add preferred name to new record63 votes -
Add Table Entry If It Doesn't Exist
It would be very helpful if Omatic Cloud could add a table entry during the import if it doesn't already exist. This is IOM functionality that is needed in Omatic Cloud.
10 votes -
Ability to Send One by One from Ready
it would be helpful to have the ability to send records individually from Ready.
Sometimes a record might need more review while others can be sent to the destination.13 votesThanks Amanda. Can you share a scenario or two why someone would want to be reviewing records in Ready? We would think that if it ended up in Ready that the record should be "good" and the other buckets are where records need to be reviewed. Is there another classification of record that would cause them to need to be reviewed that we don't accommodate that calls out the need to have records to go to a needs attention bucket? Meaning, is there some other criteria that calls out the need to review? If so, what might that be?
-
Classy Endpoint API Field Additions
Classy Recurring Giving Plans:
- Company Name (Available for Classy Transactions): This will be used to determine if a Recurring Gift was given by a Company or Individual.
- Primary Source and Secondary Source (Available for Classy Transactions) Needed to populate SF Campaign and GAU Allocation
Classy Transactions:
- ACH Last 4 (Available on Recurring Giving Plans)
7 votes -
Increased Email Import Capabilities
We would like the ability for more detailed mapping of emails/phone numbers like it does for address updates. For example, the ability to add an email as a specific type ONLY if it does not already exist on their record. If it does exist, the option to ignore or update the email type. It would also be nice to say if a specific email type exists, add as "Email 1, 2, 3, etc." There are many times during events we get new email addresses but do not want to override an existing email address and do not want 5 of…
11 votes -
additional -- useful -- logic operators in P2GL
Can we add some additional -- useful -- logic operators to P2GL?
*Blank
*Not Blank
*Does Not ContainBlank and Not Blank are especially useful. Today, without them, we're forced to use 'Equal' or 'Does Not Equal' and then compare that to an unpopulated field. Sometimes, however, if there are spaces in a field, it might look to be blank but isn't really.
All and all, it's just safer and more efficient to have 'Blank' and 'Not Blank' operators.
'Does Not Contain' is useful for working against alphanumeric data, and would prevent needing to use more complicated 'If/Then' or 'True/False'…
5 votes -
Add a Classy Event Recurring Plan profile type
Classy users have the option to configure an event with Recurring Gift options for donors. A Classy Event Recurring Plan profile type seems to be needed for recurring gifts created on events since those new recurring setups don't come through with the standard Classy recurring plan profile. The recurring installments are able to come down through the donations profile, but none of the existing Classy connector profile types seem to be able to handle the Recurring Setup gift currently if it made on an event record in Classy.
0 votes -
Add Classy payment type filter during import - paypal vs. stripe
The ability to import paypal gifts only and then stripe gifts only would significantly help during import and reconciliation
4 votes -
Post to GL outputs for FE NXT
The formula template for posting to FE NXT does not furnish any options for the output files that the formula generates (other than the actual batch in FE NXT). Since a Post-to-GL user may not have direct access to the destination FE NXT system, those output files are very valuable for analysis and troubleshooting.
Currently, they come out as .txt files, which makes analysis challenging even when using an advanced editor. Can the output file that represents the created FE batch be output in .csv format? Or, could the user building the formula be given an option for the format…
2 votes -
Give Lively Connector for Omatic Cloud
It would be great to have a GiveLively Connector created for integration with Omatic Cloud.
1 vote -
Separate formula Type for HubSpot Email Subscriptions
Currently, the HubSpot formula "Contacts" handles all subscription information. Could this information to be handled separately in a stand alone formula since the "Contacts" formula handles all changes, not just email subscription changes.
The current process is noisy and creates a high volume of records that are unrelated to email subscription changes. This is also problematic for the HubSpot connector given API hits.
4 votesWe are planning to add this feature in Q4 2023!
-
HubSpot Email Information Subscription Dates
It would be very helpful to have Subscription status > history > dates available in the HubSpot Contacts formula. This would allow us to bring in more accurate data when managing email subscriptions
9 votes -
Add NIN to Omatic cloud
For importing Standing Order payments from the bank the only way we can link to Constituents is by a unique ref. We currently store this in the NIN field. Could we get this field added to the omatic cloud when it is added to the SKY API (raised with Blackbaud as well). Thanks
1 vote -
RENXT Record Type Displayed in Buckets
It would be helpful to see what kind of record type (Constituent/Non-constituent/Relationship) a record was while reviewing in the 1-Many matches bucket. This would speed up the process of determining which record is the correct match. This could be done through an extra column (that might be hidden if not wanted) or font formatting.
8 votes -
Organization Information in "Verify your account" email
When adding a user to an account, it would be helpful to see the Org Name and potentially the tenant name associated with the email verification. The current email does not include any identifying information and makes confirming access challenging. It would be much easier for users to be able to directly click on the OC URL from the "Verify your email/account" email that is sent out when a user is given access to an OC instance.
1 vote -
Additional Scheduling Options
Right now, we have 3 scheduling options generally (weekly, daily, continuous). A client has requested that we have additional scheduling options, example: twice daily, twice weekly, every two weeks.
2 votes -
Delete Field Value Using Dedicated Syntax
We often have the need to delete/clear a field when importing. It would be great to have a dedicated syntax that we can map to indicate that the mapped field should be replaced with null.
E.g. if we map {DELETE} it would remove the value in the field in Salesforce that we are updating, leaving it blank.
This would allow blank fields to be ignored, whilst giving users a way to very intentionally delete a fields.
Two examples:
1) We have a file of donor data where invalid/incorrect email addresses and phone numbers have been flagged. We can therefore import…
3 votes
- Don't see your idea?