Release Notes - Essentials 17.03.008.0004

A recent update has resolved an issue where the general ledger date (gl_date) was not populating correctly when importing journal entries from Excel. The system will now automatically set the gl_date on the imported journal entry lines to match the date specified on the form consistent with the behavior observed when manually entering journal entries. This change ensures that the gl_date is accurately reflected and available for reporting purposes enhancing the overall functionality of the journal entry import process.

A recent update has addressed an issue with the balance type defaulting incorrectly when adding lines to an income statement. Previously when users clicked 'next' to add another line the balance type would change to 'ending' instead of remaining as 'change in balance'. This has been corrected and now when creating an income statement the balance type will default to 'change in balance' as expected when adding new lines. For balance sheets the default will remain as 'ending'.

The system has been updated to enhance the security of sensitive bank account information. Specifically the Bank ID Account Number and IBAN fields in the database are now encrypted to comply with PCI standards. This change ensures that any existing data in these fields will also be encrypted providing an additional layer of protection for sensitive financial information. Users will notice that the Account Number and IBAN fields will display as masked when accessed maintaining confidentiality while allowing necessary operations to continue seamlessly.

The journal entry feature has been updated to ensure that when an entry is copied the general ledger date now automatically reflects the current date from the entry form. Previously the copied entry retained the original date which could lead to discrepancies on printed journal forms. This improvement ensures that the date displayed in the journal entry grid corresponds accurately with the date selected on the form enhancing the clarity and accuracy of financial records.

In the recent update we addressed an issue where exporting accounting reports to Excel resulted in number fields being exported as text. With the implementation of a new regex check the system now correctly distinguishes between arithmetic numbers and other numeric representations. This enhancement ensures that exported Excel files will display number fields as numeric types improving data usability and accuracy for users.

A recent update has resolved an issue where the invoicing feature was not correctly utilizing the Group Emails option when sending invoices. Previously all invoices were being sent to the same email address regardless of the individual customer details. With the latest changes the system now correctly groups emails by customer ensuring that each recipient receives their respective invoice. This enhancement improves the efficiency of the invoicing process allowing for a more streamlined communication with clients.

Fixed issue with post receipt PO adjustments so that taxes are only recalculated when saving to the database. This fixes the problem with PO Tax Lines being out of sync with the GL postings.

A recent update has improved the process of voiding transactions specifically addressing issues related to currency precision. Previously users encountered errors when attempting to void payments due to a general ledger imbalance caused by rounding discrepancies. The development team has implemented a solution that recalculates the currency amounts with greater precision ensuring that the debit and credit values are accurately reflected during the voiding process. This change allows users to successfully void transactions without encountering errors enhancing overall functionality and user experience.

A recent hotfix has resolved issues related to tax exemption processing during order entry. Previously users encountered errors when attempting to save orders that were marked as tax exempt particularly when using certain shipping addresses. The development team has implemented a check to ensure that tax exempt orders are properly handled eliminating the errors previously experienced with the Avalara system. Users can now successfully save tax exempt sales orders without encountering the prompt that indicated a tax calculation error.

A new security feature has been implemented to enhance the integrity of temporary journal entries. Users are now prevented from approving a temporary journal entry while it is being modified by another user. This change introduces record locks that function similarly to those used for other records ensuring that if a user attempts to approve an entry that is currently being edited they will receive a prompt indicating that the record is locked. Users with the appropriate permissions can override this lock allowing them to approve the entry while notifying the original editor that their changes have been lost. This update aims to streamline the approval process while maintaining data accuracy.

A recent update has addressed an issue where amounts added as rebates in the Cash Receipts screen were incorrectly categorized under Cash Discounts instead of Deduction Amounts. The development team implemented a change to ensure that when a user modifies or adds a rebate it is properly recognized as a deduction. This adjustment involved refining the filtering process for deductions allowing for accurate tracking and reporting of financial transactions. Users can now expect that any changes made to deductions will reflect correctly in the system.

A recent update has resolved an issue where the first row of a closing journal entry did not display the associated account debit or credit amounts when edited. This was due to an indexing mismatch in the system that affected how data was retrieved for the first entry line. The development team has updated the indexing logic to ensure that the correct information is now populated and displayed properly in the Edit Journal Entry window. Users can now successfully view and modify the first line of closing entries without any missing information.

Fixed an issue where projects attached to purchase orders were not being considered when adding adjustments during the Purchasing > Invoice transaction.

The functionality for processing credit card payments on account has been enhanced to include the NET1 payment window. This improvement allows users to seamlessly receive payments for existing orders using the Payment on Account option. The development team implemented new logic within the PaidSale form ensuring the NET1 payment window opens correctly when a credit card payment type is selected.

A null reference exception that occurred during the credit card reauthorization process has been resolved. The fix involved adding a check to ensure that the payment information is not null before proceeding with the authorization. Users should now be able to successfully reauthorize credit card transactions without encountering errors and the system will correctly reflect the authorized status in the transaction records.

The functionality for processing credit card backorders has been enhanced to ensure that backorders are correctly charged upon shipment. Previously backorders created from credit card parent orders were not triggering charges at the time of shipment. The development team implemented a solution that allows for reauthorization of the credit card using a vault ID ensuring that the remaining balance for the backorder is captured appropriately. This improvement streamlines the payment process and enhances the reliability of transactions for backordered items.

A new field AuthInvNum has been added to the CreateOrder API endpoint to improve transaction processing for the custom credit card processor setup with Braintree. Previously issues arose when the authorization amount was lower than the order amount leading to failed void attempts due to missing TransactionId information. With this enhancement the TransactionId will now be stored correctly in the new AuthInvNum field allowing for successful order shipping and transaction voiding. This update streamlines the handling of credit card transactions ensuring a smoother experience for users.

A recent update has addressed an issue where an error message would appear when entering a sales order for a ship-to location that had a defined facility but lacked a specified currency. The resolution ensures that if the ship-to facility does not have a currency set the system will now default to using the currency associated with the ship-to address instead. This change eliminates the error allowing users to create sales orders without encountering the previously generated error message when a currency is not defined for the ship-to facility.

When importing EDI Purchase orders, user calculations will now always be executed. Before, they were only executed if the imported PO was to be received.

The issue regarding the automatic invoicing process when receiving Purchase Orders via EDI Import has been resolved. The system now correctly honors the 'Auto Invoice' checkbox on the PO Header ensuring that invoices are generated automatically and payments are processed when there is no balance due. This functionality is consistent with the behavior observed in the main application providing a seamless experience for users. The necessary adjustments have been made to the EDI import process to eliminate previous errors related to null invoicing dates.

A recent update has resolved an issue where Master Lots were not being created during EDI imports. With the implementation of the new changes the system will now generate a new masterlot number even if the fi_masterlot value is negative accommodating specific EDI setups that require this configuration. This enhancement ensures that the masterlot number is correctly populated for both single and multiple pallet scenarios during the shipping process aligning with the expected behavior for EDI transactions.

A recent update has resolved an issue with the EDI system that allowed the shipping of quarantined inventory without proper permissions. The system now requires that the quarantine status be explicitly defined in the EDI Parsing Rule and users must have the necessary permissions to reserve and stage inventory from quarantine. This change ensures that quarantined lots cannot be unintentionally shipped enhancing inventory control and compliance with shipping protocols.

Fixed an issue where purchase order fields and user defined fields were not be updating during EDI Imports.

The functionality for producing assemblies with catch weight items has been improved. Previously users could only produce a quantity of one item regardless of the amount specified. With the recent updates the system now accurately fulfills the entire requested quantity while maintaining the specific catch weight values for each item produced. This enhancement ensures better inventory accuracy and addresses the discrepancies that were previously reported.

A recent update has resolved an issue that caused an error when printing lot labels from the lot report. Users can now successfully print labels in various formats including PDF and direct to printer without encountering any errors. This fix enhances the functionality of the inventory reporting feature ensuring a smoother experience for users when handling lot labels.

The issue related to incorrect quantities and expiration dates displayed on the Receive Purchase Orders grid when processing Transfer and Hold Purchase Orders has been resolved. The system now accurately reflects the quantities and expiration dates as per the shipped items ensuring that users see the correct information when receiving these orders.

The Final Staging process has been updated to ensure that the Formula Requirement field now consistently displays the full amount required for the formula rather than matching the remaining quantity. This change clarifies the distinction between the total formula requirement and the remaining quantity enhancing the accuracy of staging operations. Users can expect the Formula Requirement to remain constant throughout the final staging process providing a more reliable reference for inventory management.

