What's New in Version 8.02 September 2024 Release
Enhancement
Personalization Update
- Archiving Extensions: The extensions now include an archiving feature, allowing you to manage and store your extensions more effectively.
- Migration Scripts: Migration scripts have been added to facilitate the transfer of your existing personalization from M2M 7.51 to 8.0, ensuring a seamless transition.
Resolved Issues
The following issues have been fixed in this release:
| ID | Description |
|---|---|
| DEV-82870 | The fpostalcode_format string was incorrectly displayed in the To: address block on the standard RPSOPI report layout when printing pro-forma invoices for the insurance copy. |
| DEV-150450 | Exporting the shipping queue grid data to Excel using the right-click export functionality caused the date columns to be exported in a string format such as Mon Dec 19 2022 00:00:00 GMT-0500 (Eastern Standard Time). This format hindered the user’s ability to convert the column data type to a usable date format within Excel. |
| DEV-155091 | When switching the filter from Customer Returns to Receiving Inspections and then back to Customer Returns, the Customer Returns data failed to appear. |
| DEV-155950 | The INSSN work center was not visible in the list of available work centers for copying when attempting to copy a user’s work center on the SFMSETUP screen. |
| DEV-161328 | The Supervisor Console [SFMS] was displaying redundant entries for a single employee on the Employee Status grid, even after the employee clocked off a job. |
| DEV-175046 | The cursor reverted to the FROM date field when attempting to input a date in the TO date field within the RPBKLG report. |
| DEV-175091 | Parts in the Item Master browse window were not sorted alphabetically by part number. |
| DEV-191293 | The Browse button in the User screen triggered an exception after modifications were made. |
| DEV-200599 | When creating a drop-ship order and switching the Ship/Drop to Customer in the PO screen, selecting a customer in the customer lookup field displayed the vendor details instead of the correct customer information. |
| DEV-207961 | The job queue tab did not remain highlighted when switching between tabs on the work center console screen, causing confusion for the user. |
| DEV-221987 | The sorting functionality did not work as expected in the drill-down lookup window on any widgets in Action Center. |
| DEV-216937 | Phantom items were duplicated when viewing standard BOMs, disappearing only after expanding and collapsing all components. |
| DEV-218784 | The RPGLTL screen, when used to generate the Detailed GL Transaction Report with a range of accounts, experienced instability. The selected range of accounts either automatically reverted to a single account or incorrectly required a range, even when all necessary fields were filled. |
| DEV-219825 | Scheduled reports were not executing automatically on CMDS due to a discrepancy in the last run time field within the PROC screen. |
| DEV-223175 | The PINS screen prevented saving inspection data for jobs with descriptions exceeding 72 characters. |
| DEV-224223 | The APPCHK screen in 8.0 failed to save changes made to invoice selections after navigating to the print checks popup and closing. |
| DEV-226536 | The Email option within the More Actions section failed to initiate the default email application with the pre-populated subject line. |
| DEV-227115 | The warning message displayed in M2M 8.0 when entering duplicate customer PO numbers disappeared too quickly. |
| DEV-227312 | Scheduled reports failed to execute due to the RecurringEventsDocuments process running in a continuous loop, preventing other commands from executing on CMDS. |
| DEV-228087 | Creating Miscellaneous payments in the APMISC screen could create duplicate CASH-xxxx records and/or APDIST entries if the save button was clicked multiple times while the focus was on the check amount field, leading to inaccurate aging and GL data. |
| DEV-228499 | The PUT API incorrectly modified the parent facility on Standard BOMs, violating business rules and potentially causing data corruption in a multi-facility environment. |
| DEV-228901 | The Data Type field for total debit entry dollar amount in the trailer record of the NACHA-CCD-STANDARD template could not be changed from FreeText to Expression in the EFT Template Designer screen. |
| DEV-230135 | The extended price and total price fields did not populate on the pro forma invoice document, despite being present in the underlying sales order. |
| DEV-232241 | The type-ahead function for account number fields threw server errors in various forms when GL accounts lacked a separator. |