Millennium Release 7.1 |
|||
|
|
|
|
The following items are included in Release 7.1. Note that some items are enhancements to the software and some are corrections. The correction items describe the symptoms that you might have encountered, prior to the installation of this Release.
EIS World |
||
EIS World Corrections |
||
Reference World |
System-wide Enhancements
Interface |
Function |
Description |
All |
Java applets |
List boxes within java applets (allocation maintenance in Giving, constructing new criteria in Reporting) now permit you to enter a single character and have the first matching entry in the list highlighted and shown in the text box. If you repeat that same keystroke, you can scroll to the next matching entry, and so on, until the desired entry is shown in the text box. |
All |
To maintain current Millennium functionality when using SQL 2000, it was necessary to change the defaults on the table fields <tablename>userid from SUSER_NAME() to SUSER_SNAME(). The same change was made in all triggers, as needed. Note: If your institution uses any site-created or custom scripts using this function, they must also be edited. |
Profiles Enhancements
Interface |
Function |
Description |
All |
Address |
The following changes have been made to the Address Update function (not editing). When the insert form is presented, it will no longer include the Region, District, Territory, or Zone from the previous address row. When the row is inserted, that information will automatically be entered in accordance with the ZIP Code information that is contained in insert form. The conversion to 7.1 automatically creates a 'former' version of each of the entries in your institution's Address Type lookup table. When you use the Address Update function, the system will change the Type of the archived data row to the 'former' version of the previous Type. (This is in addition to the other automatic edits of changing the Locator to 'Former' and deactivating the Utilizations. |
All |
Address |
When entering a USA address, the system now prevents you from entering ZIP Code information that is not found in the lookup table. An error message is given and you may cancel the address insert or update, or you may go back to the previous maintenance form and change the ZIP Code information. |
All |
Address |
When a spouse Relationship is changed to divorced, any Addresses that are linked to the spouse's Address will be unlinked. |
All |
Address |
The following fields have been added to the Address table. All are non-displaying fields used by the optional Millennium component, Correct Address. addrcass1 |
All |
Allocation Maintenance |
It is no longer possible to delete a journal transaction from within the allocation applet. (This would result in 'orphan' void transactions.) Also, if a void transaction is deleted, the corresponding journal transaction is automatically deleted. |
All |
Attachment |
You may edit individual Attachment names or you may delete individual Attachments from the data row to which they were linked. A yellow edit button is now shown to the left of the display of the Attachment name in the data display which accesses an edit form which is used for either of those purposes. You may still unlink all Attachments to that data row using the Special menu (Browser) or the right-click context menu (Windows). |
All |
Constituent Search |
The system will now warn and prevent you from executing a standard search with no data entered as search criteria. |
All |
Correspondence |
Several related changes have been made to allow the association of a Solicitation with a particular Correspondence. The Correspondence Name lookup table now includes the ability to associate a Solicitation with each Correspondence Name. The Correspondence data table now includes the data fields corrsolic, and corrsolnm for the code and value of the Solicitation that is associated with the Correspondence Name that you choose for the data row. Those fields are automatically entered by the system and therefore they do not appear in the insert or update forms. The standard display template for the Correspondence data table has also been edited to include the Solicitation name. |
Browser |
Data Entry |
During data entry, if an Millennium SQL error message is encountered, the message screen includes a Cancel button to cancel the insert or update form (without the insertion or update of any data row) and a Back button, which will return you to the data maintenance form, containing all the data you had entered. You may then correct the information that generated the error and try again. |
All |
Data Entry |
During data maintenance, when you tab to a non-table driven text box that already contains data, the entire contents automatically highlight so that you may replace the entire contents by typing new information. |
Browser Internet Explorer |
Data Entry |
Hot keys have been added to the Browser data maintenance forms, which enable Internet Explorer users to use the keyboard short cuts to navigate through the form and enter data without using the mouse. (Netscape Communicator does not support this functionality.) |
All |
Death |
Three new fields have been added to the Death table and its standard maintenance and display templates. Those fields are: Notified Date (deathnotdt), Corroborated Date (deathcordt), and Source (deathsrce). |
All |
Death |
When a Death row is created, the system will now set all Membership rows and any of their linked rows to inactive. If a Tracking row exists, the Current Prospect flag will automatically be set to N. |
All |
Dues |
When the Discount Code is edited in a Dues transaction (a transaction that is linked to a Membership) the Discount Amount is also updated in accordance with that entry in the Membership Discount lookup table. |
All |
Education |
Constraints have been added to the Day, Month and Year fields for Degree Date to ensure that only valid values may be entered. |
Browser |
Fast Data Entry |
Sustainer pledge transactions are now available in the display area of the Fast Data Entry form. |
Windows |
Filtering and Sorting |
Filtering and Sorting have been activated for use with the Windows interface. |
Browser |
Giving |
A new option has been added for the display of Gifts or Dues in the Browser interface. In addition to the Long and Short modes, a 'Mini' mode allows you to view all transactions, each shown in a single-line format. A standard set of data from each row is displayed, using codes from lookup table data, and also using certain codes to indicate the existence of linked information. Each primary allocation transaction will have an Edit button and a detailed display button so that you may view or edit the transaction. Secondary allocations will be shown immediately following the primary allocation, with edit buttons that lead to the allocation applet. Pledge transactions are shown with hyperlinks to the Payment Schedule and also to a Post Payment form. For more details on this feature, see Giving Display. |
All |
Giving |
A text box for Comment has been added to the Allocation Edit applet, allowing you to enter different comments for individual allocations in a transaction. The Comments will be displayed with their respective allocation. |
All |
Giving |
When creating a matching transaction, you may choose either Match Pledge or Match Potential as the transaction type as the transaction is being created. |
All |
Giving |
When editing a transaction that is linked to other transactions, a message box is displayed warning that the linked transactions will not automatically be updated with the edits to the original. If those edits are desired for the linked transactions, they will need to be modified manually. |
All |
Giving |
The Giving Display includes a notation in red just below the table header that indicates the number of outstanding (unpaid) pledges for the current constituent. |
Browser |
Giving |
Several changes have been made to accommodate the editing of the non-allocation portion of a journal transaction. The journal transaction is displayed as before (as if it were another allocation) but with the addition of the Process Date and the Batch Number that belongs to the Journal transaction. In addition, the Edit button to the left of the journal is shown in yellow. If you use that button, you will access an update form for the non-allocation portion of the journal, where you may make edits to any of the editable columns. To edit any of the fields in the allocation portion of the transaction, you should use the blue Edit button shown to the left of the allocation display of the void transaction. This will launch the allocation applet, where you may edit any of the editable fields in any of the allocations - either in the void or the journal transactions. |
All |
Giving |
The editing functionality for transactions with a Ledger Flag set to Y is now the same as for those transactions that are part of a closed batch. |
All |
Giving |
Several related changes have been made to accommodate two additional Pledge Types. The Pledge Type Lookup table now includes the entries: Semi-monthly -- sm Semi-monthly No Bill -- smn. The Pledge Billing schedule options now include semi-monthly and semi-monthly no bill. This generates a default Payment schedule twice a month with billing days of 01 and 16. |
All |
Giving |
Pledge Potential transactions are not automatically changed to Pledges when a Payment is posted. If you want to change the Type, you may do so manually via an item in the Special menu. Note that when Pledge Potentials are changed to Pledges, they are always changed to conditional Pledges, in order to maintain the integrity of the Asset and NPV Amounts. |
All |
Giving |
When Pledge Potentials, Sustainer Pledges and Match Potentials are created, the NPV (giftnetpv) defaults to $0, as these transactions are appropriately considered conditional (not legally binding). |
All |
Giving |
If a Pledge of $0 is entered, it is automatically considered conditional and the revocable flag is set to Y. |
Browser |
Giving |
Several additional items in the Special menu for transactions have been activated for use with Pledge Potential transactions. These are: Add Joint Transaction |
All |
Membership |
When processing Memberships via Dues, the Membership Source now defaults to the Dues Source. |
All |
Membership |
You may now define a Membership Type to use the same day of the month as the Membership Date for the Renewal Set-up. The Membership Type lookup table was enhanced to allow this additional option, Rolling Membership, Same Day. |
All |
Membership |
Several enhancements have been made to the Automated Membership Process. When a new Membership is created, and the forms are presented for the creation of the Membership Cards, the second such form will default to the spouse name (if any). When a renewal, rejoin, upgrade or downgrade Membership is created, and the forms are presented for the creation of the Membership Cards, they will default to the names used in the Membership Cards from the previous Membership. When a renewal, rejoin, upgrade or downgrade Membership is created, and the forms are presented for accepting or declining the Membership Benefits, the system will default those settings in accordance with those settings in the Benefits that were linked to the previous Membership. If none are found of the same Type, the settings will default to Accepted for standard Benefits, and Cancel for optional Benefits. When a renewal, rejoin, upgrade or downgrade Membership is created, and the forms are presented for accepting or declining the Membership Publications, the system will default those settings in accordance with those settings in the Subscriptions that were linked to the previous Membership. If none are found of the same Name, the settings will default to Accepted for standard Subscriptions, and Cancel for optional Subscriptions. |
Windows |
Mergeid |
The Merge Id utility has been incorporated for use via the Windows interface. Access to this functionality is through the Profiles World's action bar items, File/Mergeid. This utility transfers existing data rows from one constituent id to another. For more information, see Merge Id |
All |
Name |
New functionality has been added for the generation of a preferred name for a constituent couple (when one constituent is created on the system to represent a married couple, as indicated by a gender of 'C'.) Two new standard entries have been added to the Name Types lookup table: Husband Preferred (Code: ha) and Wife Preferred (Code: wa). When doing data entry for this constituent, if you create two Name rows, one of each of the new types, the system will verify the gender of 'C' and then automatically create a third Name row with a Name Type of Preferred. The Combined Name and Combined Salutation fields for all three Name rows will automatically be filled in, in accordance with the system rules for doing so when the individual names belong to two different constituents with a spouse relationship. Note that this automatic process only occurs when there is no Preferred Name row already in existence, and that once the Preferred Name has been created, it is not automatically updated if edits are made to either the Husband or Wife Preferred Name rows. |
All |
Name |
The default for the Lookup check box on a new Name row has been changed from 'N' to 'Y'. |
All |
Planned Gifts and Proposals |
Columns have been added to Planned Gifts (planpdistr) and Proposals (proppdistr) to track the Percentage of the distribution that has been made. |
Windows |
Printing and Previewing |
Several new options are available to the Windows
interface via the File, Print action menu bar items. |
All |
Relation |
If a Relationship with a Type of Divorced Spouse is created or edited, the system now checks for the presence of another Relationship of Spouse, Spouse No Mail, Surviving Spouse, or Deceased Spouse. If one of those Relationships exists, the Basic Data Marital Status is not changed to Divorced. (This allows you to enter historical data without having the system incorrectly update the Marital Status.) |
Profiles Corrections
Remember that the descriptions for the following items describes the problem PRIOR to the installation of the corrections as part of the current release.
Posted Date Reported Problem # |
Function |
Database |
Interface |
Description |
4/19/01 30. |
Unlink Attachment to Chart of Accounts |
SQL Server |
Browser |
When you try to unlink an attachment to the Chart of Accounts, you receive an Millennium Error: Unable to unlink record. Please contact system administrator. [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid field name 'e0284'. UPDATE chart_of_accounts SET chart_doc = 'N' |
3/26/01 28. |
Posting Match Potential |
All |
Browser |
After posting a match potential to the secondary side of the joint transaction, the total on the secondary side of the transaction reflects the match, but the primary side of the transaction does not. |
3/23/01 27. |
Write-off Pledge Over Payments |
All |
Browser |
When you write of the over payment of a pledge, the total is not recalculated correctly. |
3/08/01 26. |
Giving Trends |
All |
Browser |
After writing off a pledge balance, the total in Giving Trends, with Include Pledges selected, does not reflect the write-off. |
3/8/01 25. |
Updating Attribute Default |
All |
Browser |
When updating an Attribute default, a runtime error may result. |
3/8/01 24. |
Posting a Pledge Payment |
SQL Server |
Browser |
When posting a payment to a joint pledge that has an automatic quid on it, the quid is taken twice on the spouse record. |
3/7/01 23. |
Posting a Pledge Payment |
SQL Server |
Browser |
When you post a payment to a conditional pledge, the net present value remains 0. |
3/7/01 22. |
Fast Gift Entry |
All |
Browser |
When you do a search from the fast gift entry screen and return to the fast gift entry screen, the focus is on the frame, rather than the first available text box. |
3/7/01 21. |
Address Update |
All |
Both |
When the address update function (not simple editing) is used on an address which is linked with spouse, the utilization fields on the spouse's linked address are not unchecked on the 'former' address |
2/5/01 20. |
Joint Expectancy Transactions |
All |
All |
The Net Present on joint Expectancies is automatically set to $0 - it should default to half of the face value, or it should accept any amount that is manually entered in the insert form and split that amount between the two parties who jointly own the Expectancy. |
2/2/01 19. |
Creating Constituents |
All |
Browser |
When creating a new constituent, the system copies certain information that was entered into the Search form into the data entry forms that are automatically presented. This includes those fields which were blank in the Search form. This behavior will override existing data in the Default definition. |
2/2/01 18. |
Membership |
All |
Browser |
When entering a Membership (via Membership rather than via Dues), if the first entry in the Membership Type lookup table has a blank Renewal Day, the Membership applet shows a red error message at the bottom that indicates that the Dues Effective Date is invalid. |
2/2/01 17. |
Gift Total Asset, Dues Total Asset |
SQL |
Browser |
An error may occur in the system calculation of the gifttasset or duestasset field for multiple-allocation transactions. This could result in an arithmetic overflow error. |
2/2/01 16. |
Deleting Name Rows |
Oracle |
Browser |
An error message is encountered if you attempt to delete one spouse's Name row, and when the second spouse has two Name rows of the same type as the deleted one. |
2/2/01 15. |
Comment Data Entry |
All |
Browser |
When pasting text into a Comment text box in
an insert or update maintenance form, if the text includes returns, the
system truncates the text from that point onward. This is behavior of the HTML tag INPUT TYPE="text"
in the comment text box. |
12/21/00 14. |
Address Update |
Oracle |
Browser |
When a preferred address is updated and then a constituent search is performed, the new preferred address is not shown in the Next Search results display. |
12/21/00 13. |
Non-constituent Employer |
All |
Browser |
When an existing Employment row specifies a non-constituent as the employer, and when other data from that row is edited, a constituent search form is launched. |
12/7/00 12. |
Education Custom Fields |
All |
Browser |
The following list of Education custom fields
cannot successfully be added . to the html display and maintenance templates
(.mit file). |
12/1/00 11. |
Attribute Default |
All |
Browser |
When a Default is used to create an Attribute, and when the Attribute Type is edited prior to inserting the row, the system creates the row using the Attribute Type found in the Default, rather than the edited one. |
11/10/00 10. |
Pledge Payment Schedule |
All |
Browser |
Due to a rounding error in the JAVA applet, the Payment schedule may freeze when the Payments use certain combinations of amounts, or when attempting to create a new row in the Payment schedule. |
11/10/00 9. |
Combined Names |
SQL only |
Browser |
When a spouse/spouse Relationship is deleted, the combined forms of the two constituents' name rows is not adjusted. |
11/3/00 8. |
Advanced Search |
SQL only |
Browser |
Attempts to execute an Advanced Search may produce an error message, stating that the existing query results could not be dropped. |
11/2/00 7. |
Giving Trends |
All |
Browser |
When the Giving Trends options are set to include Credits and Pledges, and when a pledge payment has been made by another constituent (resulting in a pledge being paid with a credit transaction) the system does not correctly calculate the amounts for the Giving Trends. |
11/1/00 6. |
Attribute Default |
All |
Browser |
When creating an Attribute Default, the value-based lookup applet for the Attribute Type only recognizes entries that are active for use as a stand-alone Attribute (in the lookup table entry.) This behavior is not affected based on whether the entry is also marked as active or inactive for use as linked Attributes. |
11/1/00 5. |
Attribute Default |
All |
Browser |
When an existing Attribute Default is edited, if the Attribute Type is edited, the value-based (super) lookup applet is not invoked and the edits are not preserved. Problem does not occur if Attribute Type is not edited. |
10/25/00 4. |
Job Status |
Oracle only |
Browser |
When the Job Status in an Employment row is updated from Active to No longer at this position, the following error message is received. [Microsoft][ODBC driver for Oracle][Oracle]ORA-04091: table MILLORA.JOBS is mutating, trigger/function may not see it ORA-06512: at "MILLORA.TB_JOBS", line 165 ORA-04088: error during execution of trigger 'MILLORA.TB_JOBS' |
10/25/00 3. |
Classification 1 and 2 |
All |
Browser |
When a transaction has multiple allocations, the data for Classification 1 or Classification 2 may not be appropriately assigned to the individual allocations. |
10/25/00 2. |
Quid Pro Quo Amount |
Oracle only |
Browser |
When a Quid Pro Quo data row is created, other Quid Pro Quo data rows whose quid values which were $0, might also be edited. |
10/25/00 1. |
Dues Deductible Amount with Quid |
Oracle only |
Browser |
When a Quid Pro Quo amount exceeded the amount of a Dues transaction, the deductible amount defaults to a negative dollar amount. |
Events Enhancements
Interface |
Function |
Description |
All |
Activity |
Functionality has been added to the Registration process for Guests in relation to the Maximum # of Guests for an Activity. The system now checks that limit and prevents you from creating more Attendance rows for an Activity than the number specified in the Maximum # of Guests field for the Activity. |
All |
Attachments |
It is now possible to link Attachments to the following Events data tables: Activity |
All |
Attendance |
The system now prevents you from creating multiple Attendance rows for the same Activity which have exactly the same combination of Table, Seat, Section, and Row information. |
Windows |
The use of the Seating Layout table has been activated. This was added to the database as a data table in release 7.01, but was not available for use until this time. Since that release, an additional field has been added for the name of a seating table (laytblname). See the topic, Seating Layout, for more information on the use of this data table in Events in the Windows interface. |
Events Corrections
Remember that the descriptions for the following items describes the problem PRIOR to the installation of the corrections as part of the current release.
Reported Problem # |
Function |
Database |
Interface |
Description |
3/8/01 2. |
Deleting a Registrant |
All |
Browser |
When deleting a registrant, who is a guest, their guest row is deleted, however the Total guests on the Events detail screen is not changed. |
2/5/01 1. |
Event Web Reports |
All |
Browser |
An error may occur when attempting to access
the Event web reports, if Crystal Reporting is not installed on your IIS
machine, or if either craxdrt.dll or cpeaut32.dll is not registered. To correct the problem, verify the installation of Crystal on the IIS. If the problem does not resolve, execute the following commands at a command prompt. regsvr32 c:\winnt\system32\craxdrt.dll regsvr32 c:\winnt\system32\cpeaut32.dll |
Reporting Enhancements
All |
Brio Reports |
An additional output option is available for use with Brio Reports. You may now export to PDF format, in addition to those options previously available. |
All |
Deleting Reports |
The system administrator login has been given the ability to Delete any report listed in the View Report or Edit Report listing, regardless of ownership. |
All |
Edit Menu |
The display of the Edit Criteria menu of saved criteria names now includes the Report Description from the criteria to assist in identifying a report. |
All |
New Criteria |
The display of the New Criteria menu of report template names now includes the Report Description from the template. In addition, a question mark in a yellow circle acts as a hyperlink to the Help documentation for each template. |
All |
Output List |
A new option has been added to the Output list possibilities. Now, in addition to choosing Crystal formats, Brio Reports Formats, or standard Millennium utilities, you may also choose Batch File as the output destination of the run of a set of criteria. If you do so, the system will generate a standard export worktable based on the criteria statements and other report options, and then pass that table and a set of system-generated parameters to a batch file of your own creation. You may construct this batch file to incorporate multiple SQL scripts, or other executable program files. Note that responsibility for the creation and execution of such batch files is outside the realm of standard Millennium training and support services, and is undertaken entirely at the discretion and liability of your institution. |
All |
Print Preview on the Queue Machine |
You may now disable the Print Preview option for any reports that are run from a particular Queue. This option is set from the System Info page in System Upkeep in the Tools World. |
All |
Report Groups |
Several related changes have been made to support an additional technique for classifying and securing reports within the structure of the nine standard report libraries. The Tools World includes a new item, Report Groups. In the Browser interface, it is shown in the Millennium Explorer under Tools World, between Profiles Lookups and System Upkeep. In the Windows interface, it is shown in the Tools World, Table Maintenance listing. This provides access to the new, specialized lookup table, Report Groups. When you define entries for this lookup table, those entries will be used as the names of the Report Groups into which you may place reports that you create and save. Your Report Group names are classified into the standard libraries by use of the Group field in the Report Group lookup table entries. You may specify that your Report Group be associated with a single library or that it be available to all of the libraries. (To support this, the Table Groups lookup table includes several new, standard entries for the library names.) When you define a Report Group lookup table entry, you may also specify which Millennium User Groups (MUG) will or will not be given Access and Maintenance privileges to the entry. Those users without Access to the Report Group lookup table entry will also be denied access to the reports that are stored with that Report Group. The Report Groups apply to the Viewing of the HTML output of a report that has already been run, and the Editing and Running of saved criteria. |
All |
Report Form |
Several changes have been made to the appearance of the main Millennium Reporter's Report Form. The function buttons and the action buttons below them have been replaced by a pair of menu bars. The top menu bar has the same items that were previously function buttons, namely: File, Save, Edit, Option, and Help. When you click on one of the items in the Function Toolbar, the Action Toolbar below it will show the items that correspond to that function. Items in the Action Toolbar will be enabled or disabled as appropriate. For instance, none of the Edit items are available until or unless an existing criteria statement has been highlighted. The main Report Form has been adjusted to show the Report Title and the Format/Utility name, each on its own line, in order to display the entire title or name. |
All |
Run Option |
An additional Run option has been added to reporting. You may now execute a report that uses an existing export worktable, rather than running a selection to generate a new one. If this option is activated when the report is launched, you will be prompted to specify the name of the worktable and it will immediately be passed to the specified utility or Crystal format. This allows you to do such things as: Use the same worktable for the production of letters and envelopes. Run a report to verify that you have selected the desired constituents, and then use the same worktable with the Add Attribute Utility. |
All |
A standard library of subreports has been added. The subreports are taken from the standard Millennium formats and are now made available to you for use as you construct custom formats using Seagate Crystal Reports software. The subreport library is located either mill\Formats\Subreports (SQL) or mill\OracleFormats\SubReports (Oracle). |
|
All |
Totals |
You may now define Totals that are calculated using the Deductible Amounts of the selected transactions. |
All |
Totals |
You may now restrict the kinds of Credit transactions that are used in the calculation of a particular Total. First, the Total definition must include criteria statements that specifically select transactions with a Type of Credit ('c'). (Other Types may also be selected for inclusion in the Total if desired.) If Credits are specified in the Total definition, then the new function is controlled by three radio button options shown at the bottom of the Total option form. You may include all selected Credit transactions (this mimics the behavior prior to Release 7.1) in the calculation of the Total. You may include only those selected Credit transactions which are NOT linked to another transaction, in the calculation of the Total. This would include only independent Credit transactions. You may include only those selected Credit transactions which are not linked to the owner's spouse's transaction, in the calculation of the Total. This would include both independent and linked Credit transactions, as long as the link goes to a transaction that does not belong to the spouse. (This option may be used to prevent the double counting of spouse linked transactions when using the Include Spouse option at the top of the Total option form). |
All |
Totals |
You may now use <A Prompted Reply> object within the definition of a Total. |
All |
View Reports |
When using the View Report option, the display of the report names will now include the username and the date that the report was last run. |
Reporting Corrections
Remember that the descriptions for the following items describes the problem PRIOR to the installation of the corrections as part of the current release.
Posted Date Reported Problem # |
Function |
Database |
Interface |
Description |
4/13/01 12. |
Criteria Using Never Checked |
All |
Browser |
When running a criteria that uses Never Checked option, the report will return an error message: missing expression error #00936 |
3/14/01 11. |
Duplicate Removal |
SQL Server 7.0 |
Browser |
Duplicate Id will appear in the worktable. One id will have a name and one id will have nothing in the name in the worktable. |
2/9/01 10. |
VQuery Appears to Hang - Duplicate Removal |
Oracle |
Browser |
VQuery appears to hang during the removal of duplicates processing. CPU usage appears to be very low and the system processes are the only ones that appear to be running in the Task Manager. |
2/2/01 9. |
Totals |
All |
All |
When calculating Totals using the Include Match Credit option, an error message (Connection is busy with results for another HSTMT) might be encountered. |
2/2/01 8. |
Reporting Options |
All |
All |
Individual users may experience a problem with the display of the Option, Default or Option, Report forms. Workaround: Delete the row in the Report_options system table for that user. |
2/2/01 7. |
Selecting Batch Numbers |
All |
All |
An error may occur, causing the Millennium Reporter to 'freeze', when reporting criteria attempt to select transactions based on blank Gift or Dues Batch Number data. |
12/21/00 6. |
Phonathon Form.rpt |
All |
All |
This format includes an incorrect linkage to the address table which can result in a phone number other than the home address phone being selected. |
12/21/00 5. |
Daily Report - Gifts.rpt |
All |
All |
This report format includes subreports which do not have the headers and footers suppressed. |
11/14/00 4. |
Report Descripts |
All |
All |
When a report has been run to HTML and that same report is then run to HTML for a different user, the second user's results are not listed in the View Reports list. (The second user's report does run correctly to completion and the results are appropriately placed in the reports folder.) |
11/14/00 3. |
Reporting with Parameters |
All |
All |
Due to a change in the behavior of Crystal version 8, if a format uses a parameter that is not defined in the Millennium report criteria, the system prompts on the report server for user input to define that parameter. This occurs at the time that the process reaches the formatting stage. This includes the format parameter for a landscape report. When the parameter information is entered, the formatting process will continue. |
11/2/00 2. |
Reporting with SQL Views |
SQL only |
All |
An error may occur in the following circumstance: |
10/20/00 1. |
Criteria with Totals (only) |
All |
All |
The system allows you to save and attempt to run a set of criteria that contains only Total definitions, but has no criteria statements. The Millennium Reporter should prevent you from saving such a set of criteria. |
Tools Enhancements
Interface |
Function |
Description |
All |
The Accounting Export Utility is available, enabling you to create an Excel export file based on either Gifts or Dues transactions. This utility is accessed and launched via the Millennium Reporter and consists of two additional standard report criteria templates in the Financial report template library. |
|
All |
Address Types Lookup |
Release 7.1 will create duplicate versions of most entries in your Address Type lookup table, to accommodate the new Address Update functionality. For each existing entry, a 'former' version will be created, using the same code but ending with an 'f'. For example, the entry Home/a will generate an entry of Former Home/af. These entries will be created with the Active flag set to 'N' so they will not appear in data entry situtations (though you may set any of them to 'Y' if you want to use them in regular data maintenance). No such entries will be created for Deceased/d or Former/form. If an existing entry uses a code of six characters, the conversion will replace the final character with an 'f'. |
All |
Attribute Type, Institutions, Solicitations Lookup Tables |
A search function has been to added to the process of displaying the Attribute Types, Institutions, and Solicitation lookup tables. This function behaves in the same way that the display search does for Chart of Accounts. This eliminates the need to display the entire table for those lookup tables which are most likely to be extremely large. |
All |
Chart of Accounts |
The Chart of Accounts now includes the same 11 customizable table fields that each of the data tables uses. These fields are: chart_dte1 This also necessitated the creation of three additional lookup tables, chart_lookup1, chart_lookup2, and chart_lookup3. These customizable fields behave in the same ways as those that are available for the data tables. |
All |
Chart of Accounts |
A field has been added to the Chart of Accounts to track the Department (chartdprt). This field is driven by the Department lookup table, which is also used for Education and Correspondence. When an entry is selected from the Chart of Accounts for use in a Gift of Dues transaction, the Department field will be copied to the Gift or Dues Department field and displayed as part of the standard detail display. (Note that this is in addition to the Department Id field in the Chart of Accounts which is designed to hold the Millennium Id # of the contact person within the Department.) |
All |
Create.exe |
The installation utility, Create.exe now includes the ability to add and remove constraints on system tables and reporting tables. Previously, this utility only operated on the data tables. |
All |
The Data Sync utility has been modified to include the new Chart of Accounts field, chart_dprt and the corresponding data columns, giftacdprt and duesacdprt. |
|
All |
A Delete Attribute utility is now available. This utility operates from within the Millennium Reporter, using an export worktable to identify the specific Attribute data rows that you want to delete. You may launch the utility from the same run of the criteria that you use to select the Attributes, or you may create and save the export worktable (and check it to verify that it identifies the appropriate Attributes) and then launch a new report that uses that saved export worktable. |
|
All |
A Delete Correspondence utility is now available. This utility operates from within the Millennium Reporter, using an export worktable to identify the specific Correspondence data rows that you want to delete. You may launch the utility from the same run of the criteria that you use to select the Correspondence rows, or you may create and save the export worktable (and check it to verify that it identifies the appropriate rows) and then launch a new report that uses that saved export worktable. |
|
All |
An Expire Membership utility is now available. This utility operates from within the Millennium Reporter, using an export worktable to identify the specific Membership data rows on which you want to change the Active status to 'N'. You may launch the utility from the same run of the criteria that you use to select the Membership rows, or you may create and save the export worktable (and check it to verify that it identifies the appropriate rows) and then launch a new report that uses that saved export worktable. |
|
All |
Group Maintenance |
You may now specify a view that will determine the ability to insert data rows. To accommodate that function, the Group Maintenance form includes a Change Insert button and a text box for the name of the view, rather than the Allow Insert check box. |
All |
Lookup Table Access Security |
A change has been made to the behavior of Access security on lookup table entries. Previously, if a user did not have Access security for a particular lookup entry, the message "Access denied to value" was shown instead of the value when a data row using that entry was displayed; that user would not get the value in the lookup list box or in value-based lookups during data entry or maintenance; that user could edit the data row and change the value to another lookup entry for which he or she did have access security. With Release 7.1, if a user does not have Access security for a particular lookup entry, he or she will see the lookup value in data displays. If that user accesses an update form for a data row that uses that lookup entry, the list box will show that entry, but no others from that lookup table because the user may not change that information in the data row. If that user accesses an insert form, or an edit form for a data row that does not already use that entry, then the corresponding list box or value-based lookup box will not include the entry in the list of available lookup entries. |
All |
Membership Type Lookup Table |
An additional option has been added to the Renewal Set-Up field in the Membership Type lookup table. Now in addition to the previous options, you may choose a Rolling Membership, Same Day. This allows you to use the exact date of the Membership as the renewal date, rather than the first or last of the month. |
All |
Pledge Types |
Two additional standard entries have been added to the Pledge Types lookup table. They are: Code: sm 	Value: Semi-monthly |
All |
Priority |
Three additional standard entries have been added to the Priority lookup table to support the automatic updating of Microsoft Outlook Tasks with info from Millennium Tasks (Windows interface). They are: Code: low	Value: Low |
All |
Relationship Types |
Additional standard entries have been added to the Relationship Types lookup table to support the Relationship Tree. They are: Code: bro 	Value: Brother |
All |
Report Groups Lookup Table |
The Report Groups lookup table has been added to support the additional classification and security functions that were added to the Reporting World. Rather than being used by a Profiles or Events data table, these lookup table entries are associated with individual sets of report criteria, or with the final output from the run of a report. This lookup conforms to the standard lookup table layout. The Group (table_type) field in the lookup table contains one of the new standard entries from the Table Groups lookup table to identify with which of the standard report libraries this Report Group should be associated. (To track this association, several fields have been added to the Report_descripts table.) |
All |
The Summaries Utility has undergone a major renovation, including the following: Use of this utility is now a two step process. The utility is launched in its own interface, outside the regular Millennium interface. You may use that window to create and save multiple Summary definitions. Then, from within the Millennium Reporter, you may create a set of criteria that will select the set of constituents for whom the Summaries will be created or updated, and which will also define any Totals that are referenced in the Summary definitions. The utility now allows you to create and save multiple Summary definitions, which may consist of Totals, calculations involving Totals, constant values, or other calculations, or conditional statements for the determination of Descriptors. Those conditional statements may use Totals, Calculations, or constant values. In addition to the Summaries Utility, the Years Utility is also available for the definition of Summary data rows. |
|
Browser |
System Info |
The System Info page has re-labeled the Millennium Report Information that was formerly labeled Crystal's RPT Default Location to Default Format Location. |
Browser |
System Info |
The System Info page has an additional setting for the Millennium Reporting Queue. You may now enable or disable the Print Preview function for a Queue. (This permits you to restrict this feature if the Queue is located on a machine in a remote location.) |
Browser |
System Info |
The System Info page now includes sections to identify the Millennium OLAP Server, and the Millennium Replication Server. |
All |
System Tables |
A new system-use table has been added, named memory_definition. It is used by the new version of the Summaries utility and the Years utility. |
All |
Table Groups Lookup Table |
Several new, standard entries have been added to the Table Groups lookup table. These are: Biographical Reports (rbio) |
All |
Task Status Lookup Table |
Additional standard entries have been added to the Task Status lookup table to support the automatic updating of Microsoft Outlook Tasks with info from Millennium Tasks (Windows interface). They are: Code: ntstrt	Value: Not Started |
All |
Years Utility |
The Years Utility is now available for use in defining Summary data rows that identify the year in which a particular kind of giving transaction took place, such as the year of the first, most recent, or largest transaction. The utility allows you to create and save a single such Summary definition. Then when running the Millennium Reporter, you may specify the Years utility and have the Years definition applied to the selected constituents. |
All |
A new utility is available to update the ZIP Code lookup table on your system. A text file of changes is available from Community Brands as a subscription service. Alternately, you may use the utility with a file of your own creation, as long as it conforms to the specifications expected by the utility. |
|
All |
A new utility is available to update existing Address data rows to bring them into conformity with the current information in the ZIP Code lookup table. |
Tools Corrections
Remember that the descriptions for the following items describes the problem PRIOR to the installation of the corrections as part of the current release.
Posted Date Reported Problem # |
Function |
Database |
Interface |
Description |
4/3/01 6. |
Merge ID |
SQL Server |
Browser |
The Merge Id utility hangs when merging IDs that have Actions with linked Tasks. |
2/2/01 5. |
Deleting Gift or Dues Batch Numbers or Titles |
All |
Browser |
An error may occur if you attempt to delete an existing entry in the Gift Batch Number, Dues Batch Number, or Titles lookup tables, using the small Delete button at the top of the form. |
2/2/01 4. |
Gift Batch Maintenance |
All |
Browser |
When searching for a particular batch entry to display, the system only considers the first six characters entered in the Value text box. It then displays all entries that conform to those six characters. Note: SQL Batch searches are based on all ten characters, but Oracle batch searches are limited to the first six characters. |
12/21/00 3. |
New Group Permissions |
SQL only |
Browser |
When creating a new security group, that group is not automatically granted privileges to the report worktables. |
10/25/00 2. |
Benefit Type |
Oracle only |
Browser |
When an entry from the Benefit Type lookup table is being updated to set the Quid flag equal to 'Y', an error message may be given. |
10/25/00 1. |
Lookup Table Maintenance |
All |
All |
The UserId of the last user to update a lookup table entry is not being displayed. This is the case for Attribute Types for both SQL and Oracle, and the Membership Lookup tables in Oracle. |
Database and System Changes
Interface |
Function |
Description |
All |
Address |
The following fields were added to this data table: addrcass1 |
All |
Chart of Accounts |
The following fields were added to this lookup table: chart_dte1 |
All |
Chart_lookup1 |
These are new lookup tables, which conform to the standard layout for lookup tables. |
All |
Correspondence |
The following fields were added to this data table: corrsolic |
All |
Correspondence_name |
The following fields have been added to this lookup table: table_sol |
All |
Death |
The following fields were added to this data table: deathnotdt |
All |
Dues |
The following field was added to this data table: duesacdprt |
All |
Gifts |
The following field was added to this data table: giftacdprt |
All |
Memory_Definitions |
This system-use table has been added. It is designed to hold user-selected parameters for use by the Summaries or the Years Utilities. |
All |
Name-types |
The following are new, standard entries for this lookup table, created by the installation of Release 7.1: ha	Husband Preferred |
All |
Planned Gifts |
The following field was added to this data table: planpdistr |
All |
Pledge Types |
Two additional standard entries have been added to the Pledge Types lookup table. They are: sm 	Semi-monthly |
All |
Proposal |
The following field was added to this data table: proppdistr |
All |
Relationships |
The following additional standard entries have been added to the Relationship lookup table. bro 	Brother |
All |
The following fields have been added to this system table: report_groups |
|
All |
Report_groups |
This is a new lookup table that conforms to the standard layout for lookup tables. The installation of 7.1 also creates a blank entry in this lookup table. |
All |
Report_servers |
The following fields have been added: report_preview |
All |
Seating Layout |
The following fields have been added: laytblname |
All |
Seating Shapes |
This is a new lookup table that conforms to
the standard layout for lookup tables. It supports the Seating Assignment
component of Events in the Windows interface. All entries are standards
and are created by the installation of 7.1. This lookup table is not available for traditional table maintenance.
|
All |
Table_groups |
The following are new, standard entries for this lookup table, created by the installation of Release 7.1: allprt	All Reports |
Browser |
HTML Templates |
Changes have been made to the following standard HTML templates. act_up.mit |