WillRelease Notes - 17.03.009.0003

We have enhanced the Inventory Adjustments report by adding a new column 'Postref' to the grid layout. This update enables users to include the 'Postref' field in their reports providing additional transaction details. The enhancement involved modifying the query for the Inventory Adjustment report to incorporate this new column. This change ensures that users can view the 'Postref' value for each transaction enhancing the report's utility and accuracy. The update resolves previous issues where scripts erroneously ran without data by ensuring that the script only executes when there are records to process.

The EDI Import process has been improved to recognize inventory stored in Master Lots when shipping sales orders. Previously inventory within Master Lots was not accessible for reservation or shipping via EDI Import causing issues for users who utilize Master Lots for their inventory management. The updated code logic now includes Master Lots in the inventory check during order shipment ensuring that orders can be processed correctly without manual intervention. This enhancement aligns the functionality of the EDI Import process with the main application providing a seamless experience for users managing inventory in Master Lots.

In certain environments users experienced intermittent issues with printers not appearing when attempting to print from the system. Initially all printers would display correctly but subsequent attempts would result in no printers being available. This was due to long lists of printers being split into multiple network packets which were not properly reassembled by the web server. The issue has been resolved by updating the connection and data handling methods to modern standards ensuring that printer lists are correctly reassembled. Additionally improved error handling and automatic reconnection processes have been implemented to maintain a stable connection allowing users to consistently access their printers for printing tasks.

We have enhanced the performance of the Job Inventory calendar feature significantly reducing the time required for loading moving and saving calendar entries. By optimizing data processing and minimizing redundant operations the loading time has been decreased from over two minutes to just 20 seconds while the time to move jobs has been cut from more than nine minutes to just over two minutes. Additionally saving calendar changes now takes less than two minutes down from three and a half minutes. These improvements ensure a smoother and faster user experience when managing job inventories.

We have enhanced the process of job creation and management linked to Sales Orders to prevent unnecessary job duplication. Previously modifying a Sales Order could inadvertently trigger the creation of a new job even when production was complete and the job was closed. The updated system now considers all jobs associated with a Sales Order including closed ones and adjusts its behavior based on the status of these jobs. If there is only one open job it will proceed normally while a prompt will inform users of any closed jobs. If all jobs are closed the system will list them without creating a new job. Additionally when a job is canceled the 'Create Line Job' flag is reset to prevent automatic job creation ensuring that a new job is only generated if the flag is manually rechecked. These improvements provide a more intuitive experience reducing unnecessary job creation and enhancing the clarity of job status prompts.

The Production Job Reporting Expense Material Report has been improved to accurately display the list of expensed items based on inventory transactions associated with a job. Previously the report incorrectly included certain transactions due to an assumption that a 'finish' transaction would immediately follow a 'relieve' transaction. In situations where this sequence did not occur especially with concurrent user activity the report mistakenly listed items as expensed when they were not. The update now accounts for any 'un-finish' transactions ensuring that only valid expensed materials are included in the report. This enhancement ensures the report provides a precise reflection of the inventory transactions related to expensed materials.

A change was made to address issues with the job material cost detail report. This enhancement allows users to access accurate and detailed job cost material information. The development team focused on optimizing the codebase for better efficiency and reliability ensuring that the report functions smoothly and meets user needs effectively.

A change has been implemented to improve the user experience when modifying sales orders. Users will now receive a warning prompt if they attempt to close the Order Entry tab while there are unsaved changes in the Edit Features form. This enhancement ensures that users are alerted to any unsaved modifications preventing potential data loss. The system will now require acknowledgment of the unsaved changes before allowing the tab to be closed thus enhancing the integrity of user inputs.

A new solution has been implemented to address the import of Sales Order Engineering BOMs using CSV files. The challenge was to correctly import files in the required format without encountering errors. Development changes were made to improve the import process for Mitek Shopnet files specifically removing unnecessary checks for file paths and accommodating missing tags in the files. These improvements ensure that files can be imported successfully without errors although custom BOMs will not be added due to missing elements in the sample file provided. This update facilitates smoother integration of engineering items into sales orders enhancing usability for customers.

A performance issue has been addressed significantly improving the efficiency of the Cash Receipts report. Previously generating this report took around 17 minutes but after implementing optimizations the runtime has been reduced to approximately 20 seconds. The enhancement involved creating a dictionary to store unique results from a key function which minimizes redundant processing and speeds up report generation.

A technical issue was identified where the system incorrectly posted material burdens on purchase orders (POs) even when the 'pu_matbur' setting was not applied. This caused discrepancies in the financial records and auditing concerns. To resolve this the development team adjusted the code so that the PO material burden is only set when Standard Cost is selected in Accounting Options. This ensures the correct assignment and retention of the 'pu_matbur' value during the receipt process preventing unintended postings and maintaining balance in the General Ledger.

The issue of discounts not being correctly posted to the appropriate General Ledger (GL) accounts with facility overrides during check runs has been resolved. Previously the system failed to apply the correct GL override leading to discrepancies in accounting records. The development team addressed this by ensuring that the facility's GL override is properly applied to the discount account when printing checks. This fix ensures that discounts are accurately reflected in the GL accounts according to the specified facility overrides improving the accuracy of financial reporting.

In the financial statement module an issue was identified where the prior year column did not correctly include data from February 29th for leap years. This affected reports generated for February 2025 which failed to account for February 29th 2024 leading to discrepancies in year-over-year comparisons. The development team resolved the problem by adjusting the logic used to determine the date range for the 'Last Year' column calculations. Now if the report spans a fiscal period's start and end dates the system will correctly include the entire prior fiscal period ensuring accurate financial comparisons even in leap years.

Recent updates have resolved an issue where job postings for labor and burden were inaccurately affecting the Inventory Adjustments account. The system now properly recalculates labor and burden values when finishing items ensuring that postings reflect the correct amounts based on job size. This enhancement minimizes variances that previously occurred between standard and re-calculated costs leading to more accurate inventory accounting. Users can expect improved accuracy in their inventory adjustments as a result of this update.

An issue was identified where the 'Hide if Zero' feature on financial statements was not functioning correctly when the balance type was set to 'Change in Balance.' This feature was only working when the balance type was set to 'Ending Balance.' The development team resolved this by ensuring that the 'Hide if Zero' feature now correctly hides rows only when all visible columns in the financial statement grid contain zero values regardless of any hidden columns. Additionally checks were added to confirm that all relevant columns are either integers or decimals before applying the zero-value logic. This improvement ensures that financial statements are displayed accurately without showing unnecessary zero-balance rows.

We have addressed an issue causing slow performance when clearing bank reconciliation transactions. The process which previously took several minutes has been optimized to complete in under 30 seconds. This improvement was achieved by updating the system to handle data more efficiently reducing the time complexity from exponential to linear. Users can now clear un-clear and manage reconciliation items quickly and smoothly enhancing overall system responsiveness.

We have resolved an issue in the Bank Reconciliation Form where the cash balances were inaccurately reflecting activity over a period instead of the actual cash balance. This was causing confusion as users expected to see their true cash balance for reconciliation purposes. The problem stemmed from the start date not being set correctly. Our development team has updated the system to ensure the accurate start and end dates of the fiscal year are used which corrects the cash balance display issue. Users should now see their correct cash balance regardless of the selected date range.

An issue was identified where importing journal entries with values extending beyond three decimal places resulted in imbalanced entries in the general ledger. This imbalance occurred due to rounding discrepancies particularly affecting foreign currency records. The development team resolved this by adjusting the logic to ensure variance entries are applied correctly to foreign currency records. They also implemented a configuration for precise decimal rounding during Excel imports which ensures balanced entries. Additional rounding logic was added to prevent future imbalances. A fix present in the main branch effectively addressed the issue negating the need for further development changes.

A recent update has corrected an issue with the bank reconciliation process where the cash account balance was incorrectly calculated when running reports for a date range that did not include the fiscal year's start. Previously the system was displaying the change in balance for the month rather than the correct ending balance. This has been resolved by adjusting the calculation to use the first day of the fiscal year as the starting point ensuring that the ending balance is accurately reflected in the report.

A problem was identified where pre-filters saved on the Accounting Reporting page were not applying the selected fields correctly. Specifically when users saved a pre-filter with the 'Show Items' set to 'All Accounts' it reverted to 'Accounts with Balances' upon reloading. The development team resolved this by adjusting the logic that sets default values during form loading. Now the system correctly retains and applies user-saved settings ensuring that the 'Show Items' field remains as selected. This fix ensures consistent and accurate behavior when using saved pre-filters.

We have resolved an issue where encrypted bank account details were not displaying correctly when exporting files. Previously these details appeared in their encrypted form making them unreadable. With this fix the bank account information now decrypts properly ensuring that the details are visible and accurate on Grids Reports and Export Profiles. This improvement enhances the usability and accuracy of exported financial data.

A discrepancy was identified where the payment details and general ledger (GL) details were not displaying consistent values due to currency exchange rate differences. The payment details were shown in the purchase order's currency while the GL details appeared in USD. This inconsistency arose because the payment details were using the current exchange rate instead of the rate at the time of payment. The solution involved adjusting the logic to ensure that the payment details use the exchange rate from the invoice date aligning them with the GL details and ensuring consistency across reports.

An issue was identified where adjustments for un-receipt transactions caused inventory reconciliation to be out of balance. This occurred when a Purchase Order (PO) was un-received on the original date despite subsequent transactions. The solution ensures that inventory and General Ledger (GL) postings align correctly when un-receiving a PO. Development changes have been made to automatically adjust inventory on the original received date allowing the PO to be un-received with subsequent adjustments occurring on the current date. This ensures that all related GL postings happen on the same date maintaining balance in inventory reconciliation.

Users previously encountered an issue where the Journal Entry screen would prompt them to save changes even when no modifications were made. This occurred when exiting the screen after selecting either 'Modify' or 'View'. The development team resolved this by removing a redundant loop that incorrectly triggered the save prompt. As a result the application now correctly identifies when no changes have been made allowing users to exit the screen without unnecessary save prompts.

The issue with the purchase order detail report displaying incorrect prices and extensions for orders in foreign currency has been addressed. Previously an incorrect conversion rate was used leading to discrepancies between the report and the general ledger. The development team resolved this by adjusting the query responsible for these calculations to apply the correct conversion factor. This fix ensures that the report now accurately matches the values recorded in the general ledger providing consistent and reliable financial reporting.