Added a new security "Inventory -- allow move without source location" to support the ability to require, or not require an entry in the Source Location and Source Location Type field when moving inventory. This allows more precise control and also allows users, for example, to move an entire lot split into different locations

Fixed an issue where users could not receive Transfer and Hold Purchase Orders with non-Deacom parts, i.e - the PO line only contained a part description and the part number field was blank. This process is allowed by the Transfer and Hold process in Deacom.

The View BOM report has been updated to ensure that the facility selected in the BOM revision carries over correctly. Users will now see the appropriate facility displayed on the View Bill of Materials form when accessing it from a revision. Additionally the standard total costs for the BOM will now align with the costs from the item master data for that facility providing more accurate financial information. These enhancements improve the overall usability and accuracy of the BOM reporting process.

The issue with printing labels for purchase orders that involve split lots has been resolved. Previously labels were incorrectly displaying part numbers or missing information when multiple part numbers were involved. The development team implemented a change to ensure that the report properties dictionary uses the sequence number of the labels cursor instead of the record number which had caused errors in certain scenarios. This adjustment guarantees that labels now print with the correct information including barcodes for all lots even when splitting occurs. Testing has confirmed that labels are now generated accurately across various scenarios.

A recent update has resolved an issue with the lot control settings for specific facilities. Previously the system was not correctly applying the facility override settings for lot requirements leading to confusion during the shipping process. With the latest changes when the 'Require Lot On Relief' and 'Require Lot On Receipt' settings are adjusted in the Item Master the system now accurately reflects the intended lot control behavior. This ensures that the correct lot control status is enforced based on the configured settings enhancing the overall functionality and user experience.

A recent update has addressed an issue where some pallets were not being included in the master lot during the finishing process. The development team identified that the problem stemmed from the system not properly handling the query results. The resolution involved implementing a generated identifier for messages and ensuring the stream was flushed correctly. Following these adjustments the system was tested and confirmed to function as expected with all pallets and finishes being accurately recorded in the master lot.

A recent update has resolved an issue with the calculation of accounts receivable postings during inter-company transfers involving multiple lots. Previously the system incorrectly multiplied the total for certain accounts by the number of lots reserved leading to inflated totals. The logic has been adjusted to ensure that the correct amount is calculated based solely on the order total regardless of how many lots are involved. Testing has confirmed that the system now accurately reflects the expected total ensuring that financial records remain consistent and reliable.

The Master Production Calendar has been updated to ensure that the inventory availability colors remain consistent regardless of whether the calendar is run by shop area or not. Previously the colors would change based on the selected shop area leading to confusion. With this resolution users will now see the same color representation for inventory ensuring clarity and consistency in job status. This change improves the overall functionality of the calendar and enhances user experience.

A bug that caused negative inventory to persist after unshipping inter-company transfers has been resolved. Previously when an inter-company transfer was shipped and then unshipped any negative lots created during the shipment were not zeroed out leading to incorrect inventory counts. With the recent update these negative balance lots are now correctly zeroed when the transfer is unshipped ensuring that the inventory reflects accurate quantities.

The visibility of the Shelf % Required and Shelf Days Required fields has been improved in the system. These fields are now accessible in the Bill-To Record Customer Part Cross References and Ship-To Defaults Tab allowing users to better manage shelf life requirements. This update involved adjusting the licensing for these fields to ensure they are displayed correctly in the relevant forms.

A recent update has resolved an issue with the scanning of UPC substitutes in the Reserve Sales Order process within the Deacom Essential WMS. Previously scanning a UPC code for a substitute would not correctly process the quantity required leading to errors in inventory lot reservations. The development team has implemented changes to ensure that the correct part information is sent to the backend allowing the system to accurately reserve inventory when a substitute is scanned. Users will now be able to scan UPC codes for substitutes and the system will appropriately populate the transaction list after entering the required quantity.

The Lot Tracking Explosion report has been updated to ensure that only finished lots are displayed when the 'Finish' view filter is applied. Previously this report was erroneously showing unfinished items The fix involved adding a validation to the relevant function that processes the report aligning its behavior with expectations and enhancing the accuracy of material tracking for users.

Fixed an issue where duplicate facility items were allowed on the item master record.

The Case Item facility form has been updated to ensure that users with facility restrictions can only access the location types associated with their restricted facility. Previously users were able to select any location type which did not adhere to the established restrictions. With this enhancement the form now correctly filters the available location types providing a more secure and compliant user experience.

The issue related to the processing of receipts for specific items on a purchase order has been addressed. Previously when receiving items that were not lot controlled the system incorrectly displayed an old lot number leading to inaccuracies in cost calculations. This has been resolved by ensuring that when inventory settings are switched to standard cost the system behaves as expected referencing the correct lot costs. This fix is part of a broader update that has been validated in the development environment ensuring that the receiving process now accurately reflects the current cost values.

A new 'Group By' option has been added to the Inventory Management reporting feature allowing users to summarize reports by location or by a more general summary. This enhancement addresses issues where reports were previously displaying multiple lines for the same lot which caused confusion and inefficiency. Users can now choose to group results either by location maintaining the current functionality or by summary which consolidates data into a single line when applicable. This improvement streamlines the reporting process and reduces the need for additional data manipulation outside of the system.

The Usage Detail inventory report has been updated to accurately reflect the shipped quantities. Previously the report returned incorrect balances by failing to account for certain shipped orders due to filtering issues in the underlying SQL queries. These filters have now been revised to include all relevant shipped orders ensuring that the report displays the correct total 'out' quantity. Users can expect the Usage Detail report to now align with the Transactions report providing a more accurate overview of inventory movements.

Fixed an issue where lots received report was not honoring filters correctly.

A recent update has resolved an issue where scanning a lot label during the Reserve Sales Order process would only populate the part number requiring a second scan to fill in the lot information. The problem was traced to a variable that was not set correctly after processing the part number which has now been fixed. Users will now find that both the part number and lot information are populated with a single scan streamlining the inventory management process.

Fixed an issue where lots were not printing on the staging picklist for certain job types.

Fixed an issue where inventory lots were not properly relieved from Shop Area Locations.

User can now final stage lots that are in "QC Pending" status. This change only applies when performing final staging. It effects no other moving, staging or issuing transactions.

The recent update has addressed an issue where move transactions were incorrectly included in the usage and usage detail reports. This change reverts a previous modification that had removed the necessary filtering for inventory moves. After discussions with the product development team it was concluded that these transactions should indeed be filtered out to accurately reflect actual usage. As a result the reports will now correctly exclude any 'Move Inventory' transactions ensuring that only genuine usage data is presented.

The issue where the quantity entry parameter only appeared once for multi-line purchase orders has been resolved. The development changes ensure that the parameter prompt is now displayed for each line item when printing labels allowing for distinct values to be entered for each line. Additionally if the part form is set to print by lot the parameter will appear for each lot as intended. This enhancement improves the functionality and ensures accurate label printing based on user input.

The system has been updated to ensure that lot notes are retained during the shipping and receiving process of inter-company transfers. This enhancement allows users to maintain the notes associated with lots, providing better traceability and information continuity.

The Cost Updates tool has been enhanced to include 'Supplies' as an option in the Item Type field. This update allows users to filter and target supplies during cost updates ensuring that all relevant update types are available for selection. As a result users can now effectively manage and update lot costs fixed standard costs purchase order price variances and shipped orders COGS delta for supplies.

An adjustment has been made to ensure that when updating lot costs for facilities using a currency other than the base currency the system no longer incorrectly posts to the currency gain/loss account. The development changes involve using the facility's currency ID and exchange rate for accurate postings. Following this update the general ledger entries will now only reflect the inventory account and the standard gain/loss account streamlining the accounting process and improving accuracy.

A recent update has resolved an issue in the Time-Phased MRP report where the exclusion of lead time unintentionally removed the issued row from the output. This change ensures that the issued row remains visible even when lead time is excluded from calculations thereby providing users with a more accurate representation of their inventory planning data. The underlying code has been modified to maintain the integrity of the issued row based on the user's filter selections enhancing the overall functionality of the MRP reporting feature.

A resolution has been implemented to address an error encountered when creating jobs from MRP for items with the 'Split Jobs by Job Qty' option enabled. Previously users received an error message indicating that no available days could be found in the shop schedule even when there were no routings associated with the item and the scheduling was set to Manual. The development change ensures that the job scheduling process will now correctly bypass availability checks when the job schedule is set to Manual or Not Scheduled. As a result users can now create jobs without encountering this error under the specified conditions.

