Classic Products
350 results found
-
Add ability to create constituent batches from constituent import that could be processed at different times or by different staff.
Ideally, we could set a maximum number of records per batch and batching would automatically occur if this number was exceeded. This came up when we just did our NCOA update which created thousands of address changes that had to be imported to LO which triggered them combing back through the Connector.
1 vote -
Display spouse first and last name next to the constituent name in the first row of the Duplicate Search results screen
Currently, even when the spouse first and last name are specified in the incoming data, they are not displayed next to the constituent name in the first row of the Duplicate Search results screen. They will only be displayed when the spouse relationship itself is being matched. Apart from that, the only way to view the spouse information during importing is to double-click the first row to display all of the incoming fields.
Although the profile configuration allows for columns to be displayed for the spouse's first and last name, this does absolutely no good if the names are not…
1 vote -
Change the mapping of phone/email attribute
Raiser's Edge has moved phones/emails from address to their own record. However, Importomatic is still mapping the attribute to address attribute instead of constituent attribute. This should be changed so that the data is consistent.
1 vote -
expose granular errors Levels to drive branches in batch script when scheduling unattended
On error level X DO Y
in the absence of functional error handling in the GUI it would at least be possible to email someone when an error of type X occurs.
1 vote -
Recommend using a UNC (rather than drive letter) for Exception Files Folder
(especially if referencing a drive mapping)
to prevent an error when using scheduler because the drive (mapping) is not present when not logged on.
1 vote -
Luminate Connector / Group Sync - ability to see which records were added & removed
It would be helpful to have a log of processing when importing or exporting. In particular, the message received after an Export using the Luminate Group Sync Connector usually doesn't make sense as far as number of constituents added or removed. A log file of processing would allow me to see exactly who was added or removed. There are also times during an Import where it's not clear on what data is being updated (again using a Luminate Connector).
1 vote -
When importing gift batch, warn of outstanding pledge balance or recurring gifts
Gifts that are meant to be a pledge payment or recurring gifts are in batches to be imported to RE. It would help if these gifts, would be kicked into an exception file so that they may be recorded as such. In RE/Config/Business Rules/Batch Options/When adding a gift to a batch, warn if constituent has Outstanding Pledge balance or Outstanding recurring gifts.
1 vote -
remove relationship link to non-constituent by mistake without deleting the other record
There have been a number of times a relationship link has been established by mistake between two non-constituent records. When you try to remove the relationship link it completely removes the entire non-constituent record from list management! This creates a nightmare to try to reconstruct the deleted record. I just want to break the link - not remove the record and all its history!
1 vote -
Gift Import Notifications
Create a file of any business rule notifications for imported donations. For example, if we have a notification for all users who have attempted to give fraudulently in the past, it would be nice to have a 'error' file that told us which imported records had this notification.
1 vote -
Individual relationship Additional Addressee/Salutations
Add ability to import an additional addressee for a non-constituent relationship. We are already able to import additional addressee for the main record and primary address for the spouse. We jut need this last field...
1 vote -
Accessing non-constituents from constituent or event records
When in a constituent or event and viewing a non con relationship/participant that is in list management have a button that allows you to push over or open the non con record in list management without having to navigate to List Management
1 vote -
Show where non-constituents live
When viewing a non-constituent have it list the names of the lists in LM or events that it is listed somewhere, like the bottom of their window like constituency codes or in properties. For a full constituent it would also be nice to be able to see from the record side what Lists in List Management the record falls into
1 vote -
FOM non-constituent have the same Fields as List Management
FOM should have the same fields that LM non cons have, if the LM module is installed. So that you do not have to go into LM to view all the information when FOM finds a non-constituent that is in LM
1 vote -
Business Rule or prompt for Non-Constituent in List Management
The ability to create a business rule that would appear when opening a full con that has a relationship to a non con that is in list management
1 vote -
View non-constituent from FOM results from Batch
When using barcode in gift batch and the value is not a barcode, when FindOmatic launches and performs a search based on this value but the selected record is a non-constituent, FOM should let you open the non-constituent record to review and confirm it is the correct record before promoting it to a full constituent. If selected it should handle it the promotion of the record based on user settings, always promote, ask, or never promote. Another option would be to view a record - hold the CTRL key while clicking on one of the matching records to open it…
1 vote -
Make "Change Data Source" into a button
To make this option more visible, instead of just a link (highlighted in blue), change the link into a button same as the "Save" button at the bottom of the profile screen window.
1 vote -
allow to export listmanagement fields
It would be helpful to see outside of Omatic how many list a person is on. We use the list as mailings so we can determine when and why we have mailed to them before.
1 vote -
allow for randomization in segment omatic
allow for randomization in segment omatic a common feature in any appeal
1 vote -
When matching to alternate address, prompt to make it preferred.
When IOM matches constituent via alternate address, prompt user that incoming address differs from preferred address by displaying the Address Processing Screen. This will give us the option to make incoming address the preferred address as this is the most current info provided by constituent. (We have donors who revert back to an alternate address, but right now do not know it because we cannot see it as it is done in the backend.)
1 vote -
Bucket exceptions into separate files based on error
It would be nice to bucket exceptions into separate files based on the error
1 vote
- Don't see your idea?