In the Check Run report within the Accounting module an issue was identified where payee names were being truncated if they were particularly long. This led to difficulties when performing tasks such as VLOOKUPs and queries as the truncated names did not match the full vendor names. To resolve this the report has been updated to allow payee names to display up to 60 characters aligning with the database's capacity. This ensures that full names are visible and accurately represented facilitating smoother data operations and reporting.

A recent update has resolved an issue related to importing multi-currency journal entries from Excel. Previously when users uploaded journal entries with accounts set to different default currencies all entries were incorrectly posted in a single foreign currency. The fix ensures that each journal entry is now posted in the correct default currency for its respective account allowing for accurate financial reporting. This enhancement improves the functionality of the journal entry import process streamlining operations for users handling multiple currencies.

A recent issue was identified where purchase orders made in foreign currency were incorrectly affecting the Purchase Price Variance (PPV) account instead of the intended foreign exchange gain/loss account. This occurred due to discrepancies in currency conversion during the receipt of purchase orders. The development team has resolved this issue by updating the system to correctly allocate variances to the foreign exchange gain/loss account based on company configuration and foreign currency settings. This ensures accurate financial reporting when receiving or un-receiving purchase orders in foreign currencies.

We have addressed an issue where the currency conversion rate used in closing entries was incorrectly set to the rate from the journal entry date rather than the last date of the accounting period. This fix ensures that the conversion rates applied to closing entries now correctly reflect the intended date providing accurate financial reporting. Users can now expect the closing entries to utilize the conversion rate from the end date of the period aligning with standard accounting practices.

An issue was resolved where users encountered a prompt stating Cannot locate foreign currency record" when attempting to save sales orders. This problem arose when the "Use Ship-To Credit Limit" option was selected but no currency was set for the Ship-To entity leaving the currency field empty and triggering the prompt. The resolution involved implementing a system change that automatically assigns a default currency if the currency field is left blank when saving a sales order. This ensures that the prompt no longer appears allowing for smoother order processing without interruptions."

We have resolved an issue with posting journal entries involving multiple currencies which previously resulted in an out-of-balance error due to a backward currency conversion. The fix ensures that optional spreadsheet columns are properly checked before being referenced during the Excel import of journal entries preventing errors during the process. This enhancement allows for smoother handling of journal entries in various currencies maintaining the integrity of financial data. The changes specifically improve the functionality of importing journal entries by ensuring that currency conversions and entries are correctly managed aligning with the intended financial operations.

A technical issue was identified where cash payments and receipts were not properly utilizing specified gain/loss accounts during processing. Instead of using the designated accounts from the chart of accounts the system defaulted to general ledger overrides based on currency settings. The resolution involved updating the system logic to prioritize the explicitly specified gain/loss accounts on the cash accounts payable and accounts receivable records. This ensures that transactions are accurately recorded according to the intended financial settings improving the accuracy of accounting entries related to currency fluctuations.

A technical issue was identified where transactions were incorrectly posting in Canadian dollars instead of the intended US dollars despite the account and purchase order being set to US currency. The resolution involved modifying the system to prevent unnecessary currency conversions during invoice adjustments. This change ensures that transactions are accurately posted in the account's designated currency eliminating the double currency conversion that led to the error. The development team implemented a condition to bypass conversion if the posting currency already matches the account's currency ensuring accurate postings moving forward.

A problem was identified with the way foreign exchange (FX) rates were being applied to imported journal entries specifically when using a currency other than the home currency such as CAD. The system was incorrectly multiplying the amounts by the exchange rate instead of dividing them resulting in inaccurate financial figures. This issue did not occur when entries were made manually. To resolve this the development team made adjustments to ensure that both manual and imported journal entries are processed consistently. They introduced a function to correctly adjust currency values during FX postings and removed unnecessary checks to streamline the balance validation process. These changes ensure that entries remain balanced and accurately reflect currency conversions whether entered manually or imported from an Excel file.

We have resolved several issues related to the installation of the Deacom eCommerce system enhancing both functionality and user experience. Improved error reporting now provides detailed feedback when the eCommerce database is invalid or lacking necessary data preventing further errors. This includes a new modal popup that clearly communicates issues to users. Additionally we have addressed a problem with the eCommerce site form where saving the form multiple times could cause errors due to password encryption issues. This has been corrected by ensuring passwords do not undergo multiple encryptions thereby preventing logic save errors. Furthermore the 'dxecommsync' table which previously required manual data entry for synchronization is now automatically populated with the necessary records upon saving the eCommerce site settings. These updates streamline the installation process and improve the system's reliability and ease of use.

The issue with EDI Purchase Order invoicing has been resolved by implementing two key code changes. Firstly the unnecessary 'order save' action that occurred before receiving and invoicing has been removed preventing additional triggers from firing. Secondly the logic has been updated to ensure that orders with a zero balance are paid regardless of whether the Auto Invoice option is checked. Additionally a history record will now be created to indicate that an order has been invoiced even when Auto Invoice is unchecked. These changes ensure smoother processing of EDI imports and accurate historical records for invoiced orders.

A problem was identified with processing sales orders created via EDI that included items marked as 'Do Not Post Inventory.' Users encountered an error message stating 'No line items have a quantity to ship' preventing successful order processing. This issue stemmed from incorrect logic in the system that failed to properly handle non-stocked line items. The development team resolved this by refining the logic to accurately differentiate between stocked and non-stocked items ensuring the system processes non-stocked items without errors. This fix allows users to smoothly ship and invoice orders with non-stocked items restoring functionality to the expected behavior.

A technical issue was identified where the system failed to display the Some lots are not frozen" prompt during cycle count worksheet creation for physical inventories. This occurred despite the absence of any inventory transaction prevention flags in the system settings. The resolution involved updating the logic to ensure the prompt appears correctly addressing scenarios where item facilities were improperly filtered. This fix ensures that users are alerted about non-frozen lots when generating cycle count worksheets aligning with expected procedures and improving inventory management accuracy."

In the latest update we've addressed an issue where sales data was inaccurately displayed within the Item Inquiry module. Previously when viewing sales only actual items were shown excluding phantom kit items which resulted in incomplete sales reporting. The resolution involved updating the system logic to ensure that sales data for both actual items and phantom kits are included in the Availability grid. This adjustment aligns the sales figures in the Availability section with those in the View Sales option providing a comprehensive view of all sales orders and kit configurations. Users can now expect accurate sales history reporting reflecting all relevant data without the need for workarounds.

The Notes field on the Move Inventory form has been successfully updated to be a required field when configured as such. This change ensures that users must fill in the Notes field before completing an inventory move addressing a previous issue where moves could be completed without this information. This enhancement includes functionality that triggers the requirement based on changes to the location type or facility.

In certain situations items that aren't tracked by lot and are placed in quarantine were mistakenly being shipped. This occurred even though users didn't have access to manage inventory from quarantine. To resolve this issue the system has been updated to ensure that quarantine lots are properly excluded from shipping processes. Users should ensure they are using this updated version to prevent the shipping of quarantined lots. Additionally the system now filters out unusable lots to ensure only appropriate inventory is processed for shipping effectively preventing any quarantined lots from being shipped inadvertently.

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 Sales Inventory Calendar now accurately reflects inventory status with color coding that corresponds to real-time availability and scheduled production. Previously some orders were incorrectly displayed in green when they should have been yellow due to inventory not being on hand despite values being due. The logic has been updated to account for the 'Do Not Post Inventory' option ensuring that the calendar displays the correct color for each order line based on actual inventory conditions. This improvement provides users with dependable insights for sales and production planning by accurately representing inventory status in the calendar view.

In the latest update we've resolved an issue that affected the ability to de-issue partial quantities from a master lot using the scanner system. Previously attempting to de-issue a partial quantity would inadvertently result in the entire system lot being de-issued. With this fix users can now specify and de-issue only the desired quantity from a master lot enhancing inventory management accuracy and control.

In the Inventory Pre-Staging screen the default values for certain fields were not functioning correctly specifically the 'Date Based On' element. Previously the default value was set to 'Created' but the form would always display 'Planned Start' regardless of the specified default. This issue has been resolved by ensuring that if a user-defined default value exists for the 'Date Based On' field it will be honored and 'jo_planstart' will not be automatically set as the default. This fix ensures that the form respects the assigned default value provided it matches a valid option. If the value is invalid or left blank the system now correctly defaults to 'Planned Start.' The adjustments made to the underlying code ensure that the default value behavior aligns with user expectations and system requirements.

The issue with the custom criteria not filtering correctly on the Inventory History report has been resolved. The logic for applying custom filters related to Item Master fields has been updated to ensure that these filters are correctly applied at the start of the query execution. This change aligns the functionality with similar filters used in other reporting tables. As a result users will now see accurate reporting when applying custom criteria in the Inventory History report.

A recent issue with the BOM Explosion Detail report was identified where item master fields were not displaying correctly when added to the grid. Users attempting to add these fields encountered an 'Invalid Expression' error preventing the correct display of item master data tied to BOM line items. This problem was addressed by ensuring that item master variables are now correctly available for selection and display in the grid layout. The resolution involved adjusting the report to accurately pull and display data from the item master table for each BOM line item.

Facility restrictions are now correctly enforced on the Vendor Part cross-reference grid. Previously users with facility restrictions could view and modify pricing for other facilities. This issue has been resolved ensuring that users can only access and edit pricing information pertinent to their designated facilities. The development team implemented changes to restrict access by setting the facility parameter appropriately thus enhancing data security and integrity across different facility records.

The issue with the Edit Bill of Material function when importing Excel files has been resolved. Previously an error occurred when users attempted to import data after deleting a line without saving the form. This was due to the auxiliary cursor not being properly updated. The development team implemented a fix to ensure that when a line is deleted it is also removed from the cursor preventing the error from occurring during subsequent imports. Users can now import Bill of Materials without encountering issues after making deletions.

Users experienced an issue where attempting to create an Inter-Company Transfer (ICT) via the Material Requirements Planning (MRP) system resulted in an error message about missing foreign currency records preventing the ICT from being created. This problem has been resolved by updating the system to automatically use fallback values from billing records when certain required fields are missing during the ICT creation process. As a result the system now successfully creates the ICT without displaying the error message ensuring smooth operation and accurate data handling.

In the pre-staging process an issue was identified where materials intended for specific orders were incorrectly staged to a single order causing problems in final staging. This meant that when users tried to finalize staging for multiple orders the system did not recognize the materials as being correctly staged preventing completion of the process. The development team has resolved this by ensuring that when Staging-Specific" is selected materials are now properly allocated to their respective orders. This fix ensures that the final staging picklist accurately reflects the correct allocation allowing users to complete the final staging process without errors."

