Millennium Software Home
   

Reported Bugs or Issues

Tracking # 
Level 
Description 
Fixed in Build 
CollapseStatus: Closed
 1VerifiedPrice category maint update mode is not updating the underlying table.20.0.0.14
 2VerifiedAlignment of navigation bars on customer window are displaying too low.20.0.0.14
 3VerifiedFunction menu items on the customer information window are not enabled.20.0.0.15
 4VerifiedPO receiving sessions cannot be unreceived if any serialized items were received.20.0.0.15
 5VerifiedThe stock code field on the vendor codes tab of the vendor information window was not forcing upper case.20.0.0.16
 6VerifiedCard token information not being pulled from card processing plugin for manually entered cards.20.0.0.17
 7W.A.D.Last modified image timestamp is being updated with local time instead of UTC.20.0.0.18
 8VerifiedScheduler window shows events for all resouces after a refresh or upon second open of the window.20.0.0.22
 9VerifiedError dispalyed during conversion regarding unknown field CCUpdateTokenMode. 20.0.0.20
 10VerifiedThe presence of a company or user default BCC was clearing any manually entered BCC value when sending the email.20.0.0.21
 11VerifiedModification of some transaction tax settings is not triggering a recalculation ot the transaxtion tax.20.0.0.21
 12VerifiedDirect import of .xlsx files was prohibitively slow.20.0.0.25
 13VerifiedCard history types not being saved properly. Worldpay plug-in build 20.0.0.8 or newer required for fix.20.0.0.28
 14VerifiedCreating a scheduler event from the customer information window is throwing an AV.20.0.0.28
 15VerifiedEditing existing card on file was displaying improper billing address information.20.0.0.28
 16VerifiedPresence of old signature device plug-in is causing runtime error 216 on Atrex startup.20.0.0.31
 17VerifiedInsufficient rights error during client/server data conversion.20.0.0.31
 18VerifiedPerformance of report criteria windows with stock code category lookup field is significantly slower than v19 across WAN.20.0.0.32
 19VerifiedIf v13 compatibility mode was enabled, v14 through v19 reports were incorrectly having compatibility mode applied.20.0.0.34

Legend: New: New Report - Not yet confirmed
Confirmed: Confirmed issue - Needs correction
Unresolved: Issue uncorrected - Needs further investigation
Corrected: Corrected in source code - Awaiting verification
Verified: Correction verified - Issue Resolved
W.A.D.: Working as designed or unable to reproduce the issue
Deferred: Issue to be addressed at a later time