Transfer of objects hangs if 'transfer to' user owns object of same name

Millennium supports the use of multiple merchant accounts for credit card and bank draft transaction processing through Paya Payment Solutions (SPS). For each merchant account that a site maintains, the SPS merchant account ID, SPS merchant account Key, and a unique, descriptive name for the merchant account is entered into Millennium via the System Options screen. One and only one merchant account can be designated as the default merchant account - the account to be used by the system if a gift or dues purpose (restriction) has not been associated with a particular merchant account. One and only one merchant account can be designated for use when processing event registration fees.

Merchant account information is stored in the merchant_account system table.

A merchant account can be assigned to a gift/dues purpose (restriction) when entering or updating the purpose in the Chart of Accounts lookup table. See Chart of Accounts, Description and Chart of Accounts, Layout, for more information. When a donation is then made to that purpose, Paya Payment Solutions will use the assigned merchant account to process the credit card or bank draft payment. It is not mandatory that a gift/dues purpose be assigned a merchant account. If one is not, then Paya Payment Solutions will use the merchant account that has been designated as the default merchant account.

The conversion to Millennium 7.6.1 will move the Verus id and Verus key values stored in the sysinfo table to the merchant id and merchant key fields in the merchant_account table.

The conversion to Millennium 7.6.1 will also copy the default merchant id and merchant key to all credit card rows that do not have the merchant key filled in.

Actions-Actions Tasks not added to Outlook if Task Defined Default exists

IIS crash, various errors when updating attachments

System hangs after inserting membership with apostrophe in comments field

Journaling part of a Joint multi allocation leaves uneven giftamount on Primary record

Pledge information defined defaults not retaining start date

Existence of multiple Quid Pro Quo defined defaults causes Error Code 264

ORA-00936 'missing expression' error using Received Date when registering for an event

Unable to insert guest without registration

Tasks-Errors referencing missing .mit files

CAE Category, constituent count truncated on CAE Category Totals chart

Express Report fails after changing prompted value-based lookup

Queue history error A view does not exist for table 99 when report includes InternetAddress table.

Stored parameter lookup values not available when running a report

Express Reports not saved for the 'Run for user'

New fields added to the ecommerce_pending table impact add new fields to the ADE Import Tool. See Database Changes, ecommerce_pending, below, for further details

Donate Now is the gift processing component of the Online Constituent Directory. Donate Now is available to those institutions that purchase both the Online Constituent Directory andPaya Payment Solutions. Constituents and non-constituents alike can donate through Donate Now. A non-constituent who donates will become a constituent once the information he or she supplies during the donation process is processed through the Advanced Data Examiner. For the donor who is a constituent, the online donation form will be populated with his or her name,address and email information, and any changes that he or she makes to this information during the donation process will be updated in Millennium once processed through the Advanced Data Examiner.

The ADE Import Tool cannot be executed from the Program Files or Windows directory if it is installed on a Vista machine. The default installation directory is C:\ Millennium\Import Tools\Data Examiner Import Tool for all users.

Alternate ID (corealtid), social security number, and email address matching has been added to the ADE Import Tool.

The Millennium user will be able to map a Millennium Identifier to one field in the input file. This identifier can be a valid Millennium ID, an alternate ID, a social security number, or an email address. If this identifier field is not blank, the utility will attempt to match it to an existing Millennium constituent. If no constituent is found, then the input record can be either rejected, or the record can be entered into the pending tables as a new constituent, depending on what reject option the user sets. If more than one constituent is found, the input record will be rejected. If this identifier field is blank, then the input record can be either rejected, or the record can be entered into the pending tables as a new constituent. Again, this depends on what reject option the user sets.

Run-time error '52' Bad file name or number' received accessing Data Examiner Import Tool File menu options

Each run of the Years Utility through Millennium Reporter is documented in the CreateYearsOut.log file. This log file is located in the Queue directory, and notes the start and finish date and times, number of records selected by your criteria, number of records read and processed by the Years Utility, number of Summary rows created, and number of Summary rows updated. If the utility generates any SQL or programming errors during its execution, these will be noted as well.

Each run of the Summaries Utility through Millennium Reporter is documented in the CreateSummariesOut.log file. This log file is located in the Queue directory, and notes the start and finish date and times, number of records selected by your criteria, number of records read and processed by the Summaries Utility, number of Summary rows created, and number of Summary rows updated. If the utility generates any SQL or programming errors during its execution, these will be noted as well.

If the district (table_dist), territory (table_terr), region (table_regn) and/or zone (table_zone) fields in the countries lookup table are changed, then DataSync will update the district, territory, region and/or zone fields in the address table to reflect these changes.

Each run of the Delete Correspondence Utility through Millennium Reporter is documented in the DeleteCorrOut.log file. This log file is located in the Queue directory, and notes the start and finish date and times, the number of records selected by your criteria, and the number of correspondence rows that were deleted. If the utility generates any SQL or programming errors during its execution, these errors will be noted as well.

Each run of the Delete Attribute Utility through Millennium Reporter is documented in the DeleteAttrOut.log file. This log file is located in the Queue directory, and notes the start and finish date and times, the number of records selected by your criteria, and the number of attribute rows that were deleted. If the utility generates any SQL or programming errors during its execution, these errors will be noted as well.

Each run of the Expire Membership Utility through Millennium Reporter is documented in the ExpireMembershipsOut.log file. This log file is located in the Queue directory, and notes the start and finish date and times, the number of records selected by your criteria, and the number of membership rows that were updated. If the utility generates any SQL or programming errors during its execution, these errors will be noted as well.

'No Matches Search again for a constituent record' message when searching in the Merge ID utility.

Slow performance when running the Zip Code Address Update utility

The following field was added to hold a reference number that is returned by Paya Payment Solutions when a credit card or bank draft transaction is successfully processed.

credref

The following fields were added to support Paya Payment Solutions multiple merchant accounts:

credmerid

credmerkey

The following fields were added to support the reversal of credit card payments or bank drafts that have been successfully processed through Paya Payment Solutions, when the transaction to which the credit card or bank draft is linked is subsequently journaled or journaled and corrected.

credvoidfl

credvoiddt

credvoidrf

The following fields were added to allow users to insert data into the fields that correspond to the fields in the gifts and dues data tables:

ecomclass1    (giftclass1/duesclass1)

ecomclass2    (giftclass2/dueseclass2)

ecomlook1     (giftlook1/dueslook1)

ecomlook2     (giftlook2/dueslook2)

ecomlook3     (giftlook3/dueslook3)

ecomdepost   (giftdepost/duesdepost)

ecomyesno    (giftyesno/duesyesno)

The following fields were added to support Paya Payment Solutions processing:

ecomntitle

ecomnlast

ecomnfirst

ecomnmiddl

ecomnsuffx

ecomguid

ecomref

The following fields were added to support Paya Payment Solutions multiple merchant accounts:

ecommerid

ecommerkey

These fields were added to support Paya Payment Solutions multiple merchant accounts:

chart_mkey

chart_mid

table_ecom

membexpdt2

membactiv2

The merchant_account system table has been added to the database to support Paya Payment Solutions multiple merchant account functionality.