A recent update has addressed an issue where certain item masters were encountering errors when updating the Current Materials field. These errors including logging exceptions and arithmetic overflow messages were caused by numeric values exceeding SQL constraints.The root cause in at least one scenario was traced back to a setup issue in the associated Bill of Materials (BOM). Specifically unit configurations for the part led to inflated material cost calculations that exceeded the allowable numeric range. In such cases the system now correctly triggers a DeacomLoggingException indicating that the value exceeds the allowed limit—this is the expected behavior when encountering invalid setup conditions.To prevent unintended errors elsewhere new validation logic has been introduced. The system now checks all numeric and string parameters against defined SQL constraints before attempting to save any data. These improvements ensure that both direct updates to item masters and indirect calculations within BOMs are validated maintaining system stability and data integrity.

In the latest update we have addressed an issue that prevented users from adjusting inventory directly from the staging area. This was due to changes affecting the ability to make negative inventory adjustments. The resolution involved merging updates that improved unstaging and deissuing processes ensuring that inventory adjustments can now be made without errors related to insufficient inventory. These fixes have been applied to both version 1702 and the subsequent version restoring the functionality for inventory adjustments in staging.

The issue with the Bill of Materials (BOM) report where the calculations for implosion were not aligning with explosion results has been resolved. Previously there was a discrepancy in the quantities displayed when viewing the BOM for a finished good and its component leading to confusion. The resolution involved updating the BOM implosion settings to ensure that the quantity defaults to one providing accurate calculations. This change prevents incorrect multiplication by conversion factors and aligns the implosion and explosion views. Users can now expect consistent and correct quantities when switching between these BOM views.

When inventory is returned on a sales order the system now properly uses the general Last Cost from the Item Master even if no specific facility is set for the item. Previously the cost was incorrectly calculated based on a facility's Last Cost when no facilities were configured. This update ensures that all returns utilize the correct cost value from the Item Master providing consistency and accuracy in cost calculations regardless of facility settings.

An issue was discovered where lot labels were not printing during inventory moves whether partial or full when using the 'Move Inventory' function. The problem stemmed from a coding oversight that caused the forms to close prematurely preventing the printing process. The development team has resolved this by adjusting the function to ensure forms remain open when the 'Move Inventory' function is used independently. This allows for the printing of lot labels and other necessary actions. The forms will still close as intended when triggered by another form ensuring the proper workflow is maintained across different scenarios.

An issue was identified where updating the expiration date of a lot did not reflect the change in the job inventory screen. This discrepancy occurred when users modified lot expiration dates through the system but the updated dates were not appearing as expected in the job inventory details. The resolution for this issue was addressed under a related task ensuring that any changes to lot expiration dates are now accurately updated in the job inventory screen maintaining consistency across the system.

An issue was identified where unreceiving a purchase order (PO) incorrectly debited the Purchase Cost Variance account instead of the Material Burden account. This occurred when freight costs and material burden amounts were specified on the PO line. To resolve this changes were made to ensure that the user-specified values for Material Burden on the PO form take precedence over default item master settings. This correction ensures that when a PO is unreceived the appropriate accounts are debited as expected. The fix has been implemented to adjust the account postings accurately thereby maintaining consistency in financial reporting.

The issue with the part history in the item master has been resolved. Previously the report only displayed inventory-related transactions excluding those marked as 'sal-reserv'. This exclusion was not intentional and has been corrected to ensure that all relevant transaction types including 'sal-reserv' are now included in the part history report. Users can now view a complete history without missing any transactions enhancing the accuracy and comprehensiveness of the inventory reporting feature.

There was an issue with the item master feature overrides where changes made using the filter field were not being saved correctly. Specifically only the last change was retained when multiple modifications were attempted simultaneously. To address this the development team adjusted the saving mechanism. They removed a filter from the feature override cursor ensuring that all changes are accurately captured. This update allows for modified features to be saved correctly when filtering is applied resolving the problem of incomplete updates.

An issue was identified where users received an insufficient inventory message when attempting to update lot costs for items in staging. This was caused by duplicate records due to an incorrect method of merging staging records with lots resulting in erroneous inventory calculations. The resolution involved altering the method used to fetch lots for cost updates eliminating the problematic merge and thereby preventing duplication. This adjustment ensures that the system accurately reflects the available inventory in staging allowing the cost update process to complete without error.

We have addressed an issue where the Label Claim amount was not correctly carried over to new revision records during the Bill of Material (BOM) updates. Previously the system failed to update the user-defined fields (UDFs) properly resulting in the Label Claim field being reset to zero. The resolution involved enhancing the implementation to select UDFs as objects rather than cursors ensuring that the correct values are retained and displayed in the new BOM revision records. Users can now expect the Label Claim field to be accurately updated when performing BOM updates.

An issue was identified where importing a physical inventory count sheet in Excel format resulted in an error if the file had incorrect column headers. Users were not provided with a clear message indicating that the file format was incorrect. Although this ticket was initially resolved under a related subtask the resolution involved enhancing the error messaging to better guide users in correcting the file format. This improvement ensures that users receive clear instructions when an import fails due to formatting issues helping them to resolve the problem more efficiently.

In the Inventory Item Master section users experienced difficulty using arrow keys to navigate through part numbers when the grid initially appeared. This issue has been resolved by implementing a new feature that activates arrow key navigation as soon as the grid is displayed rather than requiring a click on an item. This enhancement ensures smoother and more intuitive navigation for users allowing them to efficiently select their desired part numbers without extra steps.

In this update we addressed an issue where substitute parts for a Bill of Materials (BOM) item were not appearing in the Main Application during the Issue/Reserve process. Although the BOM item was correctly configured with substitute parts users were unable to select these substitutes in the Main App. The development team resolved this by ensuring that substitute parts are now visible and selectable during the issue process. This enhancement allows users to seamlessly issue substitute parts improving the overall functionality and usability of the system.

In the recent software upgrade from version 17.3.6.7 to 17.3.8.4 users encountered an issue where they were unable to move inventory by location due to a system prompt requiring fields such as 'Move Quantity' and 'New Account' to be filled. This problem arose because a previous update inadvertently altered the conditions that determine when these fields are necessary. Specifically when moving an entire location these fields should not be required. The development team resolved this by adjusting the logic so that these fields remain disabled during full location moves while still being required when a specific Part Number is involved. This fix ensures that users can now move inventory locations without unnecessary prompts maintaining the intended functionality.

In the Inventory system an issue was identified where the cost update function did not correctly update the cost for all lots when there were negative quantities. This has been resolved by ensuring the system now accurately updates the cost for lots with negative quantities to reflect the actual financial values. This improvement means that when the financial balance is negative the lot costs are correctly adjusted during the update process providing a more accurate reflection of costs for inventory management.

We have resolved an issue where changes to an item's part number were not being reflected in the associated deal information. Now when a deal is linked to an item that has undergone modifications any updates and saves to the deal will automatically refresh to show the latest part number category or sub-category name.

Previously credit memos required the entire lot to be returned preventing partial lot returns. This issue has been resolved by updating the system to properly handle negative quantities in credit memos. Now users can return partial lots without being forced to return the entire lot. The solution involved implementing an absolute value check for inventory and adding an exception to manage incorrect mixed signs in partial lot returns.

In this update we have addressed an issue where an incorrect quantity prompt appeared during the issuing process when using different units of measure. This was due to rounding discrepancies. The solution involved adjusting the system to round quantities to the appropriate inventory decimals when changing units in the selection form. This ensures that the 'To Apply' and 'Applied' values align correctly eliminating any remaining discrepancies and allowing the process to complete without errors.

In response to an issue where deleted documents from the Item Master were still appearing in printed reports adjustments have been made to ensure that only current documents are included. Previously the system did not properly filter out historical documents leading to inaccuracies in report outputs. The resolution involved updating the system to recognize the status change from 'current' to 'history' for documents in the database. This change means that only documents marked as 'current' will be printed ensuring that reports reflect the most accurate and relevant data.

The issue with the scanner's 'Commit on Scan' feature during final staging has been resolved. Previously users had to manually press Enter in the staging field after scanning a System Lot label which was not intended. The solution involved adjusting the system to check for a global quantity variable ensuring that the quantity is set correctly during the scan process. This change allows the scan to automatically commit without additional user input.

The DEACOM Mobile App experienced a crash when users attempted to view documents through the 'View Docs' feature. This issue arose due to outdated code and problems with file encoding specifically involving characters like spaces and pluses in file names. The development team resolved this by updating the code to align with current Android file handling practices ensuring that documents can now be opened and viewed without causing the app to crash.

We have resolved an issue where creating Maintenance Repair and Operations (MRO) jobs resulted in duplicate entries. Previously selecting 'Order All' would inadvertently generate multiple jobs for the same maintenance tasks within a group. This has been corrected so that now when you choose 'Order All' a single job is created that includes all relevant tasks. This adjustment ensures a streamlined process and prevents unnecessary duplication of jobs.

An issue with the Material Requirements Planning (MRP) system has been resolved which previously affected the accuracy of inventory suggestions for items with long lead times. The MRP was not recalculating suggestions correctly leading to insufficient inventory recommendations that could result in material shortages. Changes have been implemented to ensure that suggestions are updated appropriately with each pass allowing for a more accurate reflection of inventory needs based on current requirements. This enhancement will help prevent negative total net values and ensure that planners can better meet expected demand.

An issue was identified in the Material Requirements Planning (MRP) module where indirect requirements were not displayed when the 'Suggestions' filter was set to 'Exclude'. The development team resolved the issue by ensuring that indirect requirements are displayed regardless of the 'Suggestions' filter setting. Users can now view indirect requirement values as expected when using the MRP module with the 'Suggestions' filter set to 'Exclude.'

We have resolved an issue where users encountered an unexpected prompt indicating a lack of available days in the shop schedule when creating jobs from MRP despite having set facility availability and the 'Split Job by MRP Quantity' option enabled. The problem stemmed from improperly set shop area IDs during job creation. By ensuring that facility and shop area IDs are assigned before splitting job lines based on quantity the system now accurately schedules jobs without errors. This fix ensures seamless job creation and scheduling from MRP enhancing workflow efficiency.

We have resolved an issue where the 'View Vendors' button in the Instant MRP report was not displaying vendor part cross-references correctly. Previously when using Instant MRP the vendor information was not visible even though it appeared correctly in the Time-Phased MRP report. The system has been updated to ensure that the 'View Vendors' feature now consistently shows all vendor part cross-references regardless of pricing across both Instant and Time-Phased MRP reports. This change ensures that users will see the same vendor information in both report types enhancing the reliability of vendor data visibility in the MRP module.