A recent update has addressed an issue where forecasts without an assigned facility were excluded from MRP reports when using a facility or facility group filter. This change ensures that all relevant forecast data is included in MRP reports regardless of whether a facility is assigned. The fix has been implemented in the system allowing users to view forecast data accurately even when utilizing facility group settings in the prefilter.

The MRP system has been updated to ensure that the minimum and maximum quantities for facility part cross-references are displayed correctly when filtering by a specific facility. Previously users experienced issues where the MRP did not reflect the appropriate values based on the selected facility leading to confusion. With the recent changes the system now accurately retrieves and displays the correct minimum and maximum quantities for each facility providing users with the expected results when filtering by facility.

The issue regarding the calculated user field not populating when jobs are created from MRP has been resolved. The system now ensures that the user-defined field for the Julian date is correctly calculated and populated both when jobs are created manually and through the MRP process. This enhancement allows for seamless integration of calculated values improving the efficiency of job creation and label pre-printing.

The functionality of the Safety Days exclusion in the MRP pre-filter has been corrected. Previously when the option was set to 'Include' safety days were not factored into the suggestion date and when set to 'Exclude' they were incorrectly included. This issue has been resolved by adjusting the underlying logic to correctly interpret the inclusion and exclusion settings. Additionally we addressed concerns regarding incorrect material suggestions that could lead to over or under ordering. Users are now able to generate accurate suggestions based on lead times and safety days ensuring better inventory management.

A fix has been implemented to resolve an issue where users encountered a logic system error (LSE) when attempting to create an inter-company transfer (ICT) from the Instant MRP feature. This issue was caused by a missing facility relationship lead time in the system. The development team has updated the related method to ensure that lead times are correctly retrieved from existing facility relationships or default to zero if none are found. Following this update users can now successfully create ICTs without experiencing LSEs.

A resolution has been implemented to address an issue where the system was generating incorrect job quantities from MRP configurations. The problem stemmed from the way sub-assemblies were being evaluated resulting in some jobs not reflecting the expected quantities. The development team restored the necessary variable to ensure that new sub-assembly lines are created with the correct fields. Following this fix the job creation process now accurately reflects the intended quantities for all relevant part numbers ensuring consistency and reliability in MRP outputs.

The issue with saving pre-filter selections in the MRP settings has been resolved. Previously the fields for 'First Bucket Days' and 'Indirect Reqs After' were not retaining user-defined values upon saving. The development team has updated the functionality to ensure these inputs can now be modified and saved correctly while maintaining their default values when the MRP page is initialized. Users can now save their pre-filter settings without needing to re-enter these values enhancing the overall user experience.

A recent update has addressed an issue where the MRP and Forecast grids did not properly reload data after an invalid filter entry was cleared. Previously when users entered an incorrect filter value and then cleared it the left-hand side of the grid would remain blank even though the right-hand side displayed data. The development team has implemented changes to ensure that upon clearing the filter the grid will now correctly reload and display the expected data in both MRP and Forecast views. This enhancement improves user experience by ensuring that valid data is consistently shown after filter adjustments.

Fixed an issue where MRP would not create jobs with 9 digit quantities, which is allowed when creating jobs outside of MRP.

A recent update has resolved an issue where facility part cross reference job increments were not being properly reflected in the Material Requirements Planning (MRP) system. Previously if the job minimum was higher than the maximum on hand the system failed to consider the incremental job quantity leading to discrepancies in suggested values. With this fix the MRP now accurately honors the incremental job quantity ensuring that suggested values are calculated correctly based on the defined parameters.

Fixed an issue where Facility Relationships set on item master records were not being honored when multiple relationships exist and when creating Inter-Company Transfers within MRP.

A recent update has resolved an issue with the pre-staging process where sub-assemblies were not being included on pick lists when both the finished goods job and the sub-assembly job were present. The system now accurately tracks the quantity of produced item parts across jobs ensuring that if there is a shortage it is properly identified. Additionally the calculation of short inventory has been improved particularly when the same item part appears multiple times preventing negative quantities and ensuring accurate reporting of shortages. Users can now expect that when the 'pre-staging docs only' option is selected sub-assemblies will be appropriately reflected on the pick lists.

A resolution has been implemented for an issue where the 'Staged Quantity' field was not updating correctly when switching between iterations during the final staging process. Previously selecting a different iteration did not display the correct staged quantity from the previous iteration due to the system incorrectly referencing the current iteration's records. This has now been corrected ensuring that the 'Staged Quantity' field accurately reflects the total staged quantity after changing iterations.

A recent update has resolved an issue in the Essentials WMS system where scanning a substitute part's UPC code did not correctly pull in the part number during the reservation process for sales orders. The system now ensures that when a UPC is scanned it first attempts to retrieve the corresponding part number before reaching out for substitutes. This improvement enhances the user experience by allowing seamless identification of substitute items ensuring that inventory management is more efficient.

The WMS Move Inventory functionality has been updated to ensure that when inventory is staged to a job the Move From and Move To fields will correctly default to 'Staging - Job'. This change resolves an issue where users received an error message stating 'No inventory found matching the filter' when attempting to move lots that were staged to a specific job. The system now accurately retains the association of the inventory with the job during the move process enhancing the user experience and operational efficiency.

An issue with the expiration date being incorrectly populated when receiving a purchase order using the WMS scanner has been resolved. Previously, the Expires field was set to today's date plus the shelf life value, rather than using the vendor date plus the shelf life. The system has been updated to ensure that the expiration date now accurately reflects the vendor date plus the shelf life, providing more accurate information for inventory management.

An issue was identified where the Warehouse Management System (WMS) displayed incorrect quantities when issuing materials for a job. The problem stemmed from an improper application of the conversion factor between units of measure. This has been resolved by ensuring the conversion factor is applied correctly only when the unit changes. As a result, quantities now display accurately, aligning with the expected units of measure, ensuring consistency between printed records and the WMS scanner.

A recent update has addressed an issue with the Final Staging process in the WMS. Previously when scanning a system lot that matched the default part number the location field would be disabled preventing users from making necessary adjustments. The development team has implemented a fix that clears the location value in the filter allowing the location and user lot combo boxes to remain active and responsive regardless of the part number scanned. This change ensures that users can effectively manage their inventory and select appropriate locations during the staging process.

The functionality for moving inventory in the WMS has been updated to enhance user experience. Users can now successfully utilize the 'Use Entire' dropdown to select 'User Lot' without being prompted to choose a specific system lot. This change ensures that all system lots associated with the same user lot can be moved simultaneously. Additionally two workarounds remain available: canceling the lot chooser will allow the move to proceed or adjusting the inventory option to either 'Lot Controlled' or 'None' will also facilitate the process.

The issue with application identifiers not functioning correctly in the Warehouse Management System (WMS) has been resolved. Previously the system was incorrectly placing serial numbers in the serial number field instead of the vendor lot number field and it failed to populate the vendor date. After development efforts the application identifiers have been remapped to ensure that the correct fields are filled upon scanning vendor labels. This fix has passed internal quality assurance testing confirming that both the user lot and vendor date fields are now populated accurately as expected.

A recent update has resolved an issue with label printing in the WMS system where the quantity printed did not reflect the user's input. Previously, regardless of the quantity specified, only one label was printed when using a physical printer. The development team adjusted the logic that determines how labels are processed and printed, ensuring that the quantity specified by the user is now accurately reflected in the printed output. This fix enhances the functionality of the input production process, providing a more reliable user experience.

Fixed an issue where the Location sequence was not included as part of the sort order when using the Pre-Stage Sales Order transaction in the WMS application.

A recent update addressed an issue in the Warehouse Management System (WMS) where the 'Completing' field was not automatically populating with the default finish quantity during production input. This functionality was already working correctly in the main application but required alignment in WMS. Following the resolution the 'Completing' field in WMS now correctly defaults to the 'Default Finish Qty' specified in the Item Master ensuring a consistent user experience across both platforms.

A resolution has been implemented to address an error encountered when receiving multiline intercompany transfers in the WMS system. Previously users faced a 'KeyNotFoundException' error which prevented them from completing the receipt process. This issue arose due to simultaneous access by multiple users and the handling of temporary records in the transaction list. The development team has made necessary adjustments to ensure that users can now receive multiline intercompany transfers without encountering unexpected error prompts thereby enhancing the overall functionality and user experience.

A recent update has resolved an issue where Maintenance Repair Operations (MRO) jobs were not displaying on the Master Production Calendar (MPC). Previously the options for order types were restricted based on the selected report type which prevented MRO jobs from appearing. With the latest changes users will now see 'Maintenance' as an available option alongside 'Production' and 'All' when selecting the appropriate report types. This enhancement ensures that both Production and Maintenance jobs including their associated details are correctly populated on the calendar.

