When FindOmatic is configured to be used with gift barcode in gift batch entry, non-constituents are automatically promoted to full constituents, even when the option to never promote relationships is selected. This is especially problematic when the only match is a non-constituent and is then immediately inserted into the batch and promoted without any warning.

I understand that this is an intentional part of the design, but I believe the user should be able to control this feature. This issue has resulted in numerous records being created that should not exist.

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).

For under 18s to our events, we do not record personal details. Instead we attached them as one anonymous children record to the parent record. We record the number of children in the total number of the Guest Number box. If would be helpful if we could import this.

When exporting a dictionary, the filename should be automatically populated with the dictionary name.

For bonus points: if an import option is ever added, the dictionary name should auto populate from the filename.

Allow this field to imported through the profile.

allow for randomization in segment omatic a common feature in any appeal

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.

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.

At the moment the error messages are pretty generic when a merge fails.

We noticed the mail merge option {%INVOICE_LIST%} column heading is confusing. We have an invoice to be paid in installments, but the Amount Paid column showing the total invoice amount paid shows the full amount of the invoice when we actually just made the first of two payments. (see attachment)

In version 3.3.2.0, the Profile Date columns (Created, Modified, Last Run) are displaying in m/d/yyyy format.
It would be preferred to display in the appropriate Region format for the local computer.
It is confusing for people who don't normally use month first.

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.

The LinkedIn Connector for AppOmatic has a bug when trying to log in with your LinkedIn credentials. It pushes out the error "Error logging in to LinkedIn. Please check your credentials and try again." though the credentials entered are correct.

When importing and the Duplicate Search Matching Results window appears with possible matches, the Birth Date field should correctly display fuzzy dates, both from the import data and the potential matches in Raiser's Edge.

Currently, if the import data has "8/6" in the birth date column, the DSMR incorrectly displays it at "8/2006".

The DSMR should correctly display month/day birth dates, as does RE 7.93+ : https://kb.blackbaud.com/articles/Article/41804

Include Position in the available columns when viewing org relationship duplicate search. This would allow me to see if I'm adding new data or if it's the same.

We want the ability to import a new organization relationship on an individual who has a pre-existing relationship to the organization with the same relationship and reciprocal values. Currently, Import-o-Matic matches to and modifies the pre-existing relationship - which happens even if option "Match organization relationships based on Always add new" is selected. We wish to import very similar relationships that differ only in the From/To date columns when compared to pre-existing relationships. Within options Constituents > Relationships > Organization > Organization Updates, how about adding a checkbox: "Create new relationship regardless of any pre-existing relationships"?

In Import we see the ID of the Import profile and the File to import: Could we also see the Description of the Import profile as this has more information than just the ID.

It would be ideal that if recieving data that combines multiple gifts in one line on a CSV, IOM would have the ability to split this one large gift into several smaller ones with their own funds, campaigns and appeals.