A bug in the Material Requirements Planning (MRP) system was identified where excluding purchasing from calculations inadvertently removed the on-hand inventory data. This issue has been resolved by ensuring the on-hand inventory is consistently applied even when purchasing is excluded in MRP reports. Users can now rely on accurate inventory data regardless of purchasing exclusions providing a more reliable and comprehensive view of inventory levels.

We have resolved an issue where certain buttons in the Time-Phased MRP report were not functioning correctly when using a custom user grid layout. Previously buttons such as 'Edit Part' 'View Blankets' 'View Requirements' 'View Vendors' and 'Availability' did not open their respective forms. The development team adjusted the grid detection logic to reference the main grid rather than specific grid names that change with different layouts. This ensures that all buttons now operate correctly providing consistent functionality across both default and custom grid layouts.

An issue with the Material Requirements Planning (MRP) system has been resolved where it was previously using item master settings instead of facility-specific settings when running MRP by facility. This resulted in incorrect purchase order suggestions due to the absence of facility overrides. The system has been updated to ensure that when MRP is run for a specific facility it correctly applies the facility's override values if they exist. If no facility or facility group is selected the system defaults to using the item master values. Furthermore when running MRP by facility group the system now accurately gathers and applies the necessary values ensuring precise planning and order suggestions. This enhancement guarantees that MRP suggestions are now accurately aligned with the specific settings of each facility.

A bug was identified in the process of creating production jobs via MRP where job quantities did not align with expected amounts from the Bill of Materials or MRP suggestions. This issue was traced to the Setup Job form which initially sourced quantities from the Item Master ignoring any overrides specified in Item Facilities. The development team resolved this by implementing a method to check for Item Facilities overrides and use them to determine the correct quantities when applicable. This ensures that job quantities now accurately reflect the expected amounts enhancing the reliability of job scheduling through MRP.

A recent update has addressed an issue with manual Purchase Orders (POs) where quantities were not being correctly converted from stock units to purchase units. Previously while the Material Requirements Planning (MRP) system handled this conversion accurately manual POs did not reflect the correct purchase unit quantities. The development team has now implemented logic that ensures quantities are properly converted during manual PO entry aligning them with the conversion process used in MRP. This enhancement ensures consistency and accuracy in inventory management across different systems.

We have addressed an issue where the color coding of rows in the Material Requirements Planning (MRP) grid would become misaligned after scrolling and interacting with certain part numbers. This problem occurred when the expanded grid was reloaded with only one page of streamed rows affecting the display of row colors. The underlying logic has been corrected to ensure that row colors are processed correctly even when the scroll bar is not at the top. Additionally the frozen grid now maintains its expanded row colors during scrolling preventing any mismatch between the main and frozen grids. This fix ensures a consistent and accurate display of row colors across the MRP grid.

In the Manufacturing Resource Planning (MRP) system there was an issue where subassemblies were not being scheduled correctly during job creation for main assemblies. This was due to missing revision and shop area identifiers which caused subassemblies to be excluded from the job. The issue has been resolved by ensuring that each subassembly's revision and shop area identifiers are properly set allowing them to be included in the MRP process as intended. This fix ensures that all necessary components are accounted for during job creation enhancing the accuracy and efficiency of the MRP system.

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 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.

In certain instances when generating an invoice report for shipped sales orders an image in the page footer would disappear due to the 'Remove Line When Empty' option being checked. This issue has been resolved by adjusting the way the footer is processed. Previously the footer was only processed once before the first page was created leading to the image and other elements being invisible on subsequent pages. Now the footer is reprocessed on the last page of the report ensuring that the image appears correctly. This change allows the footer to expand vertically making the image visible without occupying unnecessary space on earlier pages.

We have resolved an issue where the detail band on the Certificate of Analysis (CoA) part form was overlapping the page footer in printed reports. Our development team has enhanced the system to ensure that when bands grow beyond the available space on a page they are split correctly preventing any overlap with the footer. This improvement involves a new mechanism that checks if multiple lines in a band fit within the remaining printable area ensuring proper page layout. Additionally conditions have been added to avoid creating empty bands during this process. Users should now see reports correctly divided into pages without footer interference.

The issue with incorrect phone number formatting on the Certificate of Analysis (CoA) form has been resolved. Previously the phone numbers were not displaying correctly due to a formatting inconsistency in the facility record. The development team implemented a solution that applies a phone number mask to ensure proper formatting even if the phone number in the facility record is not initially well-formatted. This improvement aligns the CoA phone number formatting with that of other report layouts where the formatting was already correct. As a result phone numbers now display consistently and accurately across all relevant reports.

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.

We have resolved an issue where attempting to print labels during the receipt of split lots resulted in an endless printing loop on ZPL label printers. This was particularly problematic when splitting lots into quantities greater than three. The underlying cause was identified as a misalignment in the code that incorrectly matched lines and labels leading to duplicate printing. The solution involved updating the code to ensure that each lot is uniquely identified preventing unnecessary repeated print jobs. With this fix labels will now print correctly one per lot without causing an overload of print jobs.

The issue where the print substitution functionality was not working correctly has been resolved. Previously when users attempted to print a specific version of a job batch record using print substitution groups the system defaulted to printing the normal report instead. This was due to the Substitution Id not being properly set in certain cases. The development team has addressed this by ensuring that the Substitution Id is correctly configured when using print substitutes allowing the system to print the intended report rather than the base report. Users can now expect the correct substitute report to print as configured in their setup.

A recent update has resolved an issue where users encountered errors when attempting to print sales order reports containing feature parts. Previously inconsistencies in record handling led to missing feature parts in printed documents. The solution ensures that records are freshly created with each save maintaining accurate links for printing. However any orders already affected by this issue will require manual correction by re-selecting features. This fix will prevent future occurrences and ensure seamless report generation for shipped and invoiced orders with defined features.

The issue where printing Purchase Order (PO) labels to PDF was resulting in a system error has been resolved. The error occurred when using the 'Print To PDF' option from the 'View Detail' form of a received PO. The resolution involved updating the underlying code to prevent file-related errors by implementing a file lock mechanism ensuring that files are correctly accessed during the PDF generation process. Additionally the printing logic was adjusted to reset copies after each print job ensuring consistent functionality. These changes eliminate the error allowing seamless printing of PO labels to PDF.

A technical issue was identified where printing documents related to sales orders with feature parts resulted in an error message indicating that there were no feature parts to print. This problem was traced to an error in how header information was being saved where the system attempted to update existing rows instead of creating new ones. The development team has implemented changes to ensure that new rows are generated when header information is saved effectively resolving the printing issue. This fix should prevent the error message from appearing and allow for successful document printing in future instances.

The issue with the 'Print Attached' feature in the Document Group settings has been resolved. Previously the system failed to print attachments linked to the 'Ship-To Company' due to an incorrect setting. The development team corrected the value in the 'attached when' option to properly recognize 'Ship-To Company'. This fix ensures that documents associated with the specified company are now printed correctly when selected in the document group settings.

In recent updates printing document groups to PDF resulted in files being incorrectly named with just the PO and PO number making it difficult to distinguish between different reports. Previously each file was named according to the report type and PO number which helped in identifying them easily. To address this issue a new flag specific to document groups was implemented. This flag ensures that the PDFs are named correctly restoring the original functionality. This solution was developed to specifically target the bug that had been introduced ensuring that each document within a group is labeled with the correct report type and PO number enhancing clarity and usability.

In response to the issue where sales invoices were not automatically populating the email field when printed to email the functionality has been updated. The system now checks if the 'bi_invoiceemail' field is set for the customer. If it is this email address will be used; otherwise it defaults to the 'bi_email' field. This ensures that the correct email address is selected based on the hierarchy intended for invoice communications. This update resolves the inconsistency experienced across different versions providing a more reliable and expected behavior when emailing invoices.

We have fixed an issue where attempting to print a user report with a name containing an apostrophe resulted in an error. This problem occurred because the system did not handle apostrophes correctly in user report names. Our development team updated the SQL query process to use parameterized queries which effectively resolves this issue. Users can now save and print reports with apostrophes in their names without encountering errors.

Previously when generating PDF files for sales orders with multiple items the files were incorrectly named causing confusion as they contained the same item number despite representing different specifications. This issue has been resolved by updating the system to conditionally apply the correct item labels as file names when using the 'document group' report type. A new property has been introduced to manage file names across different scenarios ensuring that each PDF accurately reflects the corresponding part number. These changes ensure that when printing document groups each part form is named according to its specific item number eliminating any naming conflicts and improving clarity.

In response to the issue where the print button on the toolbar was non-functional within the Ticket Workflow grid in CRM the development team has successfully updated the button's functionality. This enhancement allows users to print Workflow approvals directly from the Ticket Workflow interface. The solution involved adjusting the underlying function that manages the print command ensuring compatibility with versions 16.05 and above. Users can now utilize the print feature effectively improving the usability of the CRM Ticket Workflow tool.

The issue with connecting Bluetooth printers to the DSD app has been resolved by updating the app to request necessary Bluetooth permissions. Previously users could connect their printers to scanners but were unable to print invoices directly from the DSD app as only network printers were visible. This update ensures that the app can now recognize and utilize Bluetooth printers like the Zebra INZ320 and ZQ320 models enabling seamless invoice printing for drivers.

We have resolved an issue where certain fields were not displaying correctly for all line items in job reports. Previously the display of allergen information varied based on the position of items in the job entry form leading to inconsistent reporting. Our development team has updated the underlying method responsible for generating these reports ensuring that allergen information is now accurately and consistently displayed for each part regardless of its position in the job.

When receiving purchase orders users experienced an issue where only the first lot label was generated as a PDF despite splitting a user lot into multiple system lots. The system was clarified to operate as intended allowing multiple PDFs to be generated only when labels are configured to print 'By Lot.' This setup is crucial for ensuring all lot labels are generated correctly. Users should update system configurations in the Inventory section to set 'PO Label' printing to 'By Lot' both under Item Master and Options.

Users encountered an issue when attempting to print job labels after modifying the part form line to update print quantities which inadvertently added an extra line to the print grid leading to an error. The development team has successfully implemented adjustments to apply the existing fix to these versions ensuring that users can modify print quantities without triggering errors thus maintaining functionality and system stability.

The Job Material Cost Detail Report has been updated to correctly calculate and display quantities when co-products are involved. Each item will now appear on its own line in the report accurately reflecting its association with the corresponding job line. This enhancement ensures that the finish quantity is calculated based on the actual production and material issued resolving discrepancies that previously occurred when co-products were present.