Fixed an issue where the quantities for related Maintenance jobs were not summing correctly.

Fixed an issue where QC data for Produced Assemblies lots was displaying differently on the COA printed from sales orders vs the same COA printed from a lots report.

Fixed issue where the final staging pick list was repeating short ordered items.

Fixed an issue where the local printer was not retained as the default after logout /login using the Deacom Local program.

Fixed an issue where the correct vendor contact was being applied when the Copies to Print form loads.

Fixed an issue where the incorrect Report Layout was being displayed for editing when multiple Report Layouts exist for the same system report.

An issue was identified where users experienced errors when attempting to print part forms to multiple printers after an upgrade. The error occurred specifically when printing to different printers with quantities greater than zero. The development team investigated the issue and found that the printing logic needed to be updated to ensure that only the currently processed JSON file is deleted during printing. Following this update users were able to successfully print document groups to multiple printers without encountering any errors. This resolution has been verified through testing confirming that the expected functionality is now working as intended.

A recent update has resolved an issue where newly created user reports were incorrectly retaining the same name resulting in confusion when printing or previewing these reports. The system now correctly differentiates between reports by utilizing unique identifiers ensuring that the correct report name is displayed and printed. Users can now generate and print reports without encountering conflicts with existing report names enhancing the overall functionality and user experience.

A recent update has improved the functionality of the Print Substitution feature. Previously users experienced issues where the base report name was incorrectly displayed in the selection list leading to confusion when adding or modifying print substitutions. The resolution involved ensuring that the correct value is set for the Base Report input preventing mismatches with the Substitution Type input. These adjustments ensure that only valid options are presented enhancing the overall user experience when managing print substitutions.

A recent update has improved the printing functionality from the sales order reporting feature in the Cloud environment. By implementing a static variable the system now initializes the PDF printer only once which enhances performance and prevents errors related to printer selection. This change ensures that users no longer encounter unexpected prompts during printing. Testing confirmed that the issue has been resolved and users can now print sales orders without any interruptions.

An update has been implemented to enhance the printing process for large grids addressing an issue where users experienced timeout errors when printing. The modifications include adjustments to the communication between the application and the Cloud Local printer specifically by introducing a pause mechanism to improve request handling. As a result users can now print large grids without encountering errors ensuring a smoother and more reliable printing experience.

A recent issue with the mass printing of customer statements has been resolved. Previously users experienced interruptions in printing when attempting to process large batches of statements which required a restart of web services to restore functionality. The problem was traced back to changes made in a prior update that affected the printing logic when multiple tasks were executed simultaneously. The development team has reverted these changes allowing for smoother printing operations without the need for service restarts even for large volumes of statements. This fix has been validated through internal testing confirming that customer statements can now be printed efficiently.

A recent update addressed an issue that caused an error when printing sales labels for multiple lots after entering variable data such as gross tare and net weights. The error occurred due to duplicate key entries in the system which were resolved by ensuring that each entry received a unique identifier during the printing process. This fix has been implemented and users should no longer experience errors related to label printing allowing for a smooth and accurate generation of sales labels.

An issue with printing lot labels to PDF via the Inventory Lots grid has been resolved. Previously when the part form name contained invalid characters users encountered an error and the PDF was not generated. The system has been updated to sanitize part form names allowing users to print labels to PDF without experiencing errors even when the names contain special characters. This enhancement ensures that users can successfully generate PDF labels without interruptions.

A recent update has resolved an issue where printing documents to PDF after viewing them on screen resulted in separate PDF files for each page. The system now generates a single PDF file that includes all pages when printing from the view report form. This improvement enhances the user experience by streamlining the process and reducing the time spent on printing multi-page reports.

Fixed an error that occurred when printing job pick lists from Inventory > Pre-Staging with the 'Docs Only / Do Not Stage' flag checked.

A recent update has resolved an issue with the MatBom2 form layout where users encountered duplicate element warnings when attempting to modify toolbar items. The underlying condition that restricted modifications to existing toolbar elements has been adjusted allowing for successful changes without triggering duplicate messages. Users can now add or remove buttons and events within the MatBom2 layout without any complications enhancing the overall functionality and user experience.

Fixed an issue where jobs where relieving lots back into, instead of out of inventory.

Fixed an issue where co product jobs were not pulling in the correct BOM revision when creating line jobs. (AI Note - An update has been made to ensure that co-product jobs correctly pull in the necessary revisions when creating line jobs. Previously, items required for co-products were not appearing for issuance unless the job was manually adjusted. The development team resolved this issue by modifying the query responsible for calculating the co-product quantities, ensuring these quantities are correctly set when the job is saved. This prevents filtering issues during the issuance process due to missing quantities. Additionally, duplicate quantity lines have been removed to streamline the process. Users will now find that all necessary items appear correctly for issuance when a job is created from a sales order line.)

A recent issue with the NewJob1 form layout where users encountered a prompt when switching to child forms has been resolved. The problem arose due to an incorrect number of parameters being passed in the system's function handling form interactions. By adding an additional parameter the system now correctly processes the interactions preventing any prompts from appearing and ensuring that data entered in child forms is retained when returning to the NewJob1 layout. This fix has been validated and is expected to enhance the user experience moving forward.

A recent update has resolved an issue with the calculation of co-product quantities in Bills of Material (BOM). Previously the system was only evaluating the co-product quantity from the first line of the BOM leading to inaccurate totals when other lines contained values. With the new changes the system now correctly sums the co-product quantities from all lines in the BOM ensuring accurate calculations regardless of the order of the lines. This enhancement improves the reliability of user-defined calculations related to co-products.

A recent update has resolved an issue where the system incorrectly set the Issue Increment Type to 'Expression' when importing BOM lines from an Excel sheet. Previously if the Excel file did not specify a value for this field it was interpreted as a blank space causing the default value rule to fail. The code has been updated to ensure that if no value is provided during the import the system will default to 'Fixed' as intended. Users can now import BOMs with the correct increment type set to 'Fixed' without any discrepancies.

The issue with the Job Pick List displaying duplicate lots and quantities has been resolved. Previously the report was incorrectly duplicating rows instead of properly splitting them according to the Bill of Materials (BOM) sequence. The development team implemented improvements to the AllocateLots function ensuring that the pick list now accurately reflects unique lot assignments without any repeated information. Users can expect the Job Pick List to show the correct number of lines for parts with split quantities across lots providing a clearer and more accurate representation of the required information.

The issue related to incorrect quantity calculations in the Implosion / Indented BOM report has been resolved. Previously certain components were displaying inflated quantities due to the application of incorrect conversion factors. The development team has updated the logic to ensure that when generating Implosion reports the correct unit identifiers are utilized leading to accurate quantity displays.

The system has been updated to correct issues related to the creation of line jobs for items with defined job maximums. Previously when the 'Split Jobs By Job Qty' option was enabled the system was incorrectly duplicating line items resulting in multiple jobs with the same quantity. This has been resolved ensuring that when this option is checked jobs will now split according to the job maximum until the full order requirement is met. Additionally if the 'Split Jobs By Job Qty' is unchecked the system will now correctly generate a single job that reflects the total order quantity. Furthermore the security settings governing the creation of jobs for quote orders have been refined to ensure that permissions are properly enforced.

A recent update has resolved an issue where notes added to Custom Adds were not being saved correctly. Modifications were made to ensure that notes entered during job modifications are now properly stored regardless of whether they are associated with original lines or new entries. Users can now confidently add and save notes in Custom Adds ensuring that all changes are recognized and retained in the job header.

A recent issue where adding additional lines to routing sequences resulted in overwriting earlier entries has been resolved. The development team identified that the existing fix inadvertently caused inconsistencies due to the routing screens operating with two cursors. The corrective action reinstated the previous functionality ensuring that users can now create and manage multiple routing sequences without any loss of data. Users can add and rearrange sequences seamlessly confirming that the system behaves as expected.

A recent update has resolved an issue that prevented users from creating non-WIP jobs. The underlying logic for checking inventory for non-WIP jobs has been improved to ensure that it accurately reflects the current inventory status. Previously the system was incorrectly identifying negative inventory as an obstacle to job creation. With the new changes users can now successfully create non-WIP jobs without encountering prompts related to issued inventory. This enhancement streamlines the job entry process and improves overall functionality.

Enhanced system so that Item Master fields are honored as pre-filters on the Work Center Capacity report.

Fixed an issue where item facility burden and labor costs were not being considered when the item facility "Use Costs" flag was checked.

Fixed an issue where co-product lines were not being displayed when using the View Detail button in Job Reporting.

