Omatic Cloud
245 results found
-
Log when a formula is reprocessed in Activity History
Currently the activity history does not show when a formula is reprocessed. This info would be helpful especially when working through the exceptions buckets. it would all use to better track errors that are recurring.
4 votes -
Classy Transaction Filters
I would like to include the following filters in the Classy Transaction Endpoint:
- Company Gifts based on if Company is provided or Individual Gifts Based on if Company is not provided.
- Only Recurring Donations or Only Individual Gifts
- Status: Include Succesful or Pending(ACH)
- Date filters Refund Date, Date Modified, Date Added, or Payout Date.
4 votes -
Request to add ability to use sub forms in VolunteerHub
Current functionality is to use the "All Users" form when pulling fields for VolunteerHub. It would be nice to use subforms as sometimes we want to simplify the list of fields volunteers are selecting.
4 votes -
Ability to ignore a record
When pulling data into SF there are times when a user wants to ignore or skip a record and not pull it into SF. Use case for this is a list of contacts or oppts with a field value that indicates they are not valid or at the level required for adding to the SOR.
3 votes -
Ability to review all data being imported
Any field that might be touched through the Omatic import should be displayed on one screen to be approved by the importer. The current data difference grid only shows a couple fields. We should have the ability to see the two side by side (current BBCRM data & new Form Data) and decide which to keep untouched, and which to update with new data, and also have the ability to make edits to the new data before import.
3 votes -
Allow for email campaigns to be excluded from data push to database of record
Would love to be able to exclude email campaigns that are pushing back from Constant Contact to Altru.
3 votes -
It would be an improvement if we could have Payout date as an option for mapping.
When bringing gifts over from classy the GL post date is not matching our deposit dates and this is causing issues with finance. If we had the ability to map the payout date to the GL post date that would make the financial process cleaner and much smoother without manual global changes.
3 votes -
Need more flexibility for filtering records in RE NXT List, in order to export
RE Query allows for greater flexibility in the output of fields from RE than the List option does. For a client with an email connector, who may be using cons codes, solicit codes, attributes, etc. to segment their audiences this is not possible with the List endpoint in RE NXT.
3 votesBlackbaud has recently added functionality that enables us to potentially pull data from Query as a Source. We are reviewing this option an looking into adding the functionality to Omatic Cloud.
-
Enforce Unique Formula Names
Formula names should be unique in Omatic Cloud. Multiple formulas with the same name can cause confusion during processing or reporting an issue with support.
3 votes -
Add/Update Gift Data as part of PostOmatic Processing
We often use PostOmatic (POM) to apply complex logic, concatenating data from multiple sources in RE to determine the final Debit/Credit accounts to which transactions should be written in our financial systems.
There is no simple way to look at a gift in RE and say, "This is the Debit/Credit that was used."
While the output data from POM can be re-imported to RE, currently, this is a secondary manual process. Could POM be updated to include an option for automatically adding the final Debit/Credit outputs to the source gift record?
3 votesThanks for the idea JPP. Can you be more specific about where you want the debit and credit used to be added back to the gift? There are certainly limitations as to where data could be written back to the gift due to field size constraints as well as considering all of the output that is typically in Post to General Ledger files.
Here are a few more questions for consideration:
What is the goal of having this data in RE/how would that data be used?
Should there be any considerations if an adjustment is being posted due to adjustments creating reversing entries to reverse out what was previously posted and then having new journal entries created for the updated information?
What other scenarios might we need to account for if we added a write-back feature?
Thank you
Steve Brewer
Product Manager
-
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 -
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.
3 votes -
Add ability to move data from BBCRM to Omatic Cloud using Export Definitions
We are trying to move data between BBCRM and iModules Encompass using Omatic Cloud and would find it very beneficial to use export definitions to send data back and forth rather than queries. The reason is that with export definitions we can be specific about what data to send back and forth. For example, we use constituency to move data in Encompass from our main community to our sub-communities. Therefore we have a need to pull over constituency code. However, we only want to pull certain ones. In query, when we put constituency code in our output, it brings over…
3 votes -
Ability to apply gift to full constituent spouse when matched on non-constituent spouse.
In Import Omatic we have this option but not in Omatic Cloud.
3 votes -
Title part of data differences
Can you make Title part of the data differences options in routing/matching?
3 votes -
Have ability to map to custom attributes for a Participant
We record event specific information against a participant of an event in RE. Could the endpoints for attributes for a Participant be made available to enable us to add/update these.
3 votes -
Add a filter option for Classy campaigns.
Our organization has ALOT of published and unpublished campaigns in Classy. It would be wonderful to have the ability to search and select Classy campaigns by a filter vs. having to select from a very long list of "Campaign Names". It would also be great to have the option to search based on "Internal Campaign Name" since that is the field that is non-donor facing that we customize for our internal data mapping. For example, be able to filter Classy campaigns by their
campaign name or internal campaign name containing "renew", which for us, would allow us to create a…3 votes -
Have an export profile in the LO Connector that allows for TeamRaiser registrations to be exported from RE to LO.
Omatic has gotten TeamRaiser donations to flow really well from Re to LO, but the missing piece is still the offline registrations that need to go from RE to LO. Currently we have to use Blackbaud's arcaic upload system and then still rely on RELO to pull them down into RE because the import for registrations either does not have the ability to recognize offline registrations or cannot recognize the time stamp the LO uses for offline uploads of registrations.
3 votes -
Populate More Example Rows from Luminate Surveys
It would be good to have more example rows populating for Luminate Surveys when working on the Data Mapping page in a formula. When building transformations it's nice to cycle through a few records to make sure the data is transforming as expected.
3 votes -
Provide the ability to overwrite an existing value with a null value in MailChimp
Currently, date fields with null values are not sent through the MC connector. I'm not sure if this also applies to other types of fields.
This means that if a date field is populated in MC, then updated to a null value in RE, the date will not be overwritten in MC with the new value.
Because we use these date fields (expiration date, date joined, etc) as segmentation criteria, this affects our marketing campaigns to targeted audiences and can cause significant problems.
3 votes
- Don't see your idea?