The issue of jobs being improperly reordered on the Master Production Calendar after updating a job's run time has been resolved. Previously adding time to a job's routing would not only push subsequent jobs back but also change their order causing confusion. The solution involved refining the logic to ensure only the affected jobs are processed without altering their sequence. This improvement prevents erroneous shortening of job durations and maintains the original order of jobs on the calendar. Now when run times are updated subsequent jobs are correctly adjusted in timing without any reordering ensuring consistent scheduling across the work center. There´s still an additional issue in printed reports but the core functionality on the duration of the reports is resolved.

We resolved an issue in the production scheduling system where the planned start date of a job did not update correctly when scheduling the first sequence of a routing separately from subsequent sequences. Previously the start date only updated when all sequences were scheduled together. The fix ensures that the planned start date now accurately reflects the earliest scheduled sequence even when scheduled independently by correctly handling date values. This improvement allows users more flexibility in scheduling and ensures that the planned start date displayed is always current and accurate.

The issue where the export to Excel icon was missing from the Job Routing grid has been resolved. The development team updated the grid section to incorporate the default toolbar ensuring the Excel export functionality is now available. This enhancement allows users to efficiently export job routing data to Excel directly from the grid streamlining the data management process.

A technical issue was resolved where modifying a sales order linked to a closed job would mistakenly create a new job for the entire sales order quantity. This could lead to unnecessary overproduction and potential excess inventory. The solution involved updating the system to prevent new job creation when the original job is closed ensuring accurate production and inventory management.

Previously when making changes to a sales order linked to a job in a different facility the job's facility would automatically change to match the facility on the sales order header. This issue has been resolved by ensuring that the facility is only synchronized when a new job is created. For existing jobs the original facility is now retained preventing any unintended changes. This update ensures that modifications to sales orders do not inadvertently affect the facility assignment of linked jobs.

A problem was identified where saving a sales order with the 'Header job' flag selected led to an error. This issue has been resolved by enhancing the system to use savepoints within the SQL query process. Now if there is a failure in creating a job only the job creation is rolled back ensuring that the rest of the sales order transaction remains intact. This change prevents the error from affecting the entire transaction allowing the sales order to be saved successfully even if the job creation encounters issues.

We have resolved an issue where Job Dates 1-5 were not updating correctly when expressions were applied in the scheduling options. Previously these dates were supposed to auto-populate based on specified calculations whenever a job was saved or modified but they failed to do so. The fix ensures that only fields with configured date calculations will now save the new values entered. This update bypasses routing validation which previously prevented updates to job date fields. As a result users can now expect accurate date calculations and updates when using expressions in job scheduling.

A problem was identified where users could attempt to un-finish production with a quantity of zero leading to unexpected issues within the system. To address this a validation has been implemented that prevents users from un-finishing with a zero quantity. This change ensures that only meaningful quantities can be processed during the un-finish process.

A technical issue was identified where sales orders were incorrectly generating jobs for items not flagged as 'Make to Order.' This problem affected the accuracy of job creation leading to unnecessary jobs being set up for items that should not have been included. To resolve this the system now correctly filters sales order lines based on the 'Make to Order' designation ensuring that only items marked as such are processed into jobs. This development change ensures that job creation aligns with the intended order specifications improving the accuracy and efficiency of the process.

In this update we've addressed an issue where the 'Edit BOM Form Layout' button was unavailable for users. This occurred due to the system's configuration of form layouts which differed from user settings. Our development team has modified the underlying form file to ensure that the layout button is now visible and enabled by default. This change eliminates the need for manual workarounds particularly benefiting cloud users who previously could not adjust these settings.

We have fixed an issue in the AutoFinisher where the system was not correctly applying the expiration date settings from the Bill of Materials (BOM). Previously it defaulted to using the product's shelf life date instead of the specified expiration date. With this update the AutoFinisher now correctly propagates the expiration date as configured in the BOM ensuring that the correct date is applied throughout the production process. This enhancement ensures that the expiration date is accurately reflected in inventory reports aligning with the setup from the source allocation.

A technical issue was affecting the ability to complete pallets in the AutoFinisher causing them to remain in a queued state without progressing. This problem persisted despite attempts to resolve it by restarting the Automation Console and the Autofinisher Service which only provided temporary relief. To address this a new timer mechanism was implemented replacing the previous method of restarting. Additionally TaskFactory is now utilized to manage tasks more efficiently eliminating the need for the .wait function. These changes have successfully resolved the issue allowing pallets to process correctly without getting stuck.

The AutoFinisher tool was incorrectly processing non-serialized and non-catch weight items by dividing them into individual units rather than combining them into a single system lot. This issue has been resolved by updating the system's handling of inventory serialization and catch weight settings. The AutoFinisher now correctly groups these items into a combined system lot ensuring that non-serialized inventory is not mistakenly finished with a serial number. This fix ensures accurate and efficient processing of inventory aligning with the intended configuration settings.

Recently an issue was identified where pallets were incorrectly marked as 'Failed' in the Auto Finisher client despite successful completion of the finishing process. This problem arose following changes made to the system which affected the handling of items that are not serialized or do not have catch weights. The resolution involved updating the software to ensure that these types of items can be properly processed and palletized without relying on serial numbers. As a result pallets now update to 'Complete' status reflecting the actual success of the finishing operations.

We resolved an issue that prevented users from filtering multiple work centers in the master production calendar using custom criteria. Previously users encountered errors when attempting to view work centers across different types or shop areas. The problem was due to missing parameters in the query when custom filters were applied. Our team addressed this by ensuring that SQL parameters are correctly included when setting custom filters. Additionally we adjusted the order of filter application to ensure accurate results. These changes allow users to successfully filter and view multiple work centers without encountering errors enhancing the flexibility and functionality of the master production calendar.

A technical issue was identified in the Purchase Order reporting system where custom criteria using 'OR' logic did not yield results as expected. This problem occurred when criteria were applied to both the Purchase Order header and line data. The development team resolved the issue by modifying the data retrieval process. A subquery was introduced to ensure that relevant Purchase Order lines are correctly processed alongside header information. This adjustment allows the system to accurately reflect orders that fulfill at least one of the specified criteria thereby aligning with user expectations for 'OR' logic functionality.

An issue was resolved where switching vendors on a purchase order did not update the vendor part information correctly. Previously when changing the vendor the system seemed to update the vendor part on the order line form but the new data was not saved requiring manual intervention. This led to unexpected behavior including issues with the save button functionality. The development team addressed the problem by enhancing the method responsible for handling vendor changes ensuring that the vendor part information is accurately updated and displayed on the order grid. This fix ensures that vendor information is correctly managed without requiring additional manual steps.

Users experienced an issue where attempting to reverse the receipt of an in-transit order triggered an error. This problem has been resolved by updating the system to include a missing field in a database query ensuring that the un-receive process now completes without any errors. Users can now confidently un-receive in-transit orders without encountering issues.

We have resolved an issue where the purchasing line entry did not consistently start at the part number field after using the SHIFT ALT N shortcut. Previously the cursor would sometimes start at the quantity or price fields instead. The underlying issue was due to the focus being retained from previous actions. This has been corrected by ensuring that when a new line is initiated the focus is always set to the part number field.

An error was occurring when trying to add pu_notes to the PO detail grid layout due to duplicate column names. This issue has been resolved by removing the repeated 'pu_notes' field from the report configuration.

An issue was identified where users were unable to enter results for stability tests after initial quality control tests were completed causing lots to remain in a pending status. This prevented the completion and approval of QC testing with users receiving messages indicating no tests were left to complete. The development team addressed this by updating the workflow for moving stability tests to pending. Stability tests are now correctly set to allow new results to be entered aligning the automatic process with the manual process for moving tests to pending. This ensures users can successfully input and complete stability test results as intended.

A technical issue was resolved where quality control (QC) processes could not be completed for items that were moved after being returned via sales orders. Previously the system failed to recognize these items due to changes in reference identifiers when a lot was moved. The correction involved updating the system to use a consistent reference identifier that matches the original sales order ensuring that QC can be completed even after items are relocated.

A technical issue was resolved where an error occurred during the creation of jobs through the Material Requirements Planning (MRP) system for items marked with 'Plan QC During MRP Job Creation.' The error was due to an unavailable field during the job creation process via the MRP QC Planning form. A conditional adjustment was implemented to address this scenario ensuring that jobs can now be created successfully without encountering errors. This enhancement improves the job creation process for items requiring quality control planning during MRP resulting in seamless integration with sales orders when the QC flag is enabled.

A technical issue was identified where timestamps were not displaying correctly when a lot was marked as At Risk" in the system. Specifically the timestamp format was not compatible with the system's requirements leading to missing timestamps in the history view for certain actions. This problem has been resolved by correcting the timestamp format ensuring that all actions display the appropriate time when viewed in the history. Users can now see accurate timestamps for all actions related to inventory status changes enhancing clarity and record-keeping within the system."

We resolved an issue where updating a Quality Control (QC) group and opting to apply these updates to existing jobs inadvertently reset workflows in Bills of Material (BOMs). This problem stemmed from outdated logic that mishandled the workflow cursor during the saving process. Our development team has updated the relevant code to ensure that the workflow cursor loads correctly preventing any unintended clearing of workflows. This fix ensures that workflows remain intact when QC groups are modified maintaining the integrity of the BOM processes.

A technical issue was identified in the inventory movement process where the system incorrectly allowed users to move QC pending lots to staging despite permissions set to prevent such actions. This occurred when the 'QC Pending' option was disabled on the 'Move To' field of the inventory movement form causing the 'Move From' field to display 'Inventory' instead of 'Pending'. The development team has resolved this by refining the logic that populates the fields ensuring that the system correctly recognizes QC pending lots and respects user permissions. Now the form accurately reflects the QC status preventing unauthorized movement of lots and maintaining proper inventory control.

A technical issue was identified where inventory marked as 'QC Pending' with an expiration date was not being properly excluded from the available on-hand inventory calculations in the Material Requirements Planning (MRP) system even after the expiration date had passed. This meant that expired inventory continued to be incorrectly shown as available. The development team resolved this by adjusting the logic within the system to ensure that lots with future expiration dates are correctly removed from MRP calculations once they expire particularly when their status is 'QC Pending.' This ensures that expired inventory is no longer considered available improving the accuracy of inventory management.