A resolution has been implemented to address an issue where certain pallets were not transitioning to the completed status in the AutoFinisher application. The development team identified that resending the same query tool result was causing the problem. To resolve this a unique identifier (GUID) is now being used for message tracking and a flush has been added to the stream to improve processing. Following these updates all pallets are now successfully created without getting stuck or failing ensuring a smoother operation for users.

A resolution has been implemented to address an issue in the Auto Finisher application where changing the dropdown to 'All' on the Units tab after finishing cases resulted in an error message regarding invalid revision yield. The development team identified that the problem stemmed from resending the same query tool result. To resolve this the system was updated to utilize a generated GUID as the message ID and included a flush to the stream. Following these updates it was confirmed that the error no longer appeared when switching the Failed field from None to All ensuring that all pallets are correctly created without displaying incorrect error messages.

A resolution has been implemented to address delays experienced in the AutoFinisher application regarding pallet finishes. Previously there was a noticeable lag between pallets appearing in the system and the AutoFinisher reflecting their completion status which could take several minutes. The update ensures that pallet finishes are now processed and displayed in a timely manner aligning the AutoFinisher's status updates with the inventory records in the main application.

The Master Production Calendar in Week View has been updated to accurately reflect the availability of work centers. Previously there were discrepancies in the blackout areas indicating unavailable days particularly on Monday Tuesday and Friday. The issue was resolved by correcting the calculation for the width of the blackout elements in the calendar display. Following this fix the calendar now aligns correctly with the work center's availability settings ensuring that any modifications to availability hours are properly represented.

The issue with Labor and Burden COGS accounts posting to incorrect accounts has been resolved. The system has been updated to ensure that the correct account overrides are applied when shipping a sales order. This change ensures that the Labor and Burden COGS accounts now match the designated accounts as intended providing accurate financial reporting. Users can expect to see the correct postings reflected in the system following this update.

A recent update has addressed an issue where the burden account was incorrectly applied when editing time entries from an active job to an inactive job. Previously switching jobs would retain the burden account from the active job leading to inaccuracies in payroll reporting. The resolution involved implementing a new function to ensure that the burden account is updated correctly when the operation changes. This enhancement ensures that only the relevant accounts are reflected in payroll entries improving the accuracy of financial reporting.

The issue regarding user access to edit workers in the production environment has been addressed. Previously users without the appropriate permissions were able to edit worker details which posed a security risk. The development team has implemented a check within the system to ensure that only users with the correct 'Production - edit workers' access can make edits. This change has been successfully validated confirming that users without the necessary permissions are now correctly restricted from editing worker information.

An issue was identified where header job quantities were not populating correctly when the 'Synchronize Job Quantities To Linked Sales Orders' option was unchecked. This resulted in header jobs and their sub-assembly line items displaying a quantity of zero. Additionally changes to the sales order quantity did not reflect accurately in the sub-assembly quantities of the header job. The development team has implemented changes to ensure that header jobs are created with the correct quantities for both finished goods and sub-assemblies regardless of whether the synchronization option is enabled. Furthermore when the synchronization option is unchecked updates to a sales order's quantity will no longer affect the header job's quantities resolving the previously reported issues.

A recent update has resolved an issue where linked jobs were incorrectly updating the sales order's Due to Ship date. Previously modifications to the planned finish date of a job were affecting the Due to Ship date instead of the job due date. With this fix changing the job's due date will correctly update the sales order's Due to Ship date while changes to the planned finish date will no longer impact it. These adjustments ensure that the system behaves as expected enhancing the accuracy of job and sales order management.

The system has been updated to address an issue where re-phasing sales order lines did not remove the lines from the original job resulting in duplicate job lines. The modification ensures that when lines are reassigned to a different phase they are properly cleared from the original job. This change improves the accuracy of job line management and prevents confusion caused by duplicate entries.

The issue with the incorrect creation of header and line jobs when the sales order quantity is less than or equal to the job maximum has been resolved. Previously the system was generating multiple jobs instead of a single job as expected. Now when the sales order quantity is less than or equal to the job maximum the system correctly creates one job reflecting the appropriate quantity. Additionally when the sales order quantity exceeds the job maximum it accurately splits the quantity into multiple jobs based on the defined job maximum and minimum values. This enhancement ensures that job creation aligns with the intended operational logic.

The freight calculation process has been updated to exclude non-stocked items when total freight is applied on purchase orders. Previously non-stocked items were inadvertently included in the freight cost distribution leading to inaccuracies in the lot cost calculations. With this resolution only stocked items will be considered ensuring that freight costs are allocated correctly. Users can now expect accurate cost calculations reflecting only the stocked items when processing freight on purchase orders.

The INLIST function in Workflow visibility expressions has been restored to full functionality. This update ensures that workflows will now correctly populate in the Purchase Order Entry allowing for smoother operations and user training ahead of the upcoming Go Live date. The resolution involved adjustments to the ExpressionResult class which now accurately compares properties to prevent errors in workflow processing. Users can expect improved reliability and ease of use with the updated workflows.

A recent update has addressed an issue where users were able to exceed the blanket purchase order quantity when releasing or reactivating canceled purchase orders. The system now enforces a check to prevent any additional orders from being saved that would surpass the established blanket limit. This enhancement ensures that once the blanket quantity is fully utilized any attempts to modify or add new orders will prompt a notification effectively blocking the action. As a result this change improves the accuracy of blanket purchase order management and minimizes the risk of overages.

A recent update has resolved an issue where inactive workflows continued to appear on purchase orders despite being deactivated. The system now correctly prevents any inactive workflows from being included in new records ensuring that only active workflows are displayed for vendor assignments. This change enhances the accuracy of workflow management within the purchasing process providing a more streamlined and reliable experience.

The issue with the Summary page not printing as a separate page has been resolved. Users can now successfully print the Summary page along with the Terms and Conditions when generating Purchase Order reports. To ensure the Summary page prints correctly users should enable the 'Include Page Footer with Summary' option in the report properties. This change allows the system to recognize and print pages that include a footer addressing the previous problem where the Summary page was ignored if it was set to print separately.

The issue where the vendor's email address did not populate when emailing document groups has been resolved. The development team identified that the necessary properties for loading the vendor's email and subject were not being correctly utilized during the document group printing process. By updating the method to include these fields the vendor's email now populates as expected in the email form when sending document groups.

A technical issue that caused an error when accessing Blanket Releases after filtering Blanket Purchases by item has been resolved. Users can now successfully navigate from the Blanket Purchases report to the Blanket Releases section without encountering any errors even when using the 'Item Starts With' filter. This improvement enhances the overall user experience and ensures smoother operation within the purchasing module.

A recent update has resolved an issue in the purchase order entry process where the job number was not consistently populating in the system when moving to the next line. Previously when a job number was entered on the purchase order header it would populate correctly for the first line but not for subsequent lines. With the latest changes the job number now automatically carries over to all lines as expected ensuring a smoother and more accurate order entry experience.

A recent update has resolved an issue related to handling customer returns during the Quality Control (QC) process. Previously items with a job number of zero which indicated they had been moved after receipt were incorrectly displayed in the QC Results Entry preventing the completion of QC for returned items. The development team has removed these lines from the display ensuring that only relevant items appear in the QC Results Entry grid. This change allows users to complete the QC process for returned items without any hindrances.

A resolution has been implemented to address an issue where certain pallets were incorrectly marked as failed while still appearing in the inventory system. The development team updated the process to utilize a generated identifier for messages and incorporated a flushing mechanism to ensure proper data handling. Following these modifications the system was tested under the usual operational conditions confirming that failed pallets no longer appear in the inventory as expected.

A recent update has resolved an issue where users experienced invalid username and password prompts when attempting to perform e-signatures after logging in with SSO credentials. The changes ensure that users not enforced to use SSO can successfully approve QC results using their Deacom username and password while those required to use SSO will be prompted to authenticate via their Azure account. Additionally the Azure App ID and Tenant ID fields have been removed from the configuration streamlining the authentication process. This enhancement is expected to improve user experience by ensuring proper functionality for both SSO and non-SSO users.

Fixed an issue where the complete lists of QC tests was not displaying in grids when using the "QC Values" button via Job Reporting > Job Detail.

Fixed an issue where QC results for returned lots (lots shipped on negative sales orders) were being duplicated on the Certificate of Analysis form.

A recent update has addressed an issue where editing a Quality Control Group and selecting 'No' when prompted to update all current jobs inadvertently reset the workflow on associated Bills of Material (BOMs). The logic governing this behavior has been corrected to ensure that selecting 'No' retains the completed workflow sequences. Following this change the workflows remain intact as expected and the issue is no longer reproducible.

