❑Using the "Bug Fixes" List - Several "bug fixes" have been completed during this update which are shown in the table below:
•Modules with Issues - All of the Program Module(s) and Forms that were Corrected are listed.
•Chapter Links - The Chapter Links are provided for finding the revised instructions, illustrations, and details on the operational and/or usage of those corrections.
•Anomaly (Bug) Fixes - A brief Description of the Issue and the correction is shown, sometimes with additional Chapter Links.
Program Module(s) Affected |
Chapter Links |
Description of the Big Fixes, and/or Anomaly Corrections |
|
|
|
Module(s) with Issue |
Forms Affected |
Starting From 8189 Anomaly (Bug) Fixes |
|
|
|
MKMS STARK |
Some Users were setting the True/False type of Company Settings by entering the appropriate setting ("T", or "F"), and then Pressing the 8 Enter key, rather than Clicking the Update option in these True/False fields, which will appear exit that field and in so doing, the entry seems to disappear. ▪Seeing this, some Users have repeated that process, leaving multiple Ts or Fs in the field which could cause the system to misunderstand what the setting should be. ▪To eliminate this issue, and retroactively solve that problem in any existing entries, the system will now only look at the first character in those True/False fields, and ignore any others. |
|
MKMS STARK |
Several minor issues were corrected on the Calls Report including an error that would display when Report On was Vendors (All or Specific). |
|
MKMS STARK |
The selected sorting order for a List - which, when changed, should have been the new default sorting order for that List - will now also determine how, and which records are displayed (when the User is not in the List) as those Record Movement options (e.g., Begin, Next, Previous, Last) are used on all of those Main Form's Ribbon Menu. |
|
MKMS STARK |
With the Logo tab on the User Options Form now accepting .bmp, .jpg, and .png file formats when Choosing the Company's Logo Image, there were several instances where ".png file formats created an error message when certain reports were printed. ▪To date these reports have been identified and corrected: |
|
a)When Closing a Accounting Period (changing Stage from Open to Close), the program was not asking the User if she/he wanted to "Generate Late Fee Invoices" which it should. b)When reopening a period (changing Stage from Close to Open), the program was asking if the User wanted to "Generate Late Fee Invoices" which it should not do. •The correct functionality has been reimplemented. |
||
|
|
|
The issue where deleting a CSID Zone prevented the User from entering a new CSID Zone has been corrected. |
||
The Event Type field was blank for printed Scheduled Reports records. This is fixed. |
||
When selecting No Answer for an Alarm Signal the Operator could get an Access violation message. This issue has been identified and corrected.
Operators were reporting they were receiving split signals. This issue has been identified and corrected. |
||
Several operational fixes have been applied to the Sale-Purchase Items Form: ▪When changing a Sale-Purchase Item originally identified as an Inventory Item to a Non-Inventory item (by removing that Check mark), the system will now correctly enable the Purchase GL # field to allow a User to select a valid Purchase GL General Ledger Account Number. ▪Identifying a Sale-Purchase Item as an Inventory Item, the system will now inactivate the Purchase GL # field and populate it with the Inventory Account entered for that purpose in the Mandatory Accounts (and/or Re-Declare Accounts) Form. ▪The system will no longer raises the error "Could not convert variant of type (Null) into type (Double)." when editing any field on a Sale-Purchase Items Form where "Retail Price" field was blank. ▪The system will now clear the Purchase GL # field if the Item Type is set to "Sale". ▪The system will now clear the Sale GL # field if the Item Type is set to "Purchase". |
||
The system will now prevent users from changing the Item Type of an item already used if General Ledger System is installed. ▪If the Sale-Purchase Item is found in any invoice, proposal or work order and the item is changed to a type of "Purchase", the program will raise error "You cannot change the "Item Type" to "Purchase" for an item used on Invoices, Proposals or Work Orders." ▪If the Sale-Purchase Item is found in any bill or Purchase Order and the item changed to a type "Sale", the program will raise error "You cannot change the "Item Type" to "Sale" for an item used on Bills or Purchase Orders."
The User would need to create a new Sale-Purchase Item if they wanted to make that change and make the initial item "inactive". ▪The reason for this is that if a Sale-Purchase Item is in use and the item type was changed, the wrong GL Account Numbers would be inserted/updated for that record, throwing the General Ledger System out of balance. |
||
|
|
|
Module(s) with Issue |
Forms Affected |
8200-8202 Anomaly (Bug) Fixes |
Using Outlook® to Email an Invoice from within the Invoices report dialog - accessed from the Reports Menu - presented an error message. This anomaly has been corrected. |
||
The issue where the Start and End Dates enter for the RMR Rate Changes report were not being properly applied to the actual data selection (it was sometimes off by a day) has been corrected. |
||
▪Clicking the Refresh Icon on the Account Approval dialog Ribbon Menu did not do so. This anomaly has been corrected. ▪Converting a Proposal to a Job Costing record from within the Account Approval dialog's Grid did not always work. This anomaly has been corrected. |
||
|
|
Subscriber Form's Reports Menu |
The Central Station option on the Subscriber Form's Reports Menu was not available if the Central Station Monitoring module was not Registered. This anomaly has been corrected. |
|
|
|
The Import Payments dialog for the Regulus/Wells Fargo Import did not allow an Import File to be selected. This anomaly has been corrected. |
||
These issues associated with Closed Periods have been corrected: ▪When AR is closed - No longer able to modify the Sale Date on an Invoice and/or Date Received on Receipts which are in closed period. ▪When AP is closed - No longer able to change the Date Paid on Payments which are in closed period ▪When both AP and AR closed - No long able to change the Date Received on Receipts and Date Paid on Payments which are in a closed period |
||
The issue has been corrected where: the Proposal, Invoice and Bill Forms were in the Edit mode when initially displayed, or were displayed when coming from List View. |
||
|
|
If a Sale-Purchase Item is used on a Bill (it was assigned an Item Type of either Both or Purchase), and then later the Item Type of that Sale-Purchase Item is changed to Sale, when (if) the detail line item on the Bill (which includes that changed Sale-Purchase Item) is Edited, the NetCredit or NetDebit Amount is reset to NULL and so the General Ledger System would become Out-of-Balance. This anomaly has been corrected (prevented). |
|
When the GL Setup Wizard in the General Ledger System has not been executed (i.e., the GL system is not tracking Financial Transactions): 1.Certain Bank Transactions (e.g., Deposits, Payments) were not updating the Bank Account Balance in that General Maintenance Form or the Bank Transaction Register. This anomaly has been corrected. 2.The Refresh (balance) Icon on the Bank Maintenance Form is now disabled. |
||
The Bank Transaction Register dialog will no longer allow: 1.A negative Bank Transfer entry. 2.A Bank Transfer to be saved without the "To" Bank being identified.
▪Previously, when an Employee Payment or an Employee Receipt was recorded, the Balance would not Refresh until the Bank Transaction Register dialog was closed and reopened. This anomaly has been corrected. |
||
▪This issue where the Select Billing Address Icon on the Work Order Form was missing on some versions of MKMS has been corrected. ▪When you Link a new service issue to a previously entered Work Order, the issue where the Salesperson field was not being populated for the new Work Order has been corrected. |
||
1.In certain situations, it was possible in the Review GJ Transactions dialog to save an Out-of-Balance Transaction. Now, if an Out-of-Balance change is attempted, that change will be discarded when a Save is attempted (the original entries will be restored). 2.Also, when reviewing the Review GJ Transactions dialog, entering a Credit & Debit entry in the same Review GJ Transactions line item entry line was possible. That Credit & Debit - single line entry - is now rejected. 3.If a User Retrieved data and then Closed the Review GJ Transactions Form, the error "Error - 141: Table '#tempTran' not found" might be displayed. This issue has been resolved. |
||
|
|
▪The issue with improper data populating within the Sub Info (F2) Form has been resolved. ▪The issue that caused Predefined Messages - defined for use with the Communications Module - to not be sent with via a Manual Contact executed within MKMSCS has been resolved. |
|
|
|
|
Module(s) with Issue |
Forms Affected |
8203 - 8216 Anomaly (Bug) Fixes |
|
|
|
MKMS STARK |
Print Preview (from Grid style Reports) |
If a Print Preview derived from a Grid was actually printed, and that Printed report included a Detail Grid, an "Access Violation" error was presented when that Print Preview Form was closed. This issue has been resolved. |
As a new Recurring Revenue record is entered, if offered the option to Create a Pro-Rated Invoice? as a Suspended or Pro-Rated Invoice is being created: the National Sales Tax is now properly inserted when required. |
||
|
|
Bounced Check records, and the original Receipt record where inconsistently reported on the Accounts Receivable Report. ▪Now, the original Receipt, and the negative Bounced Check record, will be included in the Accounts Receivable Report only until the report's selected As Of Date is equal to, or after the Date the of (negative) Bounced Check record. ▪If the Receipt record and the negative Bounced Receipt record are dated on the same day, neither will be included on the Accounts Receivable Report. |
|
Sometimes, when an Invoice to which a Receipt has been Allocated is a changed (e.g., a Comment added or Note modified), the Balance Due shown at the top of the Invoice Form reverts to the original Gross Amount of that Invoice. The cause of this issue has been identified and corrected. |
||
If the Receipt Form's "List View" is sorted by "Receipt ID" in descending order, when a new Receipt was created and saved, the record displayed jumped to the last record, which was the oldest ReceiptID. ▪This anomaly has been corrected. |
||
Previously a Bank Deposit was able to be recorded with a Receipt Date that was prior to the Receipt Date of the Receipt being deposited. ▪This anomaly has been prevented. |
||
▪Query to insert InvoiceLineItems is malformed when selecting options: a)"Create New Invoice (Against Dealer's Bill Payer)" b)"Create New Invoice (Against Service Bill Payer)" ▪When selecting option "Create Suspended Invoice (Against Service Account)" a system error was displayed: "Error -143: Column 'NationalTaxPercentage' not found" . ▪A better error feedback for any error that occurred has been added and any Query that fails will be written to this report's log file. |
||
The issue where emailing an Invoice using SMTP, the content of the "Enter message for Email Invoices below" box was not being passed as the body of the email (It was being passed as if the system was using Outlook®), has been corrected. |
||
▪When the Hide Inactive Items box was Checked on the Sale-Purchase Items Form, an error occurred intermittently. The cause has been found and eliminated. ▪When a Vendor Filter was applied on the Sale-Purchase Items Form, then an additional Vendor added to that Vendor Filter, a Field ID not found error occurred. This issue has been resolved. |
||
▪When Printing Options and attempting to import a custom report (RTM file), the program raises an "Invalid Format" error and the custom report format is not imported. This issue has been resolved. ▪When pringing using a Custom Report Format, the program raises an "Access Violation" error. This issue has been resolved. |
||
In the Cash Receipts Summary by Month report, when Receipts posted to a Division Group were to be included, an error stating that "There is no data matching your selection criteria" was presented when in fact, there was data. This issue has been corrected. |
||
|
|
|
If a Prospect was identified as Taxable and a Tax Rate Code (and Percentage) was assigned, when a new Recurring Revenue Item for a Proposal was entered: ▪The Tax Rate Code was not inserted. This issue has been corrected. ▪If aa National Sales Tax has been established in the Tax tab of the User Options Form, and the Prospect was identified as Taxable, the National Tax Code was incorrectly set to N (none). This issue has been corrected. |
||
|
|
|
▪MKMS displayed a "List Items Found" message when a Parts List tab's Use box was Checked but the selected item was not recorded in the Inventory/Materials Drop-Down Info Box. This anomaly has been corrected.
▪Priority - Updates to setting the Priority Number have been implemented: a)When a Service Type is assigned to this Quick Work Order entry, the Priority Number is reset to the Priority Number established for that Service Type and b)a Priority Number of 3 will now be properly inserted if no other number is entered. c)The Priority Number may no longer be set to a minus Value. |
||
|
|
|
|
|
Voided Payment records, and the original Payment record where inconsistently reported on the Accounts Payable Report. ▪Now, the original Payment, and the negative Voided Check record, will be included in the Accounts Payable Report only until the report's selected As Of Date is equal to, or after the Date the of (negative) Voided Payment record. ▪If the Payment record and the negative Voided Payment record are dated on the same day, neither will be included on the Accounts Payable Report. |
|
|
|
|
The location of a temporary file for writing and reading Action Plan changes during editing was "hard coded" and so caused problems for some individuals without full Administrator Rights on their PC. ▪This issue has been resolved by placing this temp file in the standard AppData folder: (c:\users\username\AppData\Local\MKMS) |
||
After Voiding a Payment, when an attempt was subsequently made to modify the Date of a Voided Payment record (created when the original Payment was Voided), an erroneous error message "Unable to modify a printed payment" was sometimes displayed. ▪ This issue has been corrected. |
||
a)The Date field on Printed Checks has been expanded to prevent truncating. b)The issue where the Count of the Checks to be Printed was 1 greater than what was actually needed has been corrected. c)When requesting Checks be reprinted, a message that should say "Click on Checks you wish to reprint" is now shown correctly. |
||
An interim version of the Bank Reconciliation dialog could create duplicate Transactions and those duplicates would not be reconciled. ▪This issue has been corrected. |
||
|
|
|
Module(s) with Issue |
Forms Affected |
8217 - 8221 Anomaly (Bug) Fixes |
▪The erroneous error occurring when changing Item Type of a Sale-Purchase Items when the General Ledger System is NOT installed and there is more than 1 Bank defined, the system presents "Error -185 SELECT returns more than one row". This issue has been identified and corrected. ▪After performing a Search, the issue with having to modify an entry twice before it was accepted has been corrected. ▪The cause of the error: "Database is not in insert or edit mode" presented when attempting to enter/modify a Proposal Description was eliminated. |
||
The "Out Of Memory" problem cause by duplicating the Credit Cards accepted message on Statements has been identified and eliminated. |
||
▪The system will no longer allow a Proposal containing a line item with a Zero ("0") Quantity to be Converted to an Invoice. ▪When Converting a Proposal to a Job, the system was not populating the Job's Title field. When a Proposal with a Title entered, is converted to a Job, the Title is now properly converted and displayed on that Job Costing Form. |
||
|
|
|
The issue where for certain Company Logos, the Legacy report format prints correctly, however the Contemporary trims a portion of the image (e.g., the Legacy report Logo width is 3.5 inches, the Contemporary report Logo width is 2.375 inches). The system now allows both logos with a width up to 3.5 inches. |
||
|
|
|
Adding and/or Modifying the Comments on Credits Memos , Invoices,or Bills which are in a Paid status or fully Allocated Credit Notes, the Balance Due was reverting to the Gross Amount on Invoice or Bill, instead of the balance due remaining to zero dollars. The cause of thsi issue has been identified and corrected. |
||
|
|
|
The issue on the Inventory Worksheet Report when the "Order By" is selected as Location or Warehouse and "Exclude Zeros" is Checked, and the report displays Inventory Items where Available On Hand and Committed On Hand is zero (which should not be listed) has been corrected. |
||
|
|
|
When Starting a New Work Order, sometimes the Primary CSID was not properly populated in that field (and the Drop-Down Selection List was empty). This CSID field is now populated correctly. |
||
|
|
|
An anomaly which disabled the Navigation options on the Ribbon Menu of a Bills Form (usually after reordering the Grid of a List View) has been corrected. |
||
|
|
|
The anomaly where the Advanced tab on the Alarm Stack Maintenance Form displayed as the default selection has been reset to Classic tab. |
||
The issue where some of the UL Categories - when displayed on the Sub Info (F2) Form - showed the internal label name rather than the data (e.g., lblULGrade versus UL Mercantile) has been corrected. |
||
The number of Priority Levels had been expanded to 20 in a prior version of MKMSCS, but the Alert Sounds for Alarm Signals presented with a the Priority greater than 9 were not heard. ▪This anomaly has now been corrected, and specific Sounds for Priority Levels 10 - 20 may be identified in the Sounds tab within the Central Station Options tab of the User Options Form |
||
|
|
|
MKMS STARK |
An intermittent "System is Out Of Balance" message shown at Login and caused by a rounding error has been corrected. |
|
MKMS STARK |
Various Reports |
Reports embedded in the application MKMS.exe - When clicking on any button in the top bar causes the MKMS application to log out. ▪This has been corrected. |
|
|
|
Module(s) with Issue |
Forms Affected |
Through 8228 Anomaly (Bug) Fixes |
|
|
|
The internal General Ledger calculations for Earned & Deferred Revenue have been updated: ▪Post Earned Revenue Process - Fixed process to now really use Cycle Starting Date (which is identified in the Billing Cycle record) to determine when Revenue is Earned.. |
||
|
|
Payments - When a Payment is Allocated and the allocation screen is closed, sometimes the "Left To Allocate" Value was not being updated properly. ▪This was a refresh issue which has been fixed. |
|
After Voiding a Payment made with a Credit Card (see the "Paying a Bill using the Credit Card Pay option on that Bills Form" discussion in the Payments chapter) the associated Bill seemed to vanish. ▪This was also a refresh issue which has been fixed. |
||
|
|
|
Module(s) with Issue |
Forms Affected |
8229 - 8231 Anomaly (Bug) Fixes |
|
|
|
MKS Auto Billing |
Run Auto Billing |
This issue where the 1 Month Discount for Annual Payment was recorded as a Positive (+) versus a Negative (-) Value has been corrected in the MKS Auto Billing application. |
|
|
|
The issue where MKMS might allow a Receipt entry to be saved when certain required data was not entered, has been resolved.
A Bounced Receipt record's Receipt Information column will have a (BOUNCED)Original Receipt message inserted. ▪This original Receipt record may no longer be modified except the Date Received and Deposited On Date can be modified as long as both are on or after the original Bounced Receipt Date when is was Deposited. |
||
The misspelling of the word "Acquired" on the Attrition Types Form has been corrected. |
||
When the Tax Status on the Tax tab of the User Options is set to Wholly Tax Exempt or Local Tax Only, then when a new Recurring Revenue record is created, National Tax should be internally set to N instead of 1. ▪This is now the case. |
||
The anomaly where Recurring Services where affecting the Recurring Revenue (Audit Report) has been corrected. |
||
The Refresh (timing) issue with the Subscribers Form - History and the Prospects Form - History has been resolved. |
||
|
|
|
When re--sizing the Form the Bank Reconciliation History section could be moved up on top of the Bank Maintenance fields above that Grid. ▪This Bank Maintenance form scrolling anomaly has been corrected. |
||
|
|
|
Some Users experienced an issue with the view of the Starting and Ending Date fields of the Taxes Billed report. ▪This anomaly has been corrected. |
||
|
|
|
On the Day View of the Technician Scheduling Form, an Appointment may be set by Dragging it from Pending Wort Orders Grid to the appropriate Time Slot on a selected Technician's schedule. ▪Using the Radial Right Click Menu, the User may then open the Work Order Form associated with that Technician's Appointment. ▪However, once that Work Order is displayed, if the User starts a new Work Order, the Salesman of record (which existed on the original Work Order) was not being entered in the new Work Order record.
The cause of the problem has been identified and corrected.. |
||
When Service Request Forms are printed, if the Work Order Type (see the Entering a Work Order chapter) is an Installation Order, the Work Order with Pages 2 to nn containing the Parts List should be printed. ▪When more than 23 items were defined on the Parts List tab of a Work Order, forcing a page 3 (and beyond), some Parts List items were skipped in those subsequent pages. ▪The cause of the problem has been identified and corrected.. |
||
When Chaining one Work Order to another, the system inserted an empty line at the top of the Description of the Conditions Report.. ▪The cause of the problem has been identified and corrected.. |
||
|
|
An issue where: a)An Inventory Item and the Warehouse from which it was taken was recorded on a Work Order in the Inventory/Material Info Box; b)Then the Warehouse from which it was taken was changed (corrected) to a different Warehouse; c)But the Inventory Counts were not properly updated (e.g., added back to the original Warehouse and deducted from the newly assigned Warehouse) has been identified ▪The cause of the problem has been identified and corrected.. |
|
|
|
|
Inventory Items were not included in the Inventory Reorder Repo when the "Include Parts List" option was Checked and the User answered "No" to the "Skip items with reorder of 0" pop-up question. Previously, the internal Query for this report was always using the Available On Hand Quantity in the Warehouse Inventory Form. ▪It now also includes any Parts List Quantities from the Item List sub-tab of the Inventory tab on the Job Costing Form. |
||
|
|
|
The issue where a Group ID was entered in the General Ledger Groups Form with a trailing space causing an irregularity in certain Financial Statements & Reports has been identified. With the installation of the 5.1.8229 Version of MKMS any cases where this data entry problem existed were corrected automatically. ▪Do not add a space at the end of a Group ID in the General Ledger Groups Form. |
||
After Login, the system (using the data in the General Ledger Checkpoints dialog) could erroneously report a "System Out of Balance" condition. This issue has been corrected. |
||
MKMSCS |
|
|
The cause of an erroneous "Data set not in edit or insert mode" error in the CSID Zones tab on the Subscriber Panels section has been found and removed. |
||
The issue where the List option on the Panel Zones tab was disabled once it was selected by the User has been corrected. ▪Now when the List option is selected all other options on the Ribbon Menu are disable until the List option is chosen again to return the User to the record editing view of the Panel Zones Form |
||
When an Active Temp Note was in effect (e.g., a Temporary Note attached to a Subscriber's record - with a starting and ending date and time within which the Temporary Note will be Active) - the Operator handling the Signal from that Subscriber and/or any other User will be reminded/notified of this special situation), the ACTIVE TEMP NOTES message was shown with a Down Arrow ˆ on the Information bar on the Subscribers Form. but sometimes displayed incorrectly because of a conflict with the recently added CSID field with its Drop-Down Selection List ▪This issue has been identified and corrected. |
||
The cause of an occasional data entry glitch in the People To Call tab in the Subscriber Panels section has been identified and corrected. |
||
▪The issue where the bottom of the Temp Notes tab on the Subscriber Panels section was not shown has been corrected. ▪The issue where the Start Date field was cut off, and the End Date field was missing on the Temp Notes sub-tab on the Dealers Form has been corrected. |
||
The default From Time and To Time fields have been reset to be 8:00AM to 8:00PM when User Specified Time button is first selected, but may be changed as needed. |
||
|
|
While Signal Processing, an Operator was not able to access Alarm Signals received from Subscribers who were assigned to a newly created Alarm (Processing) Group. ▪This issue has been identified and corrected. |
|
While Signal Processing, if an Operator attempted to cut and paste a Temp Note for a "live" Alarm Signal, it erased it. ▪This issue has been identified and corrected. |
||
|
|
|
Module(s) with Issue |
Forms Affected |
8232 - 8234 Anomaly (Bug) Fixes |
|
|
|
The documentation for the Understanding Earned & Deferred Revenue and Post Earned Revenue chapters, plus the related Billing Cycles, Company Settings, Run Automatic Billing and Deferred Revenue Setup chapters have all been rewritten; and the Deferred Revenue (Daily View), Deferred Revenue, and Earned Revenue by Month report chapters have also been updated - all based on the revised methodology used to calculate Earned & Deferred Revenues . |
||
The Refresh issue within the Related Accounts tab within the History Grid on the Subscribers Form has been identified and corrected. |
||
The situation where the Right or Left frame of the Subscribers Form could Dragged to completely hide all Subscriber data has been corrected (note that the bottom frame may still be moved horizontally to control how much of the bottom portion of the Subscribers Form is visible. |
||
The anomaly where the CSID field was not being re-displayed on the Browse View of the Subscribers Form if a User starts to add a new Subscriber record, but then cancels (aborts) the edit without Saving the record has been identified and corrected. |
||
When creating a credit memo, program raised an "Error -157: Cannot convert '--01' to timestamp" ▪The cause of this problem has been identified and corrected. |
||
When Deferred Revenue is Active, the spelling in the error message presented when a User attempted to Modify an Existing Invoice for Recurring Revenue has corrected; and the affected Invoice Number has been added to that error message. |
||
This issue where the "Click to View Package Info" field on a Proposal did not display the expected Drop-Down Info Box has been identified. A User must Click the Down Arrow within that field to be able to see that information. |
||
1)The issue where the Billing Year field was not displayed as Mandatory - when Defining Open Term Recurring Revenue with a selected Frequency of Bi-annual - has been fixed. 2)The issue where Fixed was chosen as the Billing Term when Defining Fixed Term Recurring Revenue but the Payment and Balance fields were not displayed as Mandatory fields has been fixed. |
||
When you Post Earned Revenue for a negative Recurring Revenue detail line item it will now correctly post these Transaction File entries: a)The Deferred Revenue Liability Account is Credited (increased) by the Value of the Recurring Revenue that was Un-Earned during the Accounting Period b)The (Revenue) Sales Account assigned to the Recurring Revenue Item is Debited (decreased) by the Value of the Recurring Revenue that was Un-Earned during the Accounting Period c)The Current Earnings Equity Account (a Mandatory Account) is Debited (decreased) by the Value of the Recurring Revenue that was Un-Earned during the Accounting Period d)The Earnings Posting Expense Account (a Mandatory Account) is Credited (decreased) by the Value of the Recurring Revenue that was Un-Earned during the Accounting Period |
||
The format of a Printed Proposal has been updated to better position and display the Prospect's or Subscriber's Name and Address information, and your Company's Logo when appropriate. |
||
|
|
|
When the Search by Work Order function was used, and/or when Starting a new Work Order, theSalesman field is not being populated. This anomaly has been fixed. |
||
|
|
|
While Processing Alarm Signals, the issue where the Copy To option was not available in the Temp Notes dialog has been fixed. |
||
The issue where the Dealer Pop-Up Info Box on the Signal Processing screen was showing multiple Dealers has been fixed. |
||
The issue where the Operator was not able to access Alarm Signals from a newly assigned Alarm (Processing) Group has been fixed. |
||
The issue where Alarm Signals remained in an Alert status when SPA resets Signals after alerting them for 3 minutes has been corrected. |
||
|
|
|
The Xml MicroKey Receiver Driver has a new /NoACKNAK "Driver Option" which would be entered in the Driver Option column located on the IP Port tab in the SPA Setup Form ▪It shuts off the ACK/NAK response normally sent from the Xml MicroKey Driver. ▪It uses the new (soon to be available) Company Settings option named PulseUnattendedRelay which must be defined in Company Settings table (see below) ▪Because of this, it is important to Check the Supervise Receivers field's box found on the System tab in the SPA Setup Form when you implement this /NoACKNAK option. |
||
There is a new (available) Company Settings option named PulseUnattendedRelay which must be defined in Company Settings table and when used, is set to True ("T"). ▪When PulseUnattendedRelay is set to True ("T"), SPA will pulse the designated Unattended Alarms relay for 1 second when one or more new (30 seconds of age or less) A126 - Unattended Alarms Activation records are detected in the Alarm History table. oThere is a 60 second anti-race condition timer that limits the maximum Unattended Alarms Activation relay pulse rate to once per minute. oThis implies that there would have to be new A126 - Unattended Alarms Activation - records in Alarm History after the initial 1 minute period. ▪Setting the PulseUnattendedRelay option to False ("F") causes the Unattended Alarms (see User Options > Central Station Options > Alerts tab > Unattended Alarms) relay to remain on until all the A126 - Unattended Alarms Activation alarm records age to 30 seconds or older, which is the original behavior. oTherefore, PulseUnattendedRelay defaults to False ("F") if you do not add it to the Company Settings table. |
||
|
|
|
Module(s) with Issue |
Forms Affected |
8235 - 8237 Anomaly (Bug) Fixes |
|
|
|
The "Comments" field in the Customer Deposit Report Grid was displayed incorrectly (shown as an RTF field rather than a standard Text field). ▪This issue has been corrected. |
||
When defining an Open Term or Fixed Term item for Recurring Revenue, if the Pay Type is set to Custom Pay and a Contract was identified, an erroneous error message reported that the field ExpiryDate was not found. ▪This issue has been corrected. |
||
In the Ledger Card report a few anomalies were fixed: Traditional format - If the Sale Item's Description is too long it goes off the page. Contemporary format - If the Sale Item's Description is too long it goes off the page. ▪Now it will word-wrap the Sale Item's Description, if necessary when displaying/printing both of those formats, and the format which reports Multinational Tax. |
||
The "Comments" field in the Receipts Search Grid was displayed incorrectly (shown as an RTF field rather than a standard Text field). ▪This issue has been corrected. |
||
|
|
|
When the DeferRecurringRevenue option is set to True ("T") and the General Ledger System is Activated, your Company's Earned and Deferred Revenues are tracked for each Recurring Revenue Detail Line Item on those Invoices created within the Accounts Receivable (and are recorded in the General Ledger System).
a)When Ending a Recurring Revenue item under these conditions, the system inserted incorrect information in the Transaction File including the Description field showing "Cancel RR - Invoice # nnnn" , but inserting the wrong Invoice Number, and the DocumentID field having the wrong Invoice Number. ▪This issue was resolved by modifying the Query so only records where EarnedAmount <> Nett and CreditNote <> 'T' where retrieved.
b)If you have run Auto Billing for the Month and Billing Cycle of the Recurring Revenue record you are trying to delete under these conditions, the system will now properly raise an error message which is 'Recurring Revenue ID (RRID#) cannot be deleted. The recurring revenue has been used. Please set End Date.'
c)When Ending a Recurring Revenue item under these conditions, the system will now check what the maximum Auto Billing Month and Year is for that Recurring Revenue record and raise an error if the End Date is equal to or less than that maximum Month and Year date. ▪The message is 'You have already run the auto bill process for [max auto bill month and year]. Please select a month after this date.' |
||
|
|
|
The Item List sub-tab within the Inventory Tab of the Job Costing Form had allowed the "Order Inventory", "Use Inventory", "Reserve Inventory", and "Print Parts List" options to remain active while a line item was being added or modified. This caused the system to become unstable under certain circumstances. ▪This issue has been resolved by disabling these options while actively in any Edit Mode. |
||
|
|
|
An intermittent Refresh issue during data entry on the Medical Information Form as been identified and corrected. |
||
Pending Signals - Pending Signals are those Alarm and Event Signals that have not yet been acknowledged by an Operator. Although the available number of Priority Levels is now 20 and all 20 Priority Levels lines were listed on the Docking Options, the number of those Signals with a Priority Level above than 10 were not being included in this list. ▪The cause of this problem has been identified and corrected. |
||
When accessing the list of pass codes using the "Verify Passwords" button on the Sub Info (F2) Form, the Pass Codes For... dialog is displayed where All Contacts - those in addition to the People To Call - if configured (e.g., Dealer Call List, Alternate Call List) were not being listed. When the list of pass codes was access using the "Verify Passwords" Icon on the Signal Processing Form, they would all be listed correctly. ▪The cause of this problem has been identified and corrected. |
||
|
|
|
Module(s) with Issue |
Forms Affected |
8238 - 8239 Anomaly (Bug) Fixes |
|
|
|
The Search Icon was missing on both the Prospect's and Subscriber's Referrals Form. ▪This anomaly has been identified and corrected. |
||
The system would incorrectly show an error message stating "You must enter a value for field(s): 'Terms'", but the "Terms" field was not visible in the Receivables Section of the Edit View on the Subscribers Form, so the User could not save any changes. This anomaly has been fixed as follows. a)When Company Setting "UseSubscriberTerms" option is set to False ('F'), the system will use global Terms set in the Company Options - General tab of the User Options Form as the Subscriber's Terms (and not check for this field). b)When Company Setting "UseSubscriberTerms" option is set to True ('T'), the system will display a Terms field in the Receivables Section of the Edit View on the Subscribers Form so the User may make this entry. |
||
While in the Subscribers Form: Edit View, two Users could modify the same Subscriber record at the same time. The cause of this issue has been corrected by implementing record locks once a User has started Editing a record.
▪If a User attempts to modify an existing Subscriber's record while another User has already started doing the same, an error message will now be displayed:
Record is locked by user XYZ (abc)
a)OK - Click OK to continue, and the modification made by the second User will be canceled. b)Once the first User has completed and Saved their entry, the second User may then proceed with their changes.
When accessing the General section on the Subscribers Form: Edit View, the Scroll function was not working properly so the User has difficulty in looking through all of the data without specifically choosing one of the other viewing options (e.g., Receivables, Auto Draft, Service, etc.), ▪The cause of this anomaly has been identified and corrected.. |
||
From the Address Configuration Section in the Edit View on the Subscribers Form when the User Clicks on the Ellipse to open the Addresses Form an error message stating: "Name" must have a value was being displayed . ▪The cause of this anomaly has been identified and corrected.
The issue where a specific Address could not be deleted in the Addresses Form has been corrected. |
||
After the Late Fee Generation process finished, the Form closed immediately, thereby not giving the User the view of the Summary Total and the list of the Subscribers who was Invoiced for those Late Fees. ▪The cause of this anomaly has been identified and corrected.. |
||
The Recurring Revenue Breakdown report's Grand Total Amount was being doubled on the printed copy of the report, but the Grand Total Amount was correct when the report was displayed on the screen. ▪This anomaly has been identified and corrected. |
||
1)When crediting an Invoice that has negative and positive Detail Line Items and a negative Detail Line Item is processed first, the system raised error "--01 cannot be converted to timestamp" This was a random issue since there was no way to dictate the order in which the Detail Line Items will be credited. ▪The cause of this issue was identified and resolved by Modifying the Query to set the order by Nett Amount in descending order to guarantee that any positive Detail Line Items are processed first, and re-setting the Credit Note field to true on the new Invoice (i.e, .Credit Note).
2)When creating a Credit Note and the Invoice had a Detail Line Item with a negative Amount, the system was setting the NetCredit Value to the Deferred Revenue Account for the new Credit Note record, but should have set the NetCredit Value to the Sales Account. ▪The cause of this issue was also identified and corrected.
3) For Credit Notes (for Invoices) in Open Accounting Period, the system would improperly change the Balance Due. This was happening when an Invoice was printed; and also during the event that recalculated Invoices so the Header Grand Total matched the sum of the Detail Line Item totals. ▪The system should have (will now) set the Balance Due of a Credit Notes as the Gross plus the Amount Allocated. |
||
There were many cases where a User had set the order in a List View, expecting it to remain in that order when viewing the Receipts data in the Record Editing View as well as the List View. This was not always the case. ▪The system will now store the Users sort field instructions in the internal User Settings table. |
||
The Bounce Icon on a Receipt record created for a Customer Deposit, if that Customer Deposit has been Reconciled, will now be Disabled. |
||
|
|
If the Sale-Purchase Item selected for a Proposal has the "Proposal Description" field populated, the system properly populates the Notes field for that Proposal Line Item with that Proposal Description. However, when the Proposal is Converted to an Invoice, Job Costing record, or a Installation Order (i.e., Work Order), the Invoice Line Item with that Notes field displays the Proposal Description with its rich text formatting. ▪The cause of this anomaly has been identified and corrected. |
|
|
|
Because the system was bringing an Invoice to the report and to the earned recurring revenue process twice if an Invoice was Allocated to a Credit Memo and that Credit Memo was Allocated more than once: the Deferred Revenue Report, Deferred Revenue Setup Wizard, Post Earned Revenue process and Earned Revenue by Month reports' queries had to be modified so the Join To the ReceiptAllocation table query would only bring 1 instance of the Invoice by adding a "distinct" clause to that Join To statement. |
|
For General Ledger System Users - If there are any records in the Suspended Invoicing Section of any Recurring Revenue items, during this Deferred Revenue Set Up process, those records will now be managed as a standard Sale (they will be assigned to the General Ledger Account associated with its Sale-Purchase Item ) - not as a deferred Recurring Revenue item. Why? 1)The system does not know exactly when the Suspended Invoice item will be added to a future Invoice; 2)Suspended Invoice items are ignored on the Earned and/or Deferred Recurring Revenue related reports; 3)They are also ignored during the "Post Earned Revenues" process for reason # 1).
▪Therefore it does the safe thing and assumes these Suspended Invoice items are immediately Earned. |
||
User was unable to set the Start Date information for an Open Term and/or Fixed Term entry on the Recurring Revenue Form because the special Drop Down Year & Month selection dialog was not displaying the OK / Cancel control to allow editing. ▪The cause of this anomaly has been identified and corrected. |
||
If the DeferRecurringRevenue option is set to True ("T") in Company Settings, the system was incorrectly setting NetDebit to a General Ledger System Sales Account if Recurring Revenue item's monthly Billed Amount was a negative Value. ▪The cause of this anomaly has been identified and corrected. |
||
The cause of this issue where once a Division Code was entered in the Average Recurring Revenue Report dialog, if entered in error it could not be removed, has been resolved. |
||
When Emailing a batch of Invoices, the Email process could fail. ▪The cause of this anomaly has been identified and corrected..
When attempting to Print Invoices dated within a Closed Period, the system would present the error: "Period is closed to all edits" and sometimes this would also happen when closing the specific Invoice Form. ▪The cause of this issue has been identified and corrected.
When Taxing Authorities have implemented Sales Tax Percentage Rates with up to three (3) Decimal Places, a Company Settings to support Charging and Collecting this type of Sales Tax was implemented. Since implementing the support for Sales Taxes with up to three (3) Decimal Places, the Print Invoices process was much slower. ▪The cause of this issue has also been identified and corrected. |
||
Modifying the Retail Price field's Value of a Sale-Purchase Items did not update any associated Proposal Package record. ▪The cause of this issue has been corrected with the new UpdatePackagePrices option in Company Settings.
To Automatically Update the Sale-Purchase Item's Price in a Proposal Package when an associated Sale-Purchase Item's Retail Price field is modified in the Sale-Purchase Items Form: ▪Set the UpdatePackagePrices option in Company Settings to True ("T") - which is the initial default setting. ▪Setting the UpdatePackagePrices option in Company Settings to False ("F") will turn off that Automatic Price Update feature. |
||
When an Insurance record was being printed as an Alarm Certificate, the system sometimes presented the error "JPEG error #53". ▪The cause of this issue has been identified and corrected.
The issue where the Logo on the Alarm Certificate report was being cut off has also been corrected. |
||
When Auto Billing Recurring Revenue the system would show a screen with an error message stating "Price and Quantity cannot both be negative" and the creation of that Recurring Revenue Invoice fails, then the system displays a Form with a list of the Invoices that were not able to be generated along with that same "Price and Quantity cannot both be negative" error message as the reason. ▪This was caused by the improper entry of the One Month Free for Annual Payment feature. A system trap for an incorrect entry of this type has been instituted. |
||
When modifying or adding to the Comments field on a Credit Note, if there was an Invoice Number for that Credit Note and there was a Receipt ID that matches that Credit Note's Invoice Number, the system would calculate the Balance Due of the Credit Note as: Gross Amount of the Credit Note minus the Amount that was Allocated for the Receipt ID, which of course is wrong. ▪The cause of this issue has been identified and corrected. |
||
Canada Tax - By default, the CanadaTax option is set to False ("F") in the Company Settings Form ▪Setting the CanadaTax option to True ("T") enables the specialized Goods & Services Tax tracking system (e.g., PST/GST/HST) for Companies who are required to pay that type of sale tax in Canada
When the CanadaTax option to True ("T"), the system support these options as well: 1)3 Digits Tax - will activate this Three Decimal Places Sales Tax feature in the Tax Rates Form. 2)Show Tax And Total Per Line Item Report - will add support on Reports for Charging and Collecting this type of Sales Tax. 3)Show Tax And Total Per Line Item Screen - provides a Totals information box with Net, Tax, and Gross Amounts at the bottom of the Invoice. |
||
|
|
|
The system was updating Warehouse and Inventory item Counts when an Invoice created from a Work Order had a negative Quantity assigned to an Inventory item However, this is already done as part of the Invoicing for a Job Task and/or when Completing a Work Order. ▪This duplicate process has been eliminated. |
||
|
|
|
When 2 Users had the same Proposal open at the same time, each User was able to Convert the Proposal. ▪The cause of this issue has been identified and corrected by Implementing record locks.
A User was able to add a Proposal Package to a Subscriber's Proposal which had already been Converted to an Invoice. a)The system did raise the error "Cannot modify a proposal that has been converted." but the Detail Line Items for that Proposal Package were still added to the Converted Proposal. and subsequently the User could not delete those Detail Line Items. b)That same error message was being presented when a User Clicked on multiple fields in the Proposal Form because of an unexpected record locking issue. ▪The cause of these issues have been identified and corrected. |
||
Header and Footer Options for Proposals - If the User empties the Header by deleting the whole text, the system does not clear (NULL) the field which was causing those Printed Proposals to show an empty page. ▪Modified the Rich Text Edit component for the Header so when the field is emptied and User saves changes, the field is set to NULL. |
||
The issue in the Tax Information section for Prospects section of the Edit View of the Prospects Form where a Tax Rate ID set up with Multiple Tax Rates was selected, then a Tax Code greater than 1 was chosen, which resulted in the Tax Rate field being populated incorrectly. ▪The cause of this issue has been identified and corrected. |
||
|
|
When the "UseSubscriberTerms" option in Company Settings is set to True ("T"), it should require the Convert a Prospect to Subscriber Process to get the payment Terms your Company will offer to that newly created Subscriber. ▪It now does so. |
|
|
|
|
The issue where the Planner View Active Start and End Time Range in the Technician Scheduling Form could not be modified, has now been corrected. ▪The Planner View Active Schedule Time Range may be set in hourly increments (e.g., 7am - 8pm,, 6am - 7pm, etc.) |
||
|
|
It was reported that when trying to Print a Work Order after I Emailed it, the User could not get it to print. They had to close the Print Service Request Forms dialog and then re-open it, then select the Print option again to get it to work. ▪The cause of this issue has been identified and corrected. |
|
|
|
If an Employee was Terminated, existing Work Orders - when viewed after that termination occurred - would display a blank field when that Technician or Sales Person who was previously assigned to that Work Order was subsequently was terminated. This situation also occurred when a Technician Activity record, an Inventory/Materials record, Labor Cost record, or Scheduling record contained a terminated Employee. ▪Now the Employee information - even after termination - is preserved. |
|
User was unable to set the Start Date nor End Date information on the Recurring Service Setup Form because the special Drop Down Year & Month selection dialogs was not displaying the OK / Cancel control to allow editing. ▪The cause of this anomaly has been identified and corrected. |
||
|
|
The Priority level of a Work Order listed in the Work Order Invoicing/Review Form could be re-set to a value that was less than 1 (e.g., 0, -1, -2, etc..). ▪The cause of this issue has been corrected.
Two Users working in the Work Order Invoicing/Review Form could simultaneously Edit the same Work Order. ▪The cause of this issue has been identified and corrected by Implementing record locks. |
|
|
|
|
The issue where a General Journal Entry associated with a Vendor was reported incorrectly on that Vendor's Ledger Card - has been identified and corrected. |
||
If a Sale-Purchase Item has a General Ledger Account Number (GL Number) assigned to the Purchase GL # field in the Sale-Purchase Item Form and that GL Number exists in the Bank table (which stores both Bank and Credit Card information), the system would raise the error: You cannot change the "Purchase GL # or "Item Type" for an item associated to a Credit Card. ▪This error will now only be raised when that GL Number in the bank table is assigned to a Credit Card but not to a Bank.
The system will n o longer all a Sale-Purchase Item to be deleted if it is in use by a Credit Card record. |
||
In the Payments Form's List View, the Order for Column Name selected in that Grid should be the order in which Payment records are displayed in the Payments Form's Record Editing View when using the record Navigation Menu options, but they were not. ▪The cause of this issue has been identified and corrected.
The system raises error "Cannot focus an invisible or disabled component" if the first record on the Payments Form is a Hand Check and it is Voided. ▪The cause for this error has also been identified and the problem corrected. |
||
The system raises error: "Unable to Print Checks. Check printing failed with error: QrywSetCheckNo: Cannot perform this operation on a closed dataset" when printing a Refund Check which is in a Closed Accounting Period. ▪The cause of this anomaly has been identified and corrected. |
||
▪When the Recurring Purchase record is identified as a Fixed Term item, the system will now correctly display the Gross Balance Amount. ▪When the Recurring Purchase record is identified as an Open Term item, the system will now correctly hide both the Number of Repayments and the Gross Balance fields. |
||
|
|
The Purchase Orders Form's User-Interface was not displaying properly. ▪The cause for this anomaly has also been identified and the problem corrected |
|
The issue where the Search by Purchase Order function was not always displaying the correct Purchase Order has been identified and corrected. |
||
When using the Bank Transfer option within the Edit/Add Transaction Menu to transfer Monies from one Bank account directly to another Bank account, Inactive Banks were included in the list of Banks to which Monies could be Transferred. ▪This ability was obviously incorrect and so a modification was made to prevent this from happening in the future. |
||
When modifying or adding to the Comments field on a Credit Note, if the Bill ID for that Credit Note matched a Payment ID, the system would calculate the Balance Due of the Credit Note as: Gross Amount of the Credit Note minus the Amount that was Allocated for the Payment ID, which of course is wrong. ▪The cause of this issue has been identified and corrected. |
||
Previously, If a User entered a negative Bank Fee using the Edit/Add Transaction option in the Bank Transaction Register, that Amount was listed as positive Value in the Payments section of the Bank Reconciliation Form. ▪It should have been (and now is) listed as positive Value in the Deposits section. |
||
|
|
|
|
|
|
When the Warehouse Form is opened and a new Warehouse record is created, then the Multi-Item Transfer Icon is chosen and the required data entry is competed: a)Once the Transfer Icon is selected, the system raised the error: "Transfer Failed. Error -195: Column 'ToOldQuantityTotal' in table 'InventoryTransfer' cannot be NULL (23502)" b)This only occurred when the Inventory Tracking/Job Costing System's internal ITJCIsInstalled option in Company Setting is set to False ("F") meaning that the Job Costing and Inventory Tracking Setup Wizard has not yet been run successfully. ▪The cause for this error has been identified and the problem corrected. |
||
When Calculating the Average Item Cost - the system raises an error when clicking on the Update Accounts option "Error -142: Correlation Name 'old_name' not found" ▪The cause for this error has been identified and the problem corrected. |
||
|
|
An issue where: a)An Inventory Item and the Warehouse from which it was taken was recorded on a Work Order in the Inventory/Material Info Box; b)Then the Warehouse from which it was taken was changed (corrected) to a different Warehouse; c)But the Inventory Counts were not properly updated (e.g., added back to the original Warehouse and deducted from the newly assigned Warehouse) has been identified ▪The cause of the problem has been identified and corrected.. |
|
|
|
|
The system was showing in Balance, but numbers did not match by $0.01 in some instances (because of an internal rounding error). The Total columns are now being formatted as Currency to allow the Totals to be displayed as the same currency value number. |
||
a)If a section within the Income Statement had no data to report for the selected Dates, a "Division by Zero" error was displayed (could happen for both Sales and Expenses). b)If the Show YTD option was Checked the system did not apply a One Division or One Department selection, but instead, included all Divisions and/or Departments on the Income Statement. ▪The causes for both of these issues has been identified and corrected. |
||
▪The issue where a Percentage Value that was exceptionally small or very large was displayed a "INF" has been corrected. ▪The system will now save the last setting for the Group by GL Account Check Box display this as the default until the User changes it. |
||
The system was reporting an In-Balance case but showing a $0.01 difference on the Trial Balance report. ▪This anomaly has been located and corrected. |
||
Modifying a General Journal Transaction Set in the Review GJ Transactions Form: ▪It was discovered that a User was able to change a Transaction Date to a Date within a Closed Period. 1)Therefore, now the GL#, Division, Department, Description Value of the Debit or Credit entry, the Auto Reconcile, and/or the Owner (Subscriber or Vendor), Job ID and/or Job Category may be modified. 2)However, the Date of Transaction may not be modified. |
||
1)In the Grid Detail section of the Review GJ Transactions dialog, when a User clears the Subscriber, Vendor or Job ID field, then attempts to change the Date of Transaction a madExcept error is displayed as "List Index out of bounds(0)" and if the User chooses the Continue option, the system displays another error as "RecordIndex out of range" and MKMS must be closed. 2)When a General Journal Entry is created with a Job ID and SubContract as the Job Category and later reviewed in the Review GJ Transactions dialog, when a User attempts to modify the Job Category to any other Job Category an error is displayed as "Table 'JobSubContracts' not found (42W33)" ▪These two issues have been identified and corrected. |
||
The issue where a Job Category could be identified in a General Journal Entry without first associating it with a Job Costing record's Job ID has been identified and corrected. A Job Costing Category cannot - and should not - be identified in a General Journal Entry unless a Job ID has been selected. ▪Now the Job Category field is inactive until a Job ID has been entered. |
||
In a Job Costing record, it was possible to modify the Hours for a Labor item which had originated from a General Journal Entry ▪The cause of this issue has been identified and corrected. |
||
When changing the Quantity of an Item Item previously entered in the Inventory/Materials Drop Down Info Box of a Work Order that is Not an Inventory Item, the system might post to the General Ledger's Inventory, COGS and Net Income Accounts. ▪Now, this will only occur when the Item is an Inventory Item. |
||
|
|
|
The issue has been identified and corrected where, once a new Vehicle Information record was defined and saved, the record pointer would jump to a different record. ▪In so doing, because the root cause was identified, this type of issue - which may have been occurring in other General Maintenance entry Forms - has also been corrected! |
||
|
|
|
The system raised an "Invalid Date" error when modifying the Start and/or End Date of a Temp Note accessed within the Edit View - Monitoring tab ▪The cause of this issue has been identified and corrected. |
||
The system will no longer raises the error "'Control' has no parent window." when editing a Telephone Number number within the People To Call Form |
||
1)The issue where the Select CSID dialog on the Call List Verification report was not accessible, has been resolved. 2)The issue where the CSID and Dealer Code Search fields did not work properly has also been resolved. |
||
There were several minor issues identified when using the Verify Passwords process on the Sub Info (F2) Form. ▪These anomalies have been corrected. |
||
The cause of this issue where the Operator had a problem seeing Contacts while Signal Processing an Action Plan controlled Alarm Signal has been resolved. |
||
|
|
|
Module(s) with Issue |
Forms Affected |
8240 - 8244 Anomaly (Bug) Fixes |
|
|
|
MKMS STARK |
The Modem Settings on the Personal Options tab in the User Options Form for LongDistanceDialing, LocalPrefix and LongDistancePrefix were not being properly saved to the ModemConfig.INI. ▪This issue has been corrected. |
|
MKMS STARK |
A Double-Click on an item within a List of maintenance items should select that Item and return the User to the main editing screen for that Item where the selected record may be viewed/updated/deleted, as needed,.Certain Forms did not work as expected: 1)Installed Equipment \ List View 2)Contracts \ List View 3)Insurance \ List View ▪These issues have been corrected. |
|
MKMS STARK |
Various |
Modified the table structures and triggers that wrote to the associated "Deleted" table to ensure all fields added to the parent table exist in their associated "Deleted" table. These are the transactions for which associated "Deleted" tables exist and can now be deleted (and restored where allowed) accurately: ▪Invoices and Invoice Line Items ▪Bills and Bill Line Items ▪Payments ▪POs and PO Line Items ▪Payment Allocations ▪Proposals and Proposal Line Items ▪Receipts |
|
|
|
When the User Clicks on the "Apply Receipt" option on the Receipts Form, the Receipt Allocation Form is displayed behind that Receipts Form, so the User needs to locate it and bring it to the front. ▪The issue was resolved by "forcing" that Receipt Allocation Form to the front of the Receipts Form. |
||
By using the associated Reorder ▪The issue was resolved by "forcing" that Reorder dialog to the front of the screen. |
||
When the "Bill Recurring Revenue in Cycles" option was not Checked in the Company Options - Invoice/Proposals tab, sometimes the default (Standard) Billing Cycle was not being set properly. ▪This issue has been resolved and the default Billing Cycle is now displayed (but not changeable) for information purposes only in the Auto Billing dialog |
||
When the Invoiced option was selected on the Sales Tax Breakdown Report, the system did not show the "Subject to Tax" Amount if the previous Sales Taxing Authority on the report also had the exact same "Subject to Tax" Amount. ▪How this was discovered is amazing but the fix was relative simple. |
||
Before Printing the Invoice, if this Subscriber wants the Invoice mailed to a different Address than the normal Billing Address, some Users saw the error "Error -265: Procedure 'GetInvAddress' not found (52W09)" when attempting to set an Alternate Billing Addresses defined for this Subscriber. ▪This issue has been corrected.
When an Invoice for a Service Only Account is located using the Subscriber by Invoice option, it should be opened in Read Only Mode. In certain cases, the User was still able to use the Insert, Delete, and/or other Navigation options. ▪This issue has been corrected by providing a new Search Open Invoice Read Only - By default, the SearchOpenInvoiceReadOnly option is set to False ("F") which means, when the Subscriber Search by Invoice Number feature is used, the Invoice - if located - will NOT be opened in Read Only Mode, even if the Invoice is for a Service Only Address record and it has a separate Bill Payer identified. ▪Setting this SearchOpenInvoiceReadOnly option to True ("T") Will open the Invoice in Read Only Mode, but only when that Invoice is for a Service Only Address record with a separate Bill Payer identified. ▪When an Invoice is opened in Read Only Mode, the Navigation Icons are not available. |
||
When selected "Converted Customer Deposits" option was Selected in the Customer Deposit Report and Retrieve Data was Clicked, the Amount column displayed BLANK. ▪This issue has been corrected. |
||
|
|
|
In the Tax tab of the User Options Form, when the Tax Calculations setting is "National & Local Based On Net" and Rate 1 in the National Tax Rates section is greater than '0', the program was using that Rate 1 even when the "Natl Tax" field on the Recurring Revenue Tab for a Proposal is set to 'N' or 'E'. ▪Now when the User sets "Natl Tax"field in the to to 'N' or 'E' the National Tax Rate Amount will be properly set to $0.00 |
||
The Proposal Packages maintenance Form's Package Items tab displayed the Proposal Description with Rich Text Editor internal formatting controls. ▪This has been corrected and the Proposal Description is now displayed normally. |
||
The system was jumping to the last record in the Prospect table after inserting a new Prospect and then editing another Prospect. ▪This issue has been corrected. |
||
|
|
|
|
|
The Price Total field in the Completion section of the Work Order Form was showing an incorrect Price Total Amount if there was a negative COGS Value within the required calculation. The program was adding the COGS Value of a negative Quantity rather than subtracting it. ▪The issue has been identified and corrected. |
|
When a User Prints the Service Requests, if a Work Order had no Technician assigned, a blank Work Order would be printed (instead of the requested service information). ▪The cause of this issue has been identified and corrected. |
||
The Schedule button on the Work Order Form was able to be selected more than once which caused more than one instance of the Technician Scheduling Form to be opened. The result was program inconsistencies, even a hard system shut down. ▪This issue has been eliminated by have the system ignore multiple Clicks. |
||
When creating an Appointment with the Appointment Editor for the Appointment Type "Other" and then selecting a Technician from the Schedules tab, the error message "Error -194: No primary key value for foreign key 'WorkOrder' in table 'Appointments'" was presented. ▪This issue has been resolved.
Sometimes the Appointment Editor was displayed behind the Technician Scheduling Form. ▪This issue has been resolved.
Program raised an access violation when scheduling a Service Request if that Work Order Form was opened from the Tech Schedule Form by right-clicking to open the Radial Right-Click Menu and Choosing Subscriber; then opening the Work Order; and then Clicking the "Schedule" Icon. ▪Resolution: Will no longer be allow a User to Select the "Schedule" Icon when the Work Order Form was accessed from a Subscriber record that was opened from the Technician Scheduling Form. |
||
The Auto Refresh option was not correctly performing that function in the Technician Status dialog. ▪The cause of this issue has been identified and corrected. |
||
|
Inventory Tracking/Job Costing
|
1)"WIP" Quantity for Inventory Items (in the Sale-Purchase Items Form) will no longer include any negative Quantities recorded for Inventory/Materials on a Work Order or Inventory Reserved for a Job 2)Inventory/Materials on a Work Order material "price" field and the associated Mat.\Mat."cost" field in the Work Order were not updating properly when updating (changing) Quantities, adding items to Inventory/materials(especially negative Quantities) whether it came from Inventory/Materials on a Work Order or Inventory Used for a Job.
▪This issues have been identified and corrected. |
|
|
|
|
The Bank Reconciliation dialog was displaying Receipts which had not yet been Deposited. ▪This issue, once identified, has been corrected. |
||
Previously, when a new Payment was created, and the User selected Check Type other than Credit Card (C), then changed that Check Type to Credit Card (C), the Bank Transaction record that was created initially (when the new Payment was first entered) is not deleted. ▪This issue, once identified, has been corrected. |
||
In previous versions - prior to the Bug Fix noted immediately above - changing a Payment's Check Type from anything other than Credit Card to a Credit Card was not deleting the original Bank Transaction record. So when the User attempted to delete it, since it still existed in the Bank Transaction record and Printed was marked as True, it was appropriately raising the error: Error - Cannot delete a printed payment.
As noted above, this was caused by having a Payment with a Check Type other than Credit Card (C), and the User had changed that Check Type to Credit Card (C).
With the above fix (the Bank Transaction record is deleted as appropriate), the User will be able to delete a Payment, as required, whether or not is initially was entered as a Credit Card Payment or switched to a Credit Card Payment later. |
||
Several issues were addressed based on whether the system was being used with, or without the General Ledger being activated: ▪If the General Ledger is not activated, the "Vendor" field within the Credit Card Form was disabled and so a User could not create a new Credit Card record upon attempting save the entry, an error message is displayed as follows: "You must enter a value for field(s): Vendor" The Vendor field is now available.
Now: ▪When the General Ledger is Not activated, and the Credit Card was already defined, and/or the assigned Payment Item (Purchase Category Code) was already used for a different Vendor, this message will be displayed: "Vendor/Payment item" already exists. Please select a new "Vendor/Payment item"
▪When the General Ledger is activated and the Credit Card was already defined, or the assigned GL Account was already used for a different Vendor, this message will be displayed: "Vendor/GL Account/Payment item" already exists. Please select a new "Vendor/GL Account/Payment item"
▪Also, if the General Ledger is activated, after saving a new Credit Card record, the Vendor field becomes Read Only. |
||
|
|
|
If a Work Order has Labor identified on it, and the Work Order's Service Type was properly filled in, the Service field (which should have the associated Service Type inserted automatically) on the Job Costing - Labor tab was not being being updated properly. ▪This issue has been corrected. |
||
The Inventory WIP Report with a negative value in a Work Order or Job WIP item displays it as a positive value. ▪During the analysis of why this was occurring, it was determined that for this purpose, negative WIP items in a Work Order or Job should be excluded all together since that are excluded from view in Financial Statements & Reports. ▪This change will ensure that the Inventory WIP Report matches the Balance Sheet. |
||
The Inventory Listing Report must account for a negative quantity for an Inventory Item entered on Work Orders, Jobs and Invoices. Previously, since the COGS Value is always positive, if a User entered a negative quantity for an Inventory Item entered on Work Order, Job and/or an Invoices the system retrieves a positive value. Negative quantities are being subtracted from the "Used Values" instead of added. ▪The Inventory Listing Report has been modified to ensure that the Listing report matches the Balance Sheet (Inventory Account).
Also, Job Inventory Used records associated with Work Orders will now be excluded, so the Inventory Listing report does not double calculate those items that are identified both in the Inventory/Materials on a Work Order and in the Inventory Used for a Job. |
||
Invoices may be creating from the Job Costing module. Some Users were Modifying an Existing Invoice by adding additional Inventory Items to those Invoices after they were created - causing issues with the accuracy of the Job Costing module. ▪The system will no longer allow a User to enter new Inventory Items to any Invoices originally Generated for a Job |
||
|
|
|
Corrections made to the functionality of the Review GJ Transactions Form: a)Changes to General Journal Entries were entered and posted which where then modified in the Review GJ Transactions Form where the Account was changed from a non bank GL Account to a Bank GL Account, the revised transaction was not correctly inserted into the Bank Transaction Register. b)The opposite was also failing, so when an Account was changed from a Bank GL Account to a non bank GL Account, the transaction was not correctly removed from the Bank Transaction Register. c)Finally, during these types of Review GJ Transactions modifications, the Bank Form's Current Balance field was not being updated properly. ▪These issues have been corrected. |
||
|
|
When General Journal Entries were entered and posted, then changed in the Review GJ Transactions Form so that the Debit Amount was moved to the Credit column (or visa versa), the Transaction was being displayed as a negative Amount on the wrong side in the Bank Reconciliation Form. As an example, if the User made a General Journal Entry for a $77.00 Debit and a $77.00 Credit, and then changed each Amount to the other side using the Review GJ Transactions Form, (basically reversing it yourself without hitting the Reverse GJ button), it was displayed incorrectly. ▪This issue have been corrected. |
|
|
|
|
MKMSCS |
|
|
Sometimes when Using the Subscriber Search Dialog to locate a specific CSID which is not the Primary CSID, the system will locate the Primary instead of the (secondary) one Selected. ▪This issue have been corrected. |
||
The issue where the Google Map Button presenting a "Bad Request" error when the Map is displayed has been corrected. |
||
In the CSID Zones Form in Subscriber Panels section within the Edit View - Monitoring tab, the Action Plan field's Drop-Down Selection List was not auto sizing so Users could not see all of the information that should have been available in that Drop-Down Selection List. ▪This issue has been corrected. |
||
Operator was unable to Dial a Dealer when an Action Plan was being processed because when the Dialog to dial that Dealer appeared, there is no telephone number inserted for them to dDal. ▪This issue has been corrected |
||
Clicking the "Filter" options didn't display the proper results in the Alarm Stack grid. ▪This issue has been corrected |
||
|
|
|
Module(s) with Issue |
Forms Affected |
8245 - 8251 Anomaly (Bug) Fixes |
MKMS STARK |
F2 The Subscriber Search - When All was chosen as the Limit Record option, the User could not successfully activate the option "All" because when it was selected, the program defaulted to "50" ▪This issue has been corrected. |
|
|
|
|
When canceling a Recurring Revenue record (see "Options when Entering an End Date" in the Defining Open Term Recurring Revenue chapter) originally entered with a one month discount for Annual Payment, and the User chose to issue a Credit for the remainder of the coverage period, the Credit Memo that was generated should (but didn't) exclude that One Month Discount. ▪This issue has been corrected. |
||
Resulting for the addition of a new field on the Billing Cycles Form, the Insert Icon was not working. ▪This issue has been corrected. |
||
If either the Date Paid of a Receipt which has been Allocated, or a Date Sold of an Invoice which has been Allocated has subsequently been modified, the system will now update the Allocation Date to be equal to either the Date Paid on the Receipt or the Sale Date of the Invoice, by inserting whichever of those Dates is newer. |
||
Previously, when Discounting the Gross Amount of an Invoice by using the Discount feature on the Invoice Form, the system would present the error "Could not convert variant of type (Null) into type (Boolean)" if a discount Amount was entered and the Discount Icon was chosen. ▪This issue has been corrected. |
||
When Authorize.Net was chosen as File Type in the Post Auto Drafts dialog, the associated file was not created, even when "Generate EFT File" option was also selected ▪This issue has been corrected. |
||
When Printing Invoices, the Email Invoices were not being included, even when specifically requested. ▪This issue has been corrected. |
||
The Deferred Revenue Setup Wizard, the Deferred Revenue Report, Earned Revenue by Month report, and the Post Earned Revenue process have been updated. ▪These reports and processes will now use an absolute value to compare Nett and Price when the Recurring Revenue record's Billing Frequency = 1 to calculate the Earned Revenue Amount. This needed to be changed because of a specific case: a)When a User had setup a Recurring Revenue record as "Cost Applies" was set to "Billing Frequency" (instead of "Cost Applies" Monthly), and the Amount was negative, the program was not dividing (Price/frequency) causing the Earned Revenue Amount to be overstated in this specific situation. b)When the Amount was negative but the "Cost Applies" was set to "Monthly" the program was handling that situation correctly. |
||
Recurring Revenue (records) |
1.If a Recurring Revenue record is setup with a Monthly Amount of less than $0.00 and no other Recurring Revenue records are setup with Monthly Amount greater than $0.00 with the same cycle/frequency as the negative Recurring Revenue record, the program will create a Credit Note. a.However, the Detail Line Items of that Credit Note must be (and now are) set to the GL Sales Account Number, not the Deferred Revenue GL Account, Number so it will not be picked up in the Deferred Revenue Report, Earned Revenue by Month report, and the Post Earned Revenue process as Deferred Revenue.
2.When a User enters an End Date in a Recurring Revenue record and chooses YES to create a Credit Note for any remaining coverage period, the query will now create a "positive value Invoice" for Recurring Revenue records which had a Monthly billing Amount of less than $0.00 (previously, the program had incorrectly excluded Records where the Monthly billing Amount of less than $0.00).
3.When selecting an End Date for a Recurring Revenue record and choosing Save, if the Deferred Revenue Setup Wizard was successfully executed (the DeferRecurringRevenue option in Company Settings is set to True), the program inserted any Deferred Revenue Amount remaining in (Nett - Earned Amount) for that Recurring Revenue record's RRID into the General Ledger's Transaction File. a.The calculation for what needs to be "earned" was not executed correctly for those records which were setup with a "Cost Applies" as "Per billing Frequency" or where the Monthly Amount was less than $0.00. b.Now the program correctly replaces the existing code with the same calculation the rest of the process uses and it posts properly. |
|
When inserting a new Receipt record into that table, if the system maintained field LastBankTransactionID in the User Options table was NULL, the system raised the error: "Field BankTransactionID in table BankTransaction cannot be null" ▪The cause of this issue has been identified, and corrected. |
||
If a Recurring Revenue record has been assigned an End Date and the DeferRecurrringRevenue option in Company Settings is set to True ("T"), the End Date can no longer be modified. When that Recurring Revenue record was ended, it inserted the remaining Amount that was in Deferred into the Transaction File thus reducing Deferred Amount and increasing Sales Amount. Changing the End Date would double-dip the Deferred Amount. Therefore the User must create a new Recurring Revenue record, and set the End Datedate to the Date to which is should have been set. |
||
|
|
|
|
|
|
Updates have been implemented to the internal spGLTransactionView (which is the calculation that sets values in the General Ledger resulting in the balances shown in the Balance Sheet, Income Statement and Trial Balance). Any Invoice created from a Job or a Work Order - effects the calculation for the COGSValue. ▪The system will now ensure that the "Sale Net Income Debit" and "Sale Net Income Credit" calculated when an Invoice was created from a Job or from a Work Order will retrieve Nett, otherwise it should retrieve Nett - COGSValue. ▪The system will now ensure that the Invoice values for "Invoice Inventory Debit", "Invoice Inventory Credit", "Invoice COGS Debit", "Invoice COGS Credit" are NOT coming from an Invoice generated from a Job or from a Work Order when it retrieves the COGSValue. ▪The system will now ensure that for "Job Inventory Debit" it will use the Job's CompleteDate instead of the InventoryDate.
Most Users will never see any difference because it was only an issue when the software used incorrectly. |
||
|
|
|
When using the Automatic Invoice Generation process while Completing a Work Order that originated from a Job Costing record, the General Ledger Accounts for Current Earnings and Earnings Posting (Mandatory Accounts) were not always being updated properly. ▪Now this is how those Current Earnings and Earnings Accounts will be updated: a)where Nett >=0 NetIncomeDebit = Earnings Posting NetIncomeCredit = Current Earnings b)where Nett <0 NetIncomeDebit = Current Earnings NetIncomeCredit = Earnings Posting |
||
|
|
|
When a Proposal Descriptions was entered for an included Sale-Purchase Item associated with any additional Proposal Option(s), then Printed Proposals showed internal Rich Text Formatting when addition Option(s) were defined for a Proposal and the "Print Additional Options Sheet" choice was selected. ▪This issue has been corrected. |
||
The cause of the rounding error that occurred with Sales Tax calculations on Proposal Detail Line Items has been located and corrected. |
||
|
|
|
|
|
1)When deleting non-inventory items from Inventory/Materials Drop-Down Info Box, the system would present the error: "Column lPriceIn not found" 2)When changing an entry in the Inventory/Materials Drop-Down Info Box of a Work Order from a non inventory item to an Inventory Item, that Work Order's Total Cost recalculation was not subtracting the Cost of the non inventory item (Material) that was being replaced. 3)If a User added a non inventory item from the proposed Inventory for a Job, then used it on a Work Order, the system was allowing the User to change that non inventory item to an Inventory Item which had not been previously reserved for the associated Job These 3 issues were fixed in the BeforeUpdateWorkOrderMaterialDetail database trigger. |
|
When a User chose the Print Service Request Forms option from the Service Tracking Reports Menu and/or from the Ribbon Menu on the Work Order Form, the Service Request document was showing the Previous Subscriber Balance - the Amount that the Subscriber currently owes (if any) at that address - even when the Subscriber's Work Order was from/for a "Service Account". ▪The Service Request document will now show the Total Balance Due for the Bill Payer. |
||
|
|
|
The issue with an Email process failing when the User has attempted to Email (a Purchase Order without Printing it first) has been corrected. |
||
|
|
|
Previously, the Labor tab on the Job Costing Form did not allow a User to enter a a Work Order Number. Users are now allowed to select a a Work Order Number using the (now) available Drop-Down Selection List. |
||
|
|
|
After data was retrieved and viewed, and then a Review GJ Transactions dialog was closed, an "Error - 141: Table '#tempTran' not found (42W33)" error was displayed. ▪This issue has been corrected |
||
MKMSCS |
|
|
Previously while Signal Processing, an Operator was sometimes unable to Dial a Dealer when an Action Plan was in use because when the Dial dialog to Dial a Dealer appeared, there is no telephone number inserted. ▪This issue has been corrected. |
||
|
|
The Google Maps issue - Click the Map Icon on Signal Processing, or Quick Work Order and the map displayed would navigate to the equator. ▪This issue has been identified and corrected. |
|
|
|
|
Module(s) with Issue |
Forms Affected |
8252 Anomaly (Bug) Fixes |
When using InnoEPay as the Company's Payment Gateway: In the Edit View on Subscriber Form on the Auto Draft Setup section, after a User Modified a Credit Card Number and/or the Expiration Date and then saved change(s); did not close the Auto Draft Setup screen or change to Browse View, waited about 30 seconds, then tried to change an Email address or other data not related to the Auto Draft Setup dialog (how do we find and fix these things, it's amazing!), the program would display the error: "Couldn't perform the edit because another user changed the record".
▪The cause has been identified [e.g., when the Credit Card Number and/or the Expiration Date is modified, the system calls a stored procedure ResetCardToken to blank out the CardToken field and sets the CardTokenStatus field to PENDING, after which the InnoEPay service resets the CardToken field with the appropriate Token, and sets the CardTokenStatus field to TOKEN which should not occur until the changes were saved. ▪That cause has been corrected. |
||
On data the Accounting tab within the Subscribers Form includes the Balance (displayed in Blue if Current, Red if Past Due), Last Sale Amount and Last Payment Amount information, Salesperson assigned to the Account, Average Recurring Revenue (Avg Mthly RMR), Email Invoice, outstanding Deposits (if any) and the Last Sale Date and Last Payment Date information. ▪The Average Recurring Revenue (Avg Mthly RMR) Drop-Down Info Box contained an incorrect Frequency in that column. ▪This issue has been corrected. |
||
The Comments from the first Invoice that was printed were incorrectly appearing on all other Invoices. ▪This issue has been corrected. Program raises error '' " is not a valid integer value." when a User Checks the Select RMR Range box then types inside the Cycle box ▪This issue has been corrected. |
||
When attempting to add a Billing Cycle Code with a Starting Day Number greater than 28 generates an error and will not allow that Recurring Revenue record to be saved, This was originally reported as a error, but was determined to ultimately be an appropriate (though not very graceful) error. ▪The correct solution is to not allow a Starting Day Number greater than 28 to be used when defining any Billing Cycle. This is because: once assigned, you may not realize that many times the Recurring Revenue Invoice with a a Starting Day Number greater that 28 would not be generated in February - even if it should have. |
||
When a Subscriber chooses to use the E-Pay option ("E-Payments") to pay for an Invoice, the E-Payments Form was not refreshing the Balance field and label "Open Invoice" correctly. ▪This issue has been corrected. |
||
When using Authorize.net, the Receipt was being created but the Amount was not being Allocated to the Invoice. The system did not show dialog with options: i.Add Receipt Only? ii.Add Receipt and Apply? ▪A scripting update and a default Company Settings change have corrected this issue. |
||
Fixed problem when the Billing Cycle dialog was allowing a User to change the Starting Day field to a day number greater than 28 when the DeferRecurring option in Company Settings was set to True (''T'). |
||
Corrected the Ledger Card dialog to avoid error "QryControl: Field 'InvoiceNumber' not found" error when running the Ledger Card report with format option as either Traditional or Contemporary, and then trying to run the report with the new option "Running Balance". |
||
Fixed the AV error displayed when Pay Batch Pending Transactions dialog was presented after modifying Auto Draft Setup Credit Card Number or Expiration Date Information |
||
|
|
|
The system would set the Balance Due to $0.00 when a User changed Bill Amount from a net positive to a net negative. ▪This occurred when a new Bill was created and a Detail Line Item was entered with a Quantity = 1 and a Price = $10.00 and saved it. At this point the Balance Due = $10.00 ▪However, if the User changed Detail Line Item to Quantity = -1 and and saved it, the Balance Due would re-be set to $0.00 - but of course it should be -$10.00 That cause has been corrected. |
||
|
|
|
In the Estimate vs Actuals section of the Job Costing Form the Estimate vs Actuals - Total Paid and Invoice Balance showed incorrect Amounts if the Invoice was generated which had Sales Tax charged. ▪This issue has been corrected. |
||
|
|
|
Module(s) with Issue |
Forms Affected |
8253 Anomaly (Bug) Fixes |
Attempting to manually enter an integer in the Billing Cycle field of the Recurring Revenue Preview caused an error. ▪The system now ignores anything but a selection from the Drop-Down Select List provided. |
||
Invoices show the same CSID (specifically the Bill Payer CSID) for each Recurring Revenue line item when the system generated an Invoice for Recurring Revenue on for Service Account when the option "Show CSIDs on Recurring Revenue items?", ▪This issue has been corrected. |
||
When Printing Invoices and the E-mail Invoices was selected, the system was net properly sending those Emails. ▪This issue has been corrected. |
||
When , if either Summary options (with or without Line Item Detail) is selected, and a Specific Division was selected to be reported, all Invoices were being printed. ▪This issue has been corrected. |
||
When Printing Invoices on Pre-Printed Forms the Header Graphics were being overwritten on subsequent pages when the Invoice required multiple pages. ▪This issue has been corrected. |
||
When Printing Invoices and the Use Pre-Printed Invoices? option was not Checked in the Company Options - Invoice/Proposal sub-tab, Invoices were not including the Company's Logo and Company Address information. |
||
In the Pay Batch Pending Transactions dialog when a User changes Credit Card's Number or Expiration Date, the system was not clearing the "Card Token" field. ▪This issue has been corrected. |
||
In the ePay Preview Gird, sometimes the Credit Card Numbers displayed without mask. ▪This issue has been corrected. |
||
When the Average Recurring Revenue Report was run for a specific Division, sometimes no data was presented which seemed to be caused by how the Division Code and Division Name were constructed. ▪This issue has been corrected. |
||
On the Invoice Statements report, it was noted that the Service Address section displays the Street Address from Service Address, but shows the City, State, and Zip of Bill Payer Address. ▪This issue has been corrected. |
||
When the system is set to not to use individual Subscriber's Term, the Due Date is visible on the Auto Billing Form and the User can select a Due Date when running the billing. However, the Program was not using this Due Date, it was using the System Terms field in Company Options - General ▪This issue, once identified, was corrected. |
||
Deleting a Recurring Revenue record did not remove any corresponding Suspended Invoicing record(s). ▪This resulted in Suspended Invoicing records being abandoned after deleting a related Recurring Revenue record that had an outstanding Suspended Invoice. ▪This issue has been corrected. |
||
Previously, when a Receipt has been posted to a Bank and a User attempts to set the Bank as Inactive, the system will display a message “Invalid Value You cannot make this bank Inactive. There are unallocated or undeposited receipts for this bank.” in scenarios (1-3) below. 1.When Deposited and Not Allocated 2.When Not Deposited and Not Allocated 3.When Not Deposited and Allocated ▪When Deposited and Allocated - User is able to make it Inactive
Considering the above scenarios, ▪Scenario #1 When Deposited and Not Allocated, the program should allow a User to make the Bank Inactive, but a User gets the message that they cannot make this Bank inactive. ▪The correction has been made |
||
|
|
|
When the Installed Equipment (Shift+F9) tab is updated on the Work Order Invoicing/Review Form, and items are identified on the Installed Equipment tab as Installed, the Save button was not being activated when the Work Order was marked as Non-Billable. ▪In fact, that set of Installed Equipment is stored in a Temporary table and is still posted to the Subscriber's Installed Equipment Form when so identified, even when the Work Order is not being Invoiced. |
||
When there are two Work Orders in the Work Order Invoicing/Review Form, a User is able to Generate an Invoice for the first Work Order successfully, but when trying to Generate an Invoice on the last Work Order in the list, a syntax error is displayed as “Error-131:Syntax error near ‘,’ on line 1 (42W04)” Note: After clicking on Continue application on the error, the Invoice is getting generated. This issue has been corrected. |
||
The system was incorrectly displaying a message that the User "Cannot end a recurring revenue for a month already earned" .when the DeferRecurringRevenue option in Company Settings was True ("T") because the Deferred Revenue Setup process had been activated. This prevented the User from modifying anything else after the Recurring Revenue was ended. ▪The system now shows the message only when the User is trying to end a Recurring Revenue that has already been recorded as Earned. |
||
When a Recurring Revenue record with a Billing Frequency of Annual and Discount of one Month for annual payment was automatically invoiced, it was observed that the resulting (Discount) negative Detail Line Item on that Invoice was posting to NetIncomeCredit and NetIncomeDebit, thus is causing the Balance Sheet to be Out of Balance. ▪Both Auto Billing processes were affected. ▪This issue has been corrected. |
||
|
|
|
When Printing Service Request Forms, the Phone number and CSID info were not included when no Service section information was enter within the Edit View of the Subscribers Form because If Subscriber does not have a "ServiceID" in that "Service section" then no Account information such as phone number, town code, sale date, etc. is included on a printed Service Request Forms ▪This issue has been resolved. |
||
|
|
|
The Inventory WIP report was showing incorrect Amounts for column "Value" ▪This issue has been corrected. |
||
|
|
|
Payments and Deposits were not displaying the correct values when a User selected the "Finish Later" option and then re-open the Bank Reconciliation Form, the "Payments" and "Deposits" Amount and Count sometimes do not show the correct values. ▪This issue has been corrected. |
||
|
|
|
On the Alarm Activity Report options section, when the "Specific Subscriber(s)/One CSID" or "Specific Subscriber(s)/ All CSIDs" is selected, a form is opened to Choose the Subscriber and upon selecting that Subscriber (or CSID) and Clicking the OK button, an error as being displayed: "The session property is not linked to a session", and the User was not able to close that Search Form even by Clicking on continue application on the error dialog. ▪This issue has been corrected. |
||
When an Operator attempts to Place an Account on Test, and during that process, selects New Account (see Quick Account Setup), in the process of inserting that New Account the Salesman Drop-Down Selection List was displaying all Users, including inactive Users ▪This issue has been corrected. |
||
|
|
|
Module(s) with Issue |
Forms Affected |
8254 Anomaly (Bug) Fixes |
|
|
|
MKMS STARK |
The Employee Groups Form was not functioning properly causing new entries to be inaccessible until the Form was closed and re-opened; and the List option did not properly retrieve the assigned Form Names for the selected Group. ▪These issues have been corrected. |
|
|
|
|
Deferred Revenue (Daily View) |
The Deferred Revenue (Daily View) report has been eliminated. |
|
The Cash Receipts by Employee report was not properly grouping Payment Transactions processed by the ePay Service. ▪This issue has been corrected. |
||
|
|
|
Sometimes when a User selected a Receipt with a Double Click, in the Bank Transactions Register, the system displayed an incorrect Receipt record. ▪This issue has been corrected.
An intermittent "cannot focus and invisible component" error was displayed when tn Employee Payment or Employee Receipt was being posted. ▪This issue has been corrected.
The General Ledger System was going Out-of-Balance when an Employee Receipt was posted because the General Ledger Accounts were being updated incorrectly (a Debit/Credit mix up). ▪This issue has been corrected.
The Bank Transactions dialog was allowing the selection of an incorrect Sale-Purchase Item when posting a transaction (e.g., selecting a Purchase category when a Sales category was required). ▪This issue has been corrected. |
||
|
|
|
When running the Calculate Average Item Cost process, the system was not excluding Sale-Purchase Items identified as a Kit. This caused the Value of Inventory to be inflated when reported in the Calculate Average Item Cost procedure and the Inventory Listing As Of report. ▪This issue has been corrected. . |
||
|
|
|