A security issue was identified where users in certain Quality Control (QC) groups could view and modify test results that should have been restricted based on their access permissions. Specifically users in the QA Supervisor group could access results meant for the QC Management group and vice versa which was not in line with the intended security configurations. To resolve this the system was updated to ensure that users can only view and modify QC tests that they are authorized to access. The update included refining the logic to check user permissions before displaying QC tests ensuring that all tests are appropriately filtered based on the user's access rights. This change prevents unauthorized access and modification of QC test results aligning the system's functionality with the security settings of each user group.

An issue was identified where an error occurred on the Purchase Order Quality Control (PO QC) results page when users attempted to filter items select 'All' and move the item for QC Result. This error has been resolved by making adjustments to the underlying system processes which now properly handle interactions with grid data. Users can now filter items and select 'All' without encountering any issues ensuring a smoother and more reliable experience when entering QC results.

When changes are made to a Quality Control Group users are prompted to update all current jobs to reflect these changes. However jobs were not being updated as expected. This issue has been resolved by ensuring that open jobs using the old revision ID are updated to use the new revision ID. This development change involves a query that updates all open jobs with the new revision ID ensuring consistency across job entries and reports.

The process of importing sales order lines from the iCommand database into the Deacom system has been significantly improved. Previously this task took nearly a minute causing delays for users. To enhance performance and reliability developers modified the query involved in the import process. By using a local variable instead of a parameter the query execution plan was optimized reducing the import time to less than 3 seconds. This change addresses previous inefficiencies and ensures a faster and smoother import experience for users.

A problem was identified where the commission calculations for sales orders were being incorrectly multiplied when multiple payments were applied. This issue has been resolved by updating the system to ensure that commissions are calculated only once per order regardless of the number of payments made. The fix enhances the accuracy of commission reporting ensuring that commissions are based solely on the order details and not influenced by the number of payments processed. This improvement ensures that the commission calculations are consistent and reliable providing accurate financial data for sales transactions.

In this update we resolved an issue where numerical user-defined fields in sales orders were not clearing when the reset button was pressed. While other field types were resetting as expected numerical fields retained their values leading to inconsistencies. The development team has made adjustments to ensure that numerical fields now reset to their default values along with other fields. This enhancement provides a uniform behavior across all user-defined fields within the sales order interface ensuring a smoother and more predictable user experience.

In this update the system now correctly adjusts the Shipping Account when a sales order's Bill-To or Ship-To customer is changed. Previously the Shipping Account did not update to reflect the new customer retaining the settings from the previous customer. The solution involves introducing a new variable to filter shipping account options ensuring only active accounts are displayed and selected as defaults. This change guarantees that all relevant fields in the sales order including the Shipping Account are updated accurately based on the new customer's details improving the reliability of shipping account management within the system.

The issue with the Retroactive button on the Ship To Companies report has been resolved. Previously the button was not functioning correctly due to an outdated field reference which resulted in no records being updated. The development team addressed this by updating the logic to handle multiple sales representatives for Ship To entities. This involved modifying the query to ensure that the correct sales representative is assigned to the sales orders when changes are made to the Ship To record. As a result when the Retroactive button is used it now accurately updates the sales orders to reflect the current sales representative assignments.

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.

An issue was resolved where modifying features in a sales order would inadvertently clear selected options when a filter was applied to the options grid. The problem stemmed from a coding error related to condition overrides which has now been corrected. Users can confidently apply filters and make changes to individual options without affecting other selections. The system now retains all previously selected features ensuring that toggling options only affects the intended item. This fix enhances the reliability of the Edit Features" functionality in the sales order process."

FedEx LTL shipments were experiencing issues with generating paperwork due to an error in package dimensions. The system was not able to handle dimensions that exceeded FedEx's maximum allowable limits resulting in an error message. Developers have addressed this by updating the system to provide a clear message when package dimensions exceed these limits. This improvement ensures users are informed of the specific issue allowing them to adjust package sizes accordingly to successfully generate shipment paperwork.

In response to an issue where the Customer Part Cross Reference was being erased upon changing the ship-to on a Master Order sales order line updates have been made to ensure the integrity of data. The system now retains the Customer Part Cross Reference when the Ship-To is modified provided the reference is not specific to the original ship-to. This enhancement prevents unnecessary data loss and maintains consistency across sales orders ensuring that part references remain intact unless explicitly linked to a different ship-to location.

The issue with the 'Calc Promise' feature not functioning correctly has been resolved. Previously the calculation was not accurately reflecting the promised date based on the longest lead time within the Bill of Materials (BOM). The fix ensures that when the 'Sold+Longest' option is selected the promised date now correctly sums the lead time of the sales order item with the single longest lead time from the BOM rather than cumulatively adding lead times from multiple BOM levels. This adjustment provides a more precise promised date by focusing only on the necessary lead times improving the accuracy of sales order scheduling.

In the Sales Order Entry process an issue was identified where manually added sales order lines were not sorting correctly above sales calculation lines. This has been resolved so that any manually added lines will now consistently appear above the lines generated from sales calculations. This change ensures that users can easily see their manually entered items prioritized in the order entry interface.

A problem was identified where jobs appeared duplicated in the system when sales order lines were re-phased causing confusion as only one job existed in the database. This issue arose from incorrect reassignment of line numbers leading to data corruption. To resolve this the development team implemented a fix that ensures line numbers are organized correctly preventing duplication. The system now properly deletes old lines and reassigns line numbers based on the existing order maintaining data consistency and ensuring that job lines are accurately managed when phases are modified.

In the latest update a problem was resolved where the weights of engineered items imported into sales orders were not being correctly calculated resulting in inaccurate shipping paperwork. The development team addressed this issue by ensuring that the weight from the imported engineering files is now accurately reflected in the sales order line weights restoring the correct functionality. This fix ensures that all imported items have their weights properly integrated into sales orders allowing for accurate shipping documentation.

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 recent update has improved the handling of category restrictions during sales order entry. Previously a facility-restricted user could inadvertently add a restricted item to a sales order leading to an error. This has been addressed by implementing a system prompt that alerts the user when they attempt to add an item with category restrictions thereby preventing the order process from continuing without proper authorization. This change ensures that users are informed of any restrictions before proceeding enhancing the security and accuracy of sales transactions.

The issue where copied sales orders with selected feature options did not accurately calculate the feature pricing impact on order pricing has been resolved. Now when a sales order is copied the correct feature pricing will be applied to the new sales order line ensuring that the pricing reflects the original order accurately.

An issue was identified in the sales order reporting feature where the system failed to respond correctly when a user attempted to search for a second sales order after viewing details of a previous one. This was caused by missing parameters during the query process especially when users were restricted to specific facilities. The development team resolved this by ensuring that all necessary parameters are included in subsequent searches thus preventing application freezes and inconsistencies. Additionally they improved the query process by using parameterized queries instead of direct SQL concatenation enhancing security and reliability when handling search criteria. As a result users can now seamlessly search for and view sales orders without encountering errors.

An issue was identified where lots excluded for specific Ship-To companies were still appearing as selectable options during the reservation and shipping processes. This problem has been resolved by ensuring that the system correctly filters out excluded lots based on the Ship-To Company ID. As a result when reserving or shipping orders excluded lots will no longer be available for selection if they are designated for exclusion by the Ship-To Company. This fix enhances inventory management by preventing the selection of inappropriate lots thus ensuring compliance with exclusion criteria.

The issue of being unable to save new promotions due to a duplicate description prompt has been resolved. Previously the system incorrectly flagged descriptions as duplicates even when they were unique causing confusion and preventing users from saving promotions. The update ensures that the system accurately checks for duplicate descriptions allowing users to create and modify promotions without encountering erroneous prompts. This fix enhances the functionality and reliability of the promotions feature.

A system error that occurred when modifying a Bill-To company from the searchbox has been resolved. Users will no longer encounter a KeyNotFoundException when attempting to save changes after selecting a Bill-To company from the Customer Look-Up. The development team made necessary adjustments to the underlying code to ensure smooth functionality during this process.

The commission reports have been updated to ensure that all commissionable line items from sales orders are displayed correctly even when multiple sales representatives are associated with an order. Previously the reports were only showing the first line item which led to confusion regarding missing data. This issue has been resolved by refining the handling of commission lines allowing for accurate representation of all applicable items on the report. Users can now expect to see complete data in their commission reports enhancing clarity and usability.

The development team updated the system logic when using the sales features option to include a check for null or empty values in the availability settings ensuring that only the correct feature options are shown.

An issue where contracts were incorrectly showing negative balances has been resolved. The problem occurred when modifying order lines leading to saved lines exceeding the allowed order quantity without proper validation. The system now ensures that the check for open blanket orders considers lines that have been previously saved using a specific identifier. This adjustment prevents the system from bypassing the quantity checks thereby maintaining accurate contract balances and preventing negative values.

In certain situations when creating a new Sales Order using the Page Down button the Bill-To field would only display the option selected in the previous order. This issue has been addressed by adjusting the code execution sequence. Specifically the process for updating the Bill-To field filter when the Ship-To company is changed was revised. The necessary code was moved to ensure proper execution allowing the Bill-To field to refresh correctly and display all available options each time a new order is started.

The issue where the Edit feature override" form did not advance to the next option when the "Next" button was selected has been resolved. This problem occurred when the grid was filtered by the status field causing the navigation to fail upon changing the status and attempting to move to the next or previous element. The development team addressed this by duplicating the cursor to maintain a reference to the originally modified row allowing the navigation logic to accurately identify and move to the next or previous element in the filtered grid. Users can now smoothly transition between feature overrides using the "Next" or "Prev" buttons ensuring changes are saved and the correct elements are loaded."

Users who are restricted to specific facility groups can now select facilities within their designated group when using the Deal Pricing feature. Previously these users faced limitations that prevented them from choosing facilities but this issue has been resolved. The adjustments ensure that the facility group search box reflects the user's restrictions and remains disabled while the facility search box is enabled allowing selection of available facilities within the restricted group. This enhancement provides a more streamlined and functional experience for users with facility group restrictions.

In the latest update we've addressed an issue where sales orders would crash when multiple feature part numbers were involved. This problem occurred during the process of adding and configuring items with specific features. Our development team has introduced a safeguard that checks for unselected features without child elements preventing logical sequence errors that led to system crashes. This enhancement ensures smoother operation when managing feature selections in sales orders providing a more stable and reliable user experience.

A problem was identified where the Date Based On" setting in the Sales Order Reporting feature was not being correctly retained when a saved prefilter was reused. The issue caused the "Date Based On" value to revert to "Received" instead of maintaining its intended "Created" status. To resolve this adjustments were made to ensure that the saved filter does not alter the "Date Based On" setting unless explicitly changed by the user. This fix ensures that the correct date criteria are applied consistently when using saved prefilters enhancing the reliability of order reporting functionality."