Fixed issues with Stability Testing feature not recognizing the last QC Test date. Two major changes were done:

• First, an issue was identified where modifying a lot, such as updating its expiration date, disrupted the stability testing process. That was corrected by ensuring that all lots were included in the check, regardless of the last action.
• Second, the method for gathering the date to be used for stability testing was updated to ensure that it uses the date the lot was released from QC pending.

In the latest update, the payment processing system has been enhanced to allow credit cards to be used even if their billing addresses do not match the bill-to address on file. This change enables greater flexibility for users when saving and utilizing credit cards during transactions.

A recent update has addressed an issue in the Sales Order entry process where users could inadvertently close the Order Entry tab without saving changes made to feature options. A confirmation prompt has now been implemented to alert users if there are unsaved changes before closing the tab. This enhancement ensures that modifications are not lost improving the overall user experience during order modifications.

A recent update has addressed an issue where tax amounts in the system were occasionally inconsistent with the Avalara portal showing a discrepancy of one cent. After extensive investigation and testing the development team confirmed that the tax values now remain consistent throughout the order process from entry to shipping and invoicing. This resolution ensures that the tax line reflects a stable value aligning with the Avalara calculations.

An issue with exporting reports to Excel has been resolved where numerical fields were incorrectly formatted as text. This problem arose when numbers lacked specific formatting characters which prevented them from being recognized as numerical values. The development team has updated the parsing logic to ensure that integers are properly exported as numbers regardless of their format. Users can now expect that all numerical values in exported Excel files from sales order reports will be correctly formatted enhancing data accuracy and usability.

The issue with receiving an error message when using the Sales Order Header user field in custom criteria for the Order Detail Report has been resolved. Users can now successfully filter sales orders using custom criteria based on sales header fields without encountering any SQL errors. This improvement ensures a smoother reporting experience and restores functionality that was previously available in earlier versions.

A recent update has resolved an issue where users were encountering errors while modifying sales orders if they did not have specific permissions set. Previously the system incorrectly prompted for job minimum quantities even when no jobs were linked to the sales order. With the new changes users can now modify and save independent sales orders without receiving these prompts regardless of their permission settings related to job quantities. This enhancement streamlines the order modification process and improves user experience.

Fixed an issue where the "Reset" button on sales order entry was not clearing line user fields.

Fixed issue where certain sales order user calcs weren’t calculating correctly.

The Allocation Fulfillment report has been updated to ensure that the sorting order is correctly applied. The report will now sort by Part Number Due to Ship date and Priority as intended. This enhancement improves the accuracy of the report allowing users to view the due to ship dates in the correct order when generating the report.

Optimized the saving sales order logic to minimize the number of times the Order Calculations process is called and run.

A recent update has resolved an issue with the display of deal pricing descriptions in the system. Previously when copying imported deal pricing the description field was incorrectly populated with a numerical value instead of the expected name. The development team has implemented a validation to ensure that the appropriate deal pricing description is set correctly. Now when a deal is copied if the deal is applicable to all items the system will correctly assign 'All Items' to the description field improving clarity and accuracy in deal pricing records.

A recent update addressed an issue where newly selected feature options were being lost on sales orders when the sales order lines were recalculated prior to saving. The development team implemented a solution that ensures these feature options remain intact during the recalculation process. By utilizing temporary feature values instead of relying solely on database entries the integrity of the selected features is preserved providing a smoother user experience when modifying sales orders.

A recent update has resolved an issue where the Line Level Detail report in the Calculate Commissions and Rebates feature was only displaying the first line of an order when all lines of the order should be displayed. The fix ensures that all commissionable lines are now correctly displayed in the report when the report type is set to Line Level Detail. This change addresses a filtering oversight that occurred during the migration process and the report has been validated to confirm that it now accurately reflects all relevant lines for sales orders.

The sales calculations process has been enhanced to ensure that when users modify options on sales order lines the calculated prices for those lines are updated accordingly. This improvement prevents the overwriting of existing calculation values allowing for accurate reflection of changes made during the order modification process. Users can now expect the 'House Sale Tax' price to correctly align with the updated feature options ensuring a smoother and more accurate sales order experience.

Fixed an issue with prices being automatically zeroed out when changing the quantities on sales orders or quotes.

A recent update has improved the email functionality when sending invoices from the Sales Order Summary screen. The system now correctly prioritizes the email address selected by the user ensuring that it overrides any previously cached email addresses associated with other contacts. This enhancement resolves an issue where an incorrect email address would auto-populate providing a more accurate and efficient invoicing process for users.

A recent update has resolved an issue where payments on account could not be processed if certain search fields were missing from the Ship-to customer. Previously users encountered an error when attempting to create a payment on account without these fields populated. The development team has implemented a solution that now allows payments to be processed regardless of the presence of these fields. This enhancement mirrors the existing functionality for sales orders ensuring a smoother transaction experience.

A fix has been implemented to ensure that feature notes in the sales order entry clear appropriately when switching from a child feature to its parent. This change addresses an issue where notes entered on child features would remain visible and editable when selecting the parent feature which was not the intended behavior. Users can now expect that any notes will be disabled and cleared upon selecting a parent feature enhancing the overall user experience.

The system has been updated to ensure that the General Ledger (GL) Override assigned to Sales Representatives is correctly applied during commission postings when an order is invoiced. Previously the override was not reflected in the commission postings leading to discrepancies in account assignments. After implementing the necessary adjustments the GL Override now successfully updates the relevant account positions to reflect the expected values during the invoicing process. This enhancement is expected to streamline financial reporting and improve accuracy in commission calculations.

A recent update has resolved an issue where Restricted Selling Groups were not properly enforcing start and end dates affecting the ability to link these groups to billing records. Now items categorized as restricted will only be available for sale within the designated date range for the associated customer ensuring compliance with the restrictions set in the selling groups. This enhancement also ensures that multiple restrictions can be effectively managed when adding items to a sales order improving overall functionality and user experience.

The issue with incorrect commission calculations when the display currency differs from the source currency has been resolved. Previously commissions were calculated based on the home currency instead of the currency used in the sales order leading to discrepancies in reported amounts. Adjustments were made to ensure that the commission calculations are now based on the correct values from the sales order currency resulting in accurate commission reporting.

A recent update has resolved an issue in the sales order entry process where an error was generated when recalculating prices after changing the price class. The system now accurately synchronizes the sales order data ensuring that both the order ID and product ID are correctly matched during the recalculation. This enhancement prevents duplicate errors and ensures that sales order prices are recalculated effectively based on the pricing hierarchy and order configuration eliminating any errors in the process.

A recent update has resolved an issue where only FedEx Ground shipping options were available when using EasyPost for FedEx shipments. Previously other expedited services were not displayed leading to shipping delays. The resolution involved modifying the system to prevent an unnecessary division in the parcel weight calculation which had previously rendered most FedEx options unavailable. Following this fix users can now access a full range of FedEx shipping methods including expedited services ensuring a more efficient shipping process.

A recent update has addressed an issue where a specific error was generated in sales order reporting upon modifying a sales order line. The resolution involved adjusting the calculation of a user-defined field (UDF) to ensure that its value does not exceed the maximum character limit. This change prevents the error from occurring when the sales order line is modified allowing for smoother operations without interruptions. Users should now be able to modify sales order lines without encountering any related errors.

A recent issue preventing the deletion of sales tax regions from sales orders has been resolved. The underlying logic that managed tax regions was adjusted to ensure that users can now successfully remove all tax regions from an order. This fix allows for the addition updating and complete removal of tax regions without any errors ensuring smooth functionality when modifying sales orders.

A resolution has been implemented to address an issue where a specific DXA file import resulted in an error stating that the part number was not found. The development team modified the import functionality to ensure that part numbers are correctly recognized when processing DXA files. Following this update users can now import the affected DXA files without encountering the previous error streamlining the order entry process.

A fix has been implemented to address the issue where commission calculations were being incorrectly multiplied when multiple payments were applied to a sales order. The system now ensures that commissions are calculated only once per order regardless of the number of payments made. This change improves the accuracy of commission reporting and ensures that commissions are based solely on order details rather than being influenced by the number of payments processed.

A recent update has resolved an issue that prevented users from short shipping a sales order without generating an error message. Previously an exception occurred during the shipping process when the system attempted to verify promotional lines leading to the message 'Sequence contains no matching element'. The development team implemented a null validation in the shipping method ensuring that users can now successfully short ship orders without backorders and without encountering any incorrect prompts.

