ImportOmatic 3.7.0.81 now available for download!

Version 3.7.0.81, July 7, 2021

*Scheduled for deployment in Blackbaud Azure and Colo environments Wednesday, July 7th thru Friday, July 9th.


Check out the list of improvements below, or visit the Release Notes section of the ImportOmatic User Guide for more details! When you're ready to install the update, head over to our Downloads page. Our User Guide provides instructions on how to update, and our Support team is available for help too!


If you’re using RE or RE NXT in the Blackbaud Hosting environments, this update will be available on July 7th for Azure clients and July 9th for COLO environments. We will post an update when these updates are complete.


If you’re using an Omatic Cloud Connector, this update does not require a profile refresh.


ImportOmatic

  • Added Gift Order Type to gift mapping for New Zealand databases
  • Upgraded .net framework to version 4.7.2 for increased support for TLS 1.2


Omatic Cloud Connectors

  • Fixed memory leak that caused a System Out Memory exception for Omatic Cloud Connector profiles when pulling large data sets
  • Added warning message when Omatic Cloud Connector profiles encounter an error connecting to an Omatic Cloud Connector endpoint
  • Fixed issue where Group setting was retained in memory from one Luminate Online Group Sync profile to another


List Management

  • Updated language on warning message when deleting list members to provide clarity
  • Upgraded .net framework to version 4.7.2 for increased support for TLS 1.2 


MergeOmatic

  • Fixed issue where merge wouldn't complete when records had data in the BBNC tables
  • Upgraded .net framework to version 4.7.2 for increased support for TLS 1.2


FindOmatic 

  • Upgraded .net framework to version 4.7.2 for increased support for TLS 1.2


ScoreOmatic 

  • Upgraded .net framework to version 4.7.2 for increased support for TLS 1.2


Retrace

  • Upgraded .net framework to version 4.7.2 for increased support for TLS 1.2

Scheduler

  • Updated to return a non-zero value when a failure occurs


As always, please let us know if you have any questions!