When creating a new Sales Order the cursor was incorrectly defaulting to the filter field instead of the Bill-To field. This issue occurred after saving the order and pressing the Page Down button. The development team resolved this by adjusting the system to prioritize focusing on the first visible input field that is not the filter box when a form loads. If no other input fields are available the focus will default to the filter field maintaining expected behavior. This change ensures that users can efficiently enter information without unnecessary navigation.

An issue was identified where the document and tax date in Avalara did not update correctly when a sales order was shipped and committed. This could lead to orders being reported on the wrong tax return if there was a significant delay between the order being placed and shipped. The development team resolved this by ensuring the ship date is used when updating the transaction model rather than the order date. This fix corrects the unintended behavior introduced by a previous update ensuring that Avalara reflects the correct shipping date as the document date which aligns the tax date accordingly. This enhancement prevents discrepancies in tax reporting by accurately updating the document date to match the shipping date when orders are processed.

The issue of the 'Transfer Cost Expression' fields being hidden and unavailable has been resolved. Previously these fields were not visible or accessible within certain sections of the system such as the Sales tab under Inventory Maintenance and the Shipping options under Sales. To address this the licensing restrictions on the 'Transfer Cost Expression' field were removed making it available to all users with base essentials access. This change ensures that the field now appears in the relevant sections enhancing usability and access to necessary cost expression functionalities.

A technical issue was identified where a promotional discount was incorrectly calculated by including another promotion leading to an inaccurate discount amount. The problem arose when a specific promotional setup was not correctly distinguishing between line-level and header-level discounts. The development team resolved this by refining the system's logic to ensure that promotions set to apply by line" only consider the designated line's value without incorporating other promotions. This adjustment ensures that each promotion is calculated independently resulting in the correct discount amounts being applied. The update enhances the accuracy of promotional calculations within the sales order process."

We addressed an issue where the toolbar buttons were missing from the Bill-To form layout in the system. Previously users were unable to see or use the 'Form Layouts' and 'View Docs' buttons when accessing Bill-To records. This has been resolved by ensuring that these buttons are now visible and enabled allowing users to access these functionalities directly from the Bill-To form layout.

The issue with the Sales Rep Ranking Report has been resolved. Previously when a user with sales rep restrictions accessed the report it incorrectly displayed rankings for all sales reps. The system now ensures that the 'All' option is removed from the Sales Rep filter for users with restrictions so only the relevant sales rep data is shown. This update enhances the accuracy of the report by respecting user-specific sales rep limitations.

A discrepancy in inventory reporting was identified when negative lots were un-shipped during inter-company transfers. Previously negative inventory records were zeroed out without proper adjustments leading to inconsistencies between on-hand quantities and historical data. The development team has resolved this issue by ensuring that negative shipped lots are correctly processed in inventory calculations. This update allows for accurate tracking and balancing of inventory movements aligning the on-hand and historical records. Users can now expect consistent inventory figures even when adjusting negative lots.

A technical issue was identified where promotional items were not shipping with the correct quantities when using the 'Use Quantity From Line' feature. This feature is intended to match the promotional item quantity to the corresponding sales order line but was incorrectly defaulting to a quantity of one leading to miscalculations in the promotional values. The development team resolved this issue by updating the system to ensure that promotional quantities are correctly aligned with the originating sales order quantities. This fix ensures that promotional items ship in the correct quantities maintaining consistency with the sales order lines they are associated with.

A technical issue was identified where certain feature options were not appearing in the inclusions/exclusions list for categories despite being configured correctly. This problem was traced to the way the system handled the exclusion of items from the features tree. To resolve this the development team updated the logic responsible for constructing the features tree ensuring that excluded items are correctly omitted from view. With these changes users can now accurately manage feature options within their inventory categories without encountering missing entries.

Previously when creating a new Ship-To Company the system incorrectly updated the existing shipping account record associated with the Bill-To Company instead of generating a new record. This caused the shipping accounts of the Bill-To and Ship-To companies to be linked leading to issues such as deactivation of accounts affecting both entities. The development team has resolved this by ensuring that a new record is created for each new Ship-To Company preventing the unintended linkage of shipping accounts. This change ensures that shipping accounts are managed independently for Bill-To and Ship-To entities maintaining the integrity of account information across different companies.

We have addressed an issue where users were unable to save purchase orders if the associated blanket order had zero remaining quantity even after switching the pricing method to manual. The system was incorrectly prompting that the order quantity exceeded the blanket order quantity preventing the purchase order from being saved. This has been resolved by adjusting the system to bypass the blanket order validation when the pricing method is set to manual ensuring that purchase orders can be modified and saved as intended without unnecessary prompts.

An issue was identified where modifying data on a backorder in the system caused incorrect updates to the job quantities linked to a Sales Order. Specifically when a job was created for a certain quantity from a Sales Order shipping a partial quantity and then modifying any data on the backorder incorrectly adjusted the job's planned and completed quantities. This discrepancy led to confusion about the actual quantities completed and remaining. The development team resolved this issue by implementing changes to ensure that job quantities linked to a Sales Order remain unchanged when updates are made to a backorder maintaining the integrity of the original job setup.

When creating a new deal by copying an existing one the system now automatically updates the deal name to reflect the most current item information. Previously the copied deal retained outdated item names which could lead to inconsistencies. A new function has been implemented to ensure that the deal name is always updated to match the latest item details during both copy and save operations.

We have addressed an issue where modifying sales order dates would mistakenly reset promotion values to zero if the promotion was not date-based. Now when you update any date fields such as Scheduled Date Completed Date Service Date1 or Sales Date 5 the promotional discounts will remain consistent and not revert to zero. This ensures that any flexible percentage or price-based promotions previously applied to a sales order will persist maintaining accuracy and reliability in promotional calculations.

An issue was identified where modifying a drop shipment sales order (SO) would inadvertently alter the quantity on the associated purchase order (PO). This occurred when there was a mismatch between the sales unit and the purchasing unit. The development team resolved this by implementing a conditional check to ensure that the PO quantity is correctly updated through unit conversion when these discrepancies exist. This change ensures that the quantities remain consistent between linked orders.

We have resolved an issue where users without the necessary security permissions were unable to edit Sales Order lines after attempting to create a job from a Sales Order line. Previously if a user without the 'edit production jobs' permission selected the 'Create Line Job' option they would encounter an error and the form would display blank fields preventing further edits. The system has been updated to check for the required permissions before attempting to open job-related forms. This ensures that users can now proceed with creating jobs from Sales Order lines without encountering errors even if they don't have the permission to edit production jobs.

In the cash register system an issue was identified where the split payment option displayed all available payment methods rather than just those designated for point-of-sale use. This has been resolved by ensuring that only payment types marked as suitable for the cash register are shown when using the split payment option. This improvement filters out any non-applicable payment methods providing a streamlined and accurate selection process for users during transactions.

The customer has requested an enhancement to the Sales Engineering Order import feature allowing it to process EHX files. Previously the import would fail due to the absence of a top-level panel ID element. To address this the import function has been modified to search for and utilize a 'Grandfather' element which is a label found up to five levels higher in the hierarchy. This change ensures that the import process can successfully locate the necessary information and complete without errors thereby improving the efficiency of handling these specific files.

The Print to Email functionality has been updated to improve user experience when selecting options for sending documents. Specifically the Contact field will now be grayed out when the Manual option is selected in the Email To field preventing any confusion about which contact is being used. This adjustment ensures that users do not mistakenly enter an incorrect contact when the default contact is not automatically populated. Additionally the Vendor option will continue to display available contacts as expected.

We have resolved an issue where non-Single Sign-On (SSO) users were unable to complete e-signatures because they were prompted to enter Okta credentials. To address this we introduced a 'Single Sign-On' button on the e-signature form similar to the login form. This button is visible only when the system is set up for SSO. Users can now choose to authenticate via SSO or use their regular credentials. For SSO-only users the system will prompt them to sign via the SSO provider if they attempt to use non-SSO credentials. These changes ensure that both non-SSO and SSO users can complete e-signatures as needed with adjustments made for better compatibility with both Azure and Okta systems. The Okta configuration was specifically refined to open the popup correctly streamlining the authentication process without extra server configurations.

The issue of high CPU usage in Deacom Cloud Local has been addressed by introducing a delay in the loop that listens for incoming data. Previously the loop ran continuously without pauses causing spikes in CPU usage when the service was not actively connected to a Deacom system. This change ensures that the CPU remains stable with usage levels around 0% to 0.5% when the service is running regardless of whether Deacom WebServer Console or Deacom Automation Console is active. Users will now experience more efficient CPU usage preventing interruptions or the need for frequent service restarts.

An issue was identified where users were unable to select items from a dropdown list due to the last 20 options displaying on a single line in certain browsers. To resolve this a utility function was implemented to sanitize special characters that could interfere with the dropdown rendering. This change ensures that all options are displayed correctly and can be selected in Chrome Edge and Firefox. Users can now interact with the dropdown without any display issues.

We have addressed an issue where date fields were not functioning correctly for users with Canadian English settings. Previously when the language was set to English (Canada) the visual format of dates changed but users were still required to enter dates using the English format. This discrepancy led to problems with date entry where fields would either blank out or populate incorrect dates. To resolve this we modified the underlying code to ensure that the 'Today' button and other date entry methods now correctly adhere to the YYYY-MM-DD format for Canadian settings. This fix ensures that date fields are consistent and reliable across all systems.

Users reported that certain items were being counted multiple times during the 4-week cycle count for 'A' category items. This issue has been resolved by revising the filtering process in the inventory system. The solution involved integrating new filters that prevent items from being unnecessarily repeated in cycle counts. This ensures that each item is counted only once per cycle maintaining accurate inventory records. The development team has implemented changes to utilize existing filters for gathering items and clearing flags which streamline the cycle counting process and prevent duplication. As a result items are now correctly included in cycle counts without repetition.

An issue was identified where running certain favorite reports resulted in an error due to improper handling of date filters. This error occurred when the start date type was set to 'None' leading to a null value issue. To resolve this the system now correctly formats date filters using the 'yyyy/mm/dd' format and assigns a default minimum value when the start date is unspecified. These changes ensure that reports display correctly without errors improving the reliability of favorite report functionalities.

The default value functionality for the 'Finish Linked Job To' field in the form layouts has been corrected. Previously users experienced issues where the default setting did not apply as expected and unwanted options remained available in the dropdown menu. The development team has removed a conditional exclusion that was preventing user defaults from being applied correctly in forms for creating new registries. After implementing this change the default value now successfully defaults to 'Inventory' and only the intended options are displayed. This enhancement improves the user experience when managing Bill-To settings and Prestaging configurations.