Fixed an issue where changing a bill-to/ship-to during sales order entry or modification would not change the Shipping Account to match the new bill-to/ship-to selection.

A recent issue causing a crash when adding line items to sales orders has been resolved. The fix involved adding a condition to check for a null variable in the system's expression processing function. This adjustment prevents errors from occurring when users attempt to add items ensuring a smoother experience during order entry. Users can now add line items without encountering any issues.

Fixed an issue with the Sales > Customers pre-filter where users restricted to a specific sales rep were seeing other sales rep information when running the filter with the 'Sales Rep Filter' set to 'All'.

Fixed an issue with the Sales Order Allocations/Simple report not generating correctly.

Fixed an issue where order history was no longer displaying after document has been emailed.

The functionality for credit card reauthorizations has been enhanced to allow users to perform these actions directly from the Order Entry form and the Credit Card Authorizations report. Users can now reauthorize credit cards for existing sales orders seamlessly, with confirmations indicating successful reauthorizations. Additionally, when the payment terms of an order change, a prompt will notify users that the existing authorization will be voided, ensuring that new terms are applied correctly. This improvement streamlines the process and ensures that credit card authorizations are managed effectively.

Fixed an issue where modifying the Ship-To on a line within a Master Order was incorrectly changing the Ship-To on the Master Order header section.

Fixed system logic so that when un-shipping, then re-shipping a sales order with an existing backorder, any prepayment amounts are evaluated and applied correctly.

The issue where the Clear icon on the Sales Order Line Entry Feature form did not remove the selected package option from the feature list has been resolved. Previously when the Clear option was selected the feature status changed but the corresponding package remained visible. With the recent update pressing the Clear button now correctly removes the selected feature from the list ensuring that the interface accurately reflects the current selections.

Voided pre-payments that were previously appearing on the Pre-Payment Summary report will no longer be displayed if they were voided on a different date than the original payment. This change aligns the report with our documentation ensuring that only relevant transactions are shown. Additionally if multiple pre-payments are made for an order on different dates they will now be aggregated into a single line on the summary report providing a clearer overview of the payment status.

A recent issue that caused an error when invoicing orders associated with active commission rules has been resolved. Users can now successfully invoice and print sales orders without encountering any error messages when active commissions are present. This improvement was achieved by adjusting the invoicing process to utilize the correct data fields ensuring smoother transactions for users.

Enhancements have been made to allow the Essentials platform to access bill-to and ship-to facility records. This update facilitates the management of facility restrictions under the billing section, ensuring a more streamlined process for users. Specifically, licenses have been removed from certain forms and grids, while new licenses have been added to enhance functionality for the DSD category. These changes aim to provide a baseline functionality for Essentials users, ensuring they can effectively manage facility-related tasks.

The recent update has improved the scanning functionality for lot labels within the DSD application. Users can now successfully scan lot labels using both DataWedge and Honeywell devices which allows for the accurate reservation of lots in the system. This enhancement streamlines the shipping process by ensuring that lot information is correctly captured and displayed when processing orders.

A recent update has resolved an issue where part numbers and descriptions were not being imported correctly into the forecast grid. This fix ensures that when a forecast is loaded the system will not attempt to process grid row colors for empty rows which previously caused errors and prevented the grid from fully loading. Additionally users can now successfully add new elements to the layout without encountering errors. The update enhances the overall functionality of the sales forecast import feature ensuring a smoother user experience.

A correction has been implemented to address an issue where sales orders paid with split payments were incorrectly flagged as cash sales in the Cash Register system. Previously the system did not accurately reflect the cash status of these transactions which could lead to confusion in order history. The development team has modified the payment processing logic to ensure that when split payments are entered the cash status is correctly marked as 'Yes' in the sales order records. This update enhances the accuracy of financial reporting and improves the overall user experience.

An issue with the POS Reconciliation process has been resolved. Following a recent update the starting balance was incorrectly displaying as $0.00 instead of reflecting the ending balance from the previous reconciliation. This has now been corrected ensuring that the starting balance accurately pulls from the last recorded ending balance allowing for a seamless reconciliation process. Users can expect the reconciliation form to function as intended displaying both the starting and ending balances correctly.

The issue with the temporary license expiration warning blocking the cash register from loading has been resolved. Previously users encountered a blank screen when logging into the POS system due to this warning. The development team implemented a fix that allows the cash register to load normally even when a license expiration warning is present. This improvement ensures that the cash register functionality remains accessible allowing users to continue their operations without interruption.

Changed how Deacom initializes and shuts down the Topaz signature pad to make the integration more robust

In Version 17 an issue was identified where a Salesfeat (Sales Features) report would not print if no feature selection was made during the sales order entry process for feature item types. This behavior was inconsistent with Version 15 where the report could still be printed even without a selection. The development team has resolved this by ensuring that the Save button is enabled by default on the feature selection form allowing the report to be printed regardless of whether a feature is selected. This change has been successfully implemented and verified enhancing the functionality for users entering sales orders.

A recent issue that caused an error when selecting 'Next' on the add endpoint form in the Features setup has been resolved. The problem stemmed from an incorrect row filter which has now been fixed to ensure proper functionality. Users can now proceed through the form without encountering any errors allowing for a seamless experience when adding endpoints.

A resolution has been implemented for an issue where updates to the 'Feature notes' field on the Sales Order Feature form did not reflect correctly at the top of the form. Now when users modify the quantity or notes of a feature both the grid and the header fields will update accurately to show the latest changes. This improvement enhances the overall user experience by ensuring that all relevant information is consistently displayed.

The Feature Override grid has been updated to ensure it refreshes correctly after a filter is cleared. Previously users experienced an issue where the grid did not refresh resulting in a stuck filter display. With the recent development changes this functionality has been resolved and the grid now refreshes as expected after the filter is cleared enhancing user experience and efficiency.

The issue with the feature inclusion form displaying ID numbers instead of the Parent and child values has been resolved. This was due to a handling error in the methods responsible for loading these values. The development team has updated the code to ensure that the correct values are returned allowing users to see the appropriate names instead of numeric identifiers when modifying inclusions or exclusions. After implementing this fix the system now works as intended maintaining the correct display of feature names throughout the process.

The issue where sales order lines would not update correctly after a linked job was cancelled has been resolved. Previously when a job was cancelled the sales order still displayed a link to the job and a new job was unintentionally created even if the 'Create Line Job' checkbox was not checked. The development team has modified the system to ensure that when a linked job is cancelled the association is removed from both the job and sales order preventing the creation of new jobs under these circumstances. This enhancement ensures that users can save sales orders without inadvertently generating linked jobs.

An issue was resolved where the quantities of job lines linked to sales orders were incorrectly updated when alternate revisions were used. Previously modifying the sales order would cause the sales order line quantity to revert to the default quantity based on the original bill of materials revision rather than maintaining the quantity set for the alternate revision. The system has been updated to ensure that the original quantity is prioritized allowing for consistent tracking of quantities even after changes to the sales order. This fix enhances the accuracy of job line quantities when using alternate revisions.

Modifications have been made to the system to ensure that when a sales order is linked to a closed job any subsequent modifications to that sales order will no longer trigger the creation of a new line job. This change addresses an issue where users experienced the unintended creation of additional jobs when attempting to update closed orders. The updated functionality now accurately reflects the status of linked jobs preventing unnecessary job creation and streamlining the order modification process.

A new feature has been introduced to enhance the automation service for load balancers allowing it to run automated processes concurrently without triggering duplicates. This is achieved by adding a settings file that controls the execution of automated processes. Users can now modify the configuration to enable or disable the automation triggers as needed ensuring more efficient management of automated tasks. After making changes to the settings file a restart of the service is required for the updates to take effect.

A resolution has been implemented to address an issue where emails sent from the system were incorrectly populating recipient addresses. The root cause was identified as inconsistencies in how different versions of the PrintPODocument function handled email addresses and subjects when generating emails for invoices. The development team has ensured that all versions now correctly reference the appropriate email address associated with the selected customer thereby eliminating the risk of sending sensitive information to unintended recipients. This fix has been validated in the latest build ensuring that emails generated will now consistently reflect the correct recipient information.

In version 17.04.005.0001 of the Data Tool an issue was identified where users could not select specific imports for deletion when using the View History feature resulting in the unintended deletion of all records associated with a table. This change was particularly burdensome for users managing multiple loads as it required reloading all data rather than just the targeted records. The issue has been addressed by refining the deletion process ensuring that only the selected records are deleted not all associated data. Additionally improvements were made to the View Detail functionality to enhance user experience when managing large datasets.

