Blank screen and\or Java console error(s) raised when launching Express (Yellow-Button) Reports based on Crystal formats with no defined\saved parameters.
If any of the custom columns added in previous versions of Millennium (e.g. 7.7) are added to gifts/dues>payment screen layout, Sage Ppayment Solutions pledge (sustainer and pledge) processing fails without error.
Data Examiner hangs with error manually/automatically accepting pending records with a mapped, blank coressnum field.
Modifying a constituent's employment row deletes comments on the constituent's relationship row.
Expected behavior: Comments on the Employee\Employer Relationship record remain unchanged when said constituent's Employment record has been modified.
Reports using check boxes with prompted replies in the report criteria and then deselected as not applicable at run time causes the express report to not display.
When a report is saved without a crystal format, report destination options do not appear after selecting a format at run-time.
Expected behavior: Report destination options should be available after selecting a format at run-time.
Selecting a value from the super lookup java applet window in report criteria causes the report to fail.
Expected behavior: Users should be able to select report criteria values from a java script 'super lookup' applet.
Error generated editing Dues Lookup1 – 6: Error code 207 “Invalid column name 'duestype’.
Millennium Error Message -- Update
UPDATE dues_lookup2 SET table_val = 'test', table_code = 'test', table_type = ' ', table_actv = 'Y', table_agp1 = 67108863.0,...
User creates and saves a custom form (see example below). User sets this custom form as the maintenance default. No problems with date time formats\display after initial data entry (see value for Contact 1: in graphic below)
The Profile Search screen is searching on partial instead of exact value for the Alternate Id fields as the Help files indicate should occur.
Expected behavior: Profile Search would return results on the exact value specified; not on a partial match thereof.
After inserting an Actions\Actions Tasks record that has carriage returns in the text for the Comment field, the carriage returns are not being properly displayed in the Actions Tasks Comment field on the Main Display screen...
Data field Coredate1 does not show in Data Examiner when added via Advanced Data Examiner tool....
User attempts to register a constituent for a specific event; creates and saves a custom form (see example below). Registration Detail screen populates correctly, Guest Detail screen also populates, but note the phone number and e-mail address fields in the graphic below:
Inactive super lookups can be selected on insert and update screens at the time of data entry.
Expected behavior: once a super lookup is marked as inactive it will no longer be available for selection during data entry.
On a joint pledge with credits to additional constituents, the total and balance are incorrect on the pledge credit records after deleting one of the payments.
Expected behavior: Pledge transactions and their corresponding credits will balance after a payment is...
When you run an Express report using a custom format, the thumbnail image used to view the express report does not display.
Expected behavior: Thumbnail placeholder should display next to express report allowing user to click on and view results.
Symptom: Defining basic data system default generates the following error if the chart_of_accounts entry being used in default corebio has more than 65 characters in the name.
Millennium Error Message -- Insert
ORA-06502: PL/SQL: numeric or value error:...
Report parameters stored with the report are not appearing in report option parameters.
Expected behavior: Millennium users should be able to define sorts as they wish.
When a relationship is linked to tracking the linked tracking relationships header is displaying the wrong constituent ID/Name.
Expected behavior: The tracking relationship on the secondary relationship displays the correct constituent header.
A system administrator assigned system administrator privileges to a Millennium user. All the worktables that belonged to the user were deleted.