Omatic Cloud
379 results found
-
Add fields to Altru connector (particularly Volunteer)
There is no import template available in Altru to import into a Volunteer record. This would be a gamechanger for our organization as we will have to manually enter and match volunteer data. We have the pathways set up in Omatic Cloud and we will not have enough data to warrant using ImportOmatic.
There are other fields that we have come across that would be helpful as well. I have not noticed any updates made to the Altru connector other than the move from OIC to Omatic Cloud. I am happy to share other fields that would be helpful if…
2 votesHi Jacky,
Thanks for the suggestion. Can you be more specific about which volunteer fields you would want to have included? In addition, you mentioned other data you would like to see available, can you share that information as well?
Thank you
Steve Brewer
-
Add ability to specify the Constituent Code sequency (Primary Consituent Code) when adding or editing
Blackback RENXT considers the first or top Constituent Code on a constituent record to be the primary code. This primary constituent code is automatically used in reporting and is the default on new gift records.
We are requesting the ability to specify if a constituent code should be in the top spot when importing (creating or editing) a constituent record.
The skyapi for constituents allows a sequence to be specified when creating or editing a constituent record however Omatic Cloud has not exposed access to specify a sequence value.
The current behaviour appears to add a new constituent code to…
3 votes -
Update FE NXT Batch Desicription on import error
Post to GL creates the JE batch and then progresses through importing the transactions. If a transaction results in an error, Post to GL stops the import process—however, it may have completed a partial import, and that partial import may be "in balance."
It would be helpful if, when Post to GL fails due to a transaction error, the JE batch description could be updated to append an error message so Finance is aware that the batch was not created successfully.
3 votes -
Exclude Administrators
Currently, LO connector imports administrators to Raiser's Edge. However, you can't update Luminate Administrators with LO connector, which is good.
The profile should ONLY work with constituents, NOT user accounts. Filtering out administrators should be an option without a group filter from the profile settings.
3 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 -
Integrations/Formulas | Mapping | Total Sum of Two Cells/Columns from an Import File
Built-in feature that allows combining two column headings to create a total sum during the mapping process.
Example: scenarios of summing platform fees and transaction fees.
1 vote -
Option to get user input when incoming data doesn't match existing data for specified fields
We often have enough information to be confident that the incoming data matches a record in Salesforce. However, whether the better quality data for important fields is in Salesforce or the incoming data is unknown. So we can't confidently overwrite data without a manual validation.
For example, P Ennals might match to Peter Ennals. I am happy this is a valid match and therefore want to set it as a ready record. However, I don't want P to overwrite Peter.
The functionality could be such that I specify per formula which fields require manual validation. E.g. for records where name…
6 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.
9 votes -
Include non-mapped source fields in summary fields to help with decision making.
We don't want to update fields in LO but want to see the source fields (which are not used in the mapping) in summary fields to assist in making decisions.
1 vote -
1 vote
-
We would like the ability to sort data in the Needs attention bucket. This is the way they used to be ordered.
Previous order was:
1. 1:1 Matches
2. Multiple Matches
3. New Records
4. Destination Exceptions
5. Formula Exceptions1 vote -
1 vote
-
Allow pulling an unsubscribe list from constant contact
Currently cannot pull this list. We tried to set this up pulling from the edit date, but that date is not updated when a contact unsubscribes. How else can we pull an unsubscribe list from constant contact?
9 votes -
Deceased indicator
Display a deceased indicator in the data differences columns of the triage buckets, similar to displaying Mailchimp contact status. This will help with decisions without me needing to step into the record just to find out they're deceased.
1 vote -
Provide a merge option for records merged in RENXT and corresponding records updating in Engaging Networks
Provide a merge option for records merged in RENXT and corresponding records updating in Engaging Networks
3 votes -
Add connector for AlumnIQ
Would like a connector for AlumIQ for BBCRM OC
https://www.alumniq.com/1 vote -
Post-to-GL: Create New Journal or Append to Existing Journal
The process of uploading a file to Post-toGL creates blank or incomplete JE in FE NXT if there are data entry errors in the document that cause the transaction import to fail.
Could the Post-toGL connection be updated to provide the options / ask the question if the user wants to:
- Create a New Journal Entry
- Append to an Existing Journal Entry
This update would reduce the number of empty or incorrect JE that have to be deleted from FE NXT.
3 votes -
Allow 'Replace' transformation option to include operators for 'greater than', 'less than' and 'between'
It would be great to be able to specify a range in order to have more conditional behavior within the 'Replace' transformation. For example, if I want to assign the gift letter code or acknowledgement status based on the gift amount.
29 votes -
Update Matching with Encompass Connector
When going from BBCRM to Encompass Matching only allows for custom options and pre-populates with ALL currently mapped fields.
While this is trying to be helpful, if there are 30 mapped fields it will default to matching all 30. At that point it would be more helpful to not pre-configure matching and let the user configure the matching.
1 vote -
Abilitly to do relationship matching in RE NXT based on Constituent Import ID
Currently, when importing relationships to existing constituents in RE NXT, the only option for matching to existing constituents is to map to either 'Constituent Lookup ID' or System Record ID. We really need to be able to map to Constituent Import ID. Especially when using a hybrid approach using both IOM-Classic and IOM+/OC, IOM-Classic furnishes the Import ID as an output field, but not the 'lookup ID' nor the System Record ID. This would be a very useful and valuable feature, and would allow clients to leverage the benefits of both versions of IOM.
11 votes
- Don't see your idea?