A recent update has restored the functionality for entering partial dates in the system. Users can now type a date in 'MMDD' format such as '0101' and upon pressing the tab key the system will automatically populate the full date including the current year (e.g. '01/01/2025'). This change addresses feedback from users who experienced issues with the previous method of date entry where a full six-digit format was required. The system has been tested and confirmed to work as expected.

A recent update has resolved an issue with the Data Tool where multiple destination expressions were being displayed for certain fields leading to confusion during data imports. The development team has implemented a solution to prevent the duplication of the first field when importing data profiles that contain multiple sources. This change ensures that only unique destination expressions are recorded enhancing the accuracy of data handling and improving overall system reliability.

An issue was identified in the item master form where modifying the facility incorrectly displayed the wrong location type and location allowing users to save erroneous data. This occurred due to a lack of proper filtering in the searchbox which resulted in all location types being pulled instead of just those relevant to the facility. The development team has implemented a fix to ensure that the correct location type is displayed and that the searchbox filters refresh appropriately when navigating through options. After these adjustments the functionality now works as intended providing users with the correct location information upon saving.

The User Inactivity Days feature has been updated to ensure that accounts are locked out after the specified period of inactivity. Previously the system did not properly enforce the inactivity days setting allowing users to remain logged in despite exceeding the inactivity threshold. The recent changes correct this by implementing a check that accurately evaluates whether the last login exceeds the allowed inactivity days. When the condition is met the system will now lock the user account and display a notification regarding the last login.

The email configuration process has been updated to enhance user authentication capabilities. Previously users experienced issues with email sending when using LDAP as the system did not utilize the correct password stored in the Email Password field. The resolution ensures that the system now correctly references this password for user email accounts allowing for successful email transmission regardless of LDAP settings. This change simplifies the authentication process and improves overall functionality.

An update has been implemented to address an error encountered when upgrading to version 17.03.007. The system now successfully processes updates without displaying errors related to the UpdateAPIProfiles functionality. This improvement was achieved by modifying the underlying database calls allowing for better handling of deprecated fields during the update process. Users can confidently proceed with the upgrade to version 17.03.007 without encountering the previous issues.

The recent performance enhancements have resolved issues related to system slowness experienced in the live environment. Previously multiple cache objects were created without proper disposal leading to performance degradation. The system has been optimized by ensuring that cache objects are created only once per company database significantly improving retrieval speed. Additionally the underlying data structures have been updated to facilitate faster access. Users should now experience a smoother and more responsive system.

The Data Tool has been updated to ensure that the QC Test Group field is correctly marked as required when the destination is set to Quality Control Group Tests. This change addresses an issue where the field was not displaying as required which could lead to profile failures for users exporting templates. With the new updates the QC Test Group field will now appear in blue indicating its required status both when creating records manually and when using the import data tool.

Fixed an issue where favorites were repeating when using the auto-export feature in Deacom.

The system has been updated to enhance user session management by addressing frequent logouts experienced in versions 17.02.015 and 17.02.017. Previously users were logged out after three minutes of inactivity due to browser throttling of JavaScript timers. The new implementation ensures that users will remain logged in for their configured timeout duration which can be set to 30 or 60 minutes before being logged out due to inactivity. This change allows for a more user-friendly experience by aligning the logout process with individual user settings thereby reducing unexpected disconnections.

A recent update has resolved an issue with printing multiple copies of reports to PDF in Version 17. Previously when users attempted to print reports with a specified number of copies only the first copy would print if the report layout did not include certain variables. The development team has now ensured that the specified number of copies will always print regardless of the report layout. This enhancement streamlines the printing process and aligns the functionality with expectations set by earlier versions.

Improved system stability and performance by adding a dedicated SQL connection to handle inactive sessions/inactive logins.

Fixed an issue with the help system not launching when using the About > Help button in the application.

A recent issue related to importing Excel spreadsheets exported from the Lots report has been resolved. Users will now be able to successfully import modified reports back into the system, provided they adhere to the required header format. A code adjustment was made to ensure that the data conversion process functions correctly, eliminating previous errors associated with incorrect column names. Users are reminded to maintain the specified schema for headers to ensure seamless imports.

Fixed an issue where the trigger code in SQL was only pointing to the default company database (and not other company databases which may have triggers enabled) when starting and restarting the Deacom automation service or console.

Modified the eSignature process in Deacom to work more seamlessly with Deacom SSO options and existing e-Signature options

• The e-signature form in the system will now display the "Single-Sign On" button if SSO features are enabled via System > Options < Authentication tab.
  • If the user clicks the Single Sign-On button, the SSO window will open for credential verification. If verification is successful, the system will apply the e-signature.
  • If the user does not click the Single-Sign On button and instead enters their credentials, the system will perform the following checks and actions:
    • If the user's record does not have SSO only enabled via System > Maintenance > Users, the system will simply apply the normal eSignature logic and apply the credentials.
    • If the user's record is marked to require SSO, the following prompt will be displayed "User must e-sign via a single sign-on provider".

Fixed an issue where Link Document profiles, set to run automatically, were not running.

The EvoX API profile functionality has been updated. The URL field is now enabled when creating a new EvoX API profile and defaults to the production integration engine environment. Additionally, the 'Test / Sandbox Mode' checkbox is set to false by default.

Added additional exception logging to the data tool to better help troubleshooting during data imports.

Import and Export feature have been added for API Profiles, enhancing usability and functionality. Users can now encrypt XML data during export and decrypt it upon import, ensuring secure data handling. The save button behavior has been improved, and the form fields now populate correctly when importing. Additionally, system profiles will encrypt sensitive information before storing it in the database. The export files will be named based on the API profile name and will utilize a custom file extension, with the capability to update records based on the imported data. This improvement aims to streamline the management of API profiles while maintaining data integrity and security.

A defect has been resolved where the click event for the Work Center ID on the editstartjob form was not functioning properly preventing the search box from appearing. This issue was traced back to an error in the handling of callback parameters within the scripting engine. Adjustments were made to the EditMain ColorPicker and InputBox components to ensure that the correct parameters are passed including the previously missing pEditID. Users can now successfully utilize the Work Center search functionality after adding a click event to the Work Center ID element.

A recent update has resolved an issue where users belonging to a specific group could access the Order Reporting feature even when their security settings were disabled. Previously users received an error message when attempting to run reports despite the expectation that the menu option would be disabled. The system has now been adjusted to ensure that the visibility of the Order Reporting menu item is properly governed by the corresponding security settings effectively preventing unauthorized access.

A recent update has resolved an issue that prevented users from effectively searching by date in various grids. Previously attempts to filter or sort by date would result in no data being displayed leading to frustration. With the new changes users can now filter date columns by entering dates as strings ensuring that results appear correctly when typing in the date fields. This improvement enhances the usability of the system allowing for a more efficient reporting experience.

The functionality allowing users to drag unpinned windows off the screen has been restored. Previously with the update to jQuery 3.6.0 dragging dialogs could lead to unexpected behavior such as scrolling issues within the application. The development team has revised the logic to ensure that users can now drag dialogs down to the title bar without them disappearing off-screen while still allowing horizontal movement. This enhancement improves user experience by maintaining the visibility and accessibility of dialog windows.

The issue with the user field for square footage in Version 17 has been resolved. Previously the system added a comma to the entered number which did not align with the defined format of 99999. The development team implemented a validation to prevent user-culture number formatting when specific input settings are applied. With this change the system now correctly stores and displays the numeric value without any commas ensuring consistency with the previous version.

A recent issue involving Honeywell scanners locking up and displaying an 'unable to connect to Deacom Host' error during production input has been resolved. This problem was primarily linked to the handling of multiple item numbers within the input production form. Development efforts have ensured that users no longer experience crashes or error prompts when switching part numbers allowing for a smoother workflow during production tasks. The fix has been implemented and verified resulting in improved stability for scanner operations.

A recent update to the WMS application has resolved an issue where the quantity of completed items for a given operation was not being recorded correctly. Previously when users attempted to log the quantity of completed items the system would erroneously log the worker off the job and fail to save the entered quantity. The fix ensures that when a user records an operation quantity it is now accurately captured and reflected in the relevant reports allowing for proper tracking of production progress.

A recent update has addressed an issue where Android scanners were incorrectly parsing job numbers by adding an unwanted prefix differing from the behavior observed on Windows scanners. To resolve this a new permission was added to the Android manifest to ensure the scanner initializes correctly and processes barcodes as intended. Additionally specific configuration steps for the DataWedge profile on Android 13 devices have been outlined to ensure consistent behavior allowing users to scan job numbers without the prefix. This change enhances compatibility and streamlines the scanning process across different platforms.