Unable to run previously functional custom reports after migrating to new IIS Server
Blank screen and\or Java console error(s) raised when launching Express (Yellow-Button) Reports based on Crystal formats with no defined\saved parameters.
Millennium login fails with this error message: "Sorry, you have exceeded the number of login attempts. Your username and IP address have been locked. You will have to contact the system administrator to unlock your account..."
Afterwards, not only is the initial user locked out of...
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.
Recent Reports display does not always accurately reflect (display) the most current report that was either: run, edited or published by specific user.
When you save report criteria as a Report Administrator, the criteria is overwritten for any report that has the same report table name.
Expected behavior: Criteria should not be overwritten for reports with the same worktable name. Report criteria are expected to be...
Criteria not printing if no format specified. Prior versions criteria did print. 1
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.
Two (2) default screens are presented when logged in as a Soft Edit user. This behavior manifests when inserting Attribute, Education, Relation & Tracking rows.
Error ORA-01422 generated when a pledge transaction has more than one credit for other linked transaction and then that pledge transaction is written-off.
Millennium Error Message -- Update
UPDATE gifts_full SET gifteffdat = 'Jul 20, 2011', giftsolic = ' ',...
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...
Millennium user enters a a pledge transaction without a payment schedule. The payment schedule was created manually after the pledge was created. Subsequent edits of this pledge transaction delete the pre-existing payment schedule.
Expected behavior: Millennium users...
Symptom: Running reports on replicated reporting server a second time using an existing worktable results in the following error: The error is "Parameter Check - This table does not exist. Please choose an existing worktable".
- Tools | Profile Lookups | Lookup Tables | Chart of Accounts.
- Select an account, hover over the edit button and choose update.
- Remove the active flag and click update.
- Search ...
When you update a pledge transaction that was initially inserted without a payment schedule and the payment schedule was created manually after insert, the payment schedule is deleted when you update the pledge transaction.
Expected behavior: To be able to successfully...
Users are able to customize their Address Long screen layout form with address utilizations and save them to the maintenance form even though they are already on the maintenance screen layout by default; causing an error to be generated when updating the address record.
When importing a Sustainer Pledge through Data Examiner, the Sustainer Payment Schedule field “susactive” is being set to Inactive and should be Active.
After defining a number parameter in a Crystal format, it will not display properly in the report if run with a 6 digit number or bigger.
Expected behavior: Expects the parameter to display just like it does when it is exported directly from Crystal
If a company search is done on an exact company name that is its own matching entity, the header at the top reads the name of the City of the company, not the matching entity name.
Expected behavior: One would expect to see the correct Matching Entity name.
When you edit the group's default report queue - the default report queue for those users who had the same default queue as the group's will not automatically change to the group's new default report queue until the users record has been updated.
Expected behavior: We...