The recent update resolves an issue with the 'Map' function in the data import tool which previously did not support destinations with multiple tables such as Formulas and Sales Orders effectively. Users can now map multipart destinations without losing any tables ensuring that all necessary calculations occur seamlessly. The update allows for smooth transitions between tables retaining mappings for each destination and preventing the removal of any tables after selection. This enhancement ensures that mapping fields from source files populate correctly across all tables improving the functionality and reliability of the import process.

The feature modify icon now correctly responds to the shortcut keys 'Shift' + 'ALT' + 'M' allowing users to modify entries as intended. Additionally access to set shortcuts for the Modify icon in the form layout has been restored enhancing user functionality and experience.

After upgrading to a newer version of the DEACOM software users experienced an issue where the Cloud Local program hosted on a local server would lose connection to the production environment after printing a single document. The problem was traced back to the Cloud Local service which continued to run but failed to display printer options after the initial document was printed. The resolution involved a series of improvements including bug fixes performance optimizations and feature enhancements. These changes were designed to stabilize the connection improve system efficiency and ensure that the Cloud Local printers remain accessible after document printing. Additionally security measures were strengthened to protect user data and enhance overall system reliability.

In previous updates custom report types in the system were inadvertently reverting to default settings causing user-defined report types to change back to base Deacom types after an update. This issue has been resolved by removing the code responsible for this reversion. Now when users modify a report type such as changing it to Other" it will remain unchanged through subsequent updates maintaining the user's settings consistently."

An issue was identified with the Single Sign-On (SSO) Authentication setting where selecting 'Email' as the authentication method would revert to 'Username' upon reopening the options. This has been resolved by ensuring that if the 'Email' option is chosen it is saved and displayed correctly. The system now checks the SSO authentication method setting and maintains 'Email' as the selected option if it was initially set otherwise defaulting to 'Username'. This fix ensures that user preferences for SSO authentication are preserved as intended.

A recent update has improved the functionality of form layouts by ensuring that fields marked as 'unique' effectively prevent duplicate entries. Previously marking a field as unique did not stop duplicate values from being saved which could compromise data integrity. The development team has enhanced the system to call a method that checks for uniqueness when saving records. This method now accurately identifies whether a field is empty before checking for duplicates eliminating false negatives. As a result users will receive a prompt or warning when attempting to enter a duplicate value in a field designated as unique ensuring better data management and consistency.

The issue with the visibility and consistency of icons in the sales order interface has been addressed. Previously the close minimize-maximize and pin icons were difficult to see as they appeared gray and turned white upon hovering unlike other icons that were white and turned orange. To enhance user experience and maintain uniformity across the interface these icons have been updated. They will now appear white by default change to orange when hovered over and turn light gray when pressed. This update applies specifically to the default theme ensuring that the icons are easily visible and consistent with the rest of the interface.

Improvements were made to the cache refresh process which now allows users to access cached data without delay during updates. The cache refresh interval has been optimized from 1 minute to 5 minutes and the performance of the cache was significantly enhanced reducing refresh times from 13 seconds to instant for users.

A technical issue was identified where users encountered an error when using the 'Page Down' key on the Item Master Features Overrides form. This has been resolved by adjusting the system settings to prevent the error from occurring. Users can now navigate through the form without experiencing any issues ensuring smooth operation and improved functionality.

In the latest update an issue was addressed where the data publishing feature did not align with fiscal date settings. The development team has introduced new options in the data publishing form to support both calendar and fiscal date ranges. This enhancement ensures that users can select dates based on their fiscal periods preserving the functionality that was available in the earlier version. The update includes new selections for start and end dates allowing users to choose specific fiscal year and month options thereby providing greater flexibility and accuracy in data reporting.

We've resolved an issue where the Workflow report in the Sales Order Reporting module failed to display any data regardless of the filters applied. Our development team has corrected the filter logic ensuring that the report now accurately retrieves and displays the correct records. Users can run the report with various filters including wide open settings and expect to see the appropriate data returned.

After a recent upgrade users experienced issues with the search functionality and arrow key navigation within the system. Specifically the 'Search All Columns' field was intermittently blacked out and the arrow keys were inconsistent when navigating lists. The development team addressed these issues by refining the logic that controls the rendering of the search toolbar ensuring that it retains its functionality even when navigating between different lines. Additionally improvements were made to clear elements properly enhancing the overall user interface experience. These changes have resolved the problem ensuring that the search field remains visible and the arrow keys function correctly once focus is shifted to the grid providing a smoother and more reliable navigation experience.

A problem was identified where an email trigger set up for exporting grid data was not attaching the expected Excel file. The issue was due to the system's inability to support attaching saved queries from the query tool into trigger emails. To resolve this the code was updated to allow these attachments ensuring that emails now include the correct Excel file when the trigger is activated. This enhancement improves the reliability of email notifications with attached grid exports.

An error was occurring when users attempted to adjust the layout of certain grid elements specifically when widening the layout resulting in a Target Exception message upon saving. This issue was present in both the Production and Validation environments. To resolve this a development update was made to ensure that certain properties particularly those related to passwords are checked for existence before allowing any updates. If these properties are absent the system will now ignore the update attempt preventing the error and allowing the layout changes to be saved successfully.

In a recent update an issue was identified where email attachments sent from the system were being renamed to match the email subject line. The development team addressed this by ensuring the attachment name remains distinct from the email subject preventing any automatic renaming. Users can now send emails with attachments that retain their original names regardless of the email subject enhancing clarity and consistency in communication.

An update to the User Group Master Security table was causing all user group names to display incorrectly as deacom." This issue was resolved by adjusting the system's logic to ensure user group names are correctly displayed. The update involved modifying the logic to replace any undefined columns with the actual user group names rather than default captions. This change ensures that each user group name is accurately represented in the table improving clarity and functionality for users."

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.

A recent update has addressed an issue that prevented users from successfully de-issuing Master Lots through the WMS system. The underlying logic has been improved by introducing new variables specifically for handling Master Lots enabling seamless integration with jobs and sales orders. Following these changes users can now scan or manually enter Master Lot numbers without encountering errors ensuring a smoother experience when managing staged inventory.

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.

In Warehouse Management System (WMS) an issue was identified where receiving inventory transfer transactions (ICTs) could inadvertently change the system lot numbers resulting in all pallets sharing the same lot number. This issue has been resolved by ensuring that the system lot numbers remain unchanged during the receiving process. The solution involved updating the data handling process to correctly filter and assign quantities to each lot individually preventing the duplication of system lot numbers. This fix has been implemented in the system ensuring that each pallet retains its unique system lot number upon receipt maintaining accurate inventory tracking.

A recent update to improve warehouse management system connectivity inadvertently caused a problem where items could be mistakenly moved into quarantine status during inventory transfers. Specifically the system failed to reset the 'Move To' field after completing a transaction leading to subsequent items being incorrectly placed in quarantine. This issue has now been resolved by ensuring that the 'Move To' and 'Move From' fields automatically reset to 'Inventory' status after each successful move transaction. This fix prevents the unintended quarantine placement of items and restores expected functionality in inventory management processes.

The issue of expiration dates not populating correctly in the Warehouse Management System (WMS) during production processes has been resolved. The development team enhanced the logic used to filter lot records ensuring that the system selects the oldest available expiration date from unused lots. This adjustment guarantees that the correct expiration date is applied when multiple finishes are completed. The improvement involved adding a specific condition to the lot selection process which accurately retrieves the appropriate expiration date. Users can now expect WMS to correctly reflect the oldest expiration date of remaining materials aligning with the functionality already present in the main application.

In the warehouse management system there was an issue where pre-staged inventory moved successfully but lost its job number assignment during the process. This problem has been addressed by updating the logic that filters inventory during moves. Now when users attempt to move inventory the system correctly identifies and retains the job number assignment by comparing specific inventory type values. This ensures that the inventory remains linked to its job number maintaining accurate tracking and assignment throughout the move process.

A security issue was identified where users with restricted permissions were still able to access the 'De-issue All' function in the Warehouse Management System (WMS) using a scanning device even when their permissions were set to 'No' for this action. The resolution ensures that the 'Inventory - De-issue All' security setting now correctly applies to both the main application and the WMS interface. Users with this setting disabled will no longer see the 'De-issue All' button in the WMS aligning the functionality with the main application and preventing unauthorized de-issuing of inventory. This update enhances the security controls across all platforms ensuring consistent user access based on defined permissions.

An error occurred when attempting to move inventory using a scan gun resulting in a confusing NullReferenceException message. This issue was triggered when the system failed to locate a part number associated with a specific lot. The development team addressed this by replacing the unclear error message with a more informative prompt that indicates when the Unit of Measure (UOM) is inactive. This update ensures that users receive a clear explanation of the issue specifically highlighting an invalid UOM when attempting to move inventory.

An issue was identified where the lot quantity displayed during the final staging of a sales order in the Warehouse Management System (WMS) was inaccurate. This discrepancy occurred when scanning lot labels resulting in incorrect quantities being shown for both the system lot and the required order. The resolution involved recalculating the quantity based on unique lot identifiers specifically userLot and systemLot. Filters applied to these identifiers were considered and the system was adjusted to recalculate quantities if the systemLot value was reselected. The development changes included updating the calculation method to group by these lot identifiers and applying prefilters when available ensuring the displayed quantities accurately reflect the inventory and sales order requirements.

An issue was identified where the Warehouse Management System (WMS) could not correctly determine and scan inventory lots resulting in a 'No lots found' error. The resolution involved enhancing the system's logic to ensure that the 'Type' field on the find form defaults to the user's 'Move From' selection if changed. This adjustment prevents confusion when the find form loads after scanning a lot label with a different type filter than expected. Additionally the logic was expanded to automatically apply when the find form displays due to ambiguous scans improving the system's ability to accurately identify inventory. The problem of invalid sales order prompts was addressed by creating a new inventory lot for testing which resolved the issue of WMS not finding inventory tied to orders. The successful resolution was confirmed through various steps including creating and reserving new sales orders scanning and verifying inventory movement in reports.

A recent update has improved the handling of substitute parts in the Warehouse Management System (WMS) when reserving items for a sales order. Previously the system incorrectly calculated quantities when multiple substitute parts were used for a single original part. This issue has been resolved by enhancing the process to ensure that only the specified quantities of substitute parts are reserved. Additionally new security measures have been implemented to verify user permissions when substituting lots.