17.03.010.0002 Release Notes

The system has been updated to enhance clarity and consistency by changing the caption 'Vendor Invoice' to 'Invoice Number' across all relevant areas. This modification has been implemented throughout various forms and grids within the application ensuring that users encounter the updated terminology consistently during their interactions with the invoicing features.

In the latest update a new feature has been added to enhance the usability of the invoice review process. Users can now easily access attached invoices through a newly introduced 'View Docs' button on the invoice receipt form. This addition mirrors the functionality found in purchase orders allowing users to open and review documents directly from the form. This improvement streamlines the workflow by providing direct access to necessary documents ensuring a more efficient review process.

We have enhanced the system to store detailed information at the line level for vendor invoices such as invoiced quantities and prices. This update allows users to manually enter these details providing immediate access to this data before our AI Invoicing process is fully implemented. Additionally this information can now be included in reports aiding in the evaluation of vendor invoicing performance. The update also supports saving temporary invoices offering more flexibility in managing vendor invoice data.

Users will now be able to view bank account numbers directly on relevant forms and grids within the system enhancing their ability to verify and manage financial information. Previously these numbers were encrypted and hidden making it difficult for users to see what they were entering. The update involves changes to the system that decrypt and display bank account numbers in the 'bankadd' form and 'bankmain' grid. The field in the 'bankadd' form is no longer treated as a password allowing users to see the actual account number instead of asterisks. Additionally while the database maintains encryption for security the system now properly displays decrypted account numbers. Users may need to re-save any account numbers previously stored with an older encoding method to ensure they appear correctly with the new system changes.

A new feature for direct invoice entry has been introduced simplifying the process for accounting users to enter expense invoices. Previously users had to navigate through a complex purchasing menu and purchase order (PO) creation steps which were not necessary for expense invoices. The new functionality allows users to enter invoice details such as invoice number and payment date directly without the need to post the invoice immediately. Additionally this update supports AI-assisted invoice creation where expense invoices can be submitted to corporate AI endpoints for automatic creation allowing the accounting team to review and post them efficiently. This streamlined process is now accessible through the accounting menu enhancing user experience and operational efficiency.

A recent update has enhanced the Short/Over Pay function allowing it to process successfully even if certain fields under the Ship-To Order Defaults are left blank. Previously users encountered errors when these fields were not filled but now the system automatically overrides missing Ship-To details with corresponding Bill-To information. This improvement ensures smoother processing by checking the Ship-To Currency and other fields; if they are blank the system fills them with the Bill-To Currency and relevant data. This fix is included in versions 17.02 and 17.03 and is referenced for later versions as well. This change simplifies the process and eliminates the need for manual input of default values in the Ship-To section.

We have streamlined the process for handling payments on account by adding a new feature to the Cash Receipts form. This enhancement introduces a Terms search box allowing users to easily select payment terms when creating a payment on account. This eliminates the need for constant adjustments to system settings and ensures that payment terms are accurately applied based on the user's selection rather than defaulting to preset terms. This change not only simplifies the workflow but also accommodates various payment methods such as credit card and gift card transactions ensuring flexibility and accuracy in order processing.

A new feature has been developed to streamline invoice submission using AI technology within Deacom. Users can now submit invoice files to the Nexus AI platform for OCR analysis which automatically processes the files and matches them with the corresponding Purchase Orders in Deacom. This integration includes a specialized form for submitting files ensuring they meet size and type requirements and directing them to a designated folder for processing. The system categorizes files into success processing and failure folders for easy tracking. Additionally an external program continuously checks for unprocessed batches attaching files to the appropriate Purchase Orders once analysis is complete. This development enhances efficiency by reducing manual input and supporting accurate invoice management.

The Invoice Variance Summary Report has been enhanced to provide a clearer and more streamlined presentation of Purchase Order (PO) line adjustments. The report now utilizes new fields for invoice quantity and price to directly display variances simplifying the process by consolidating adjustment lines into a single entry when linked to existing PO lines. This update removes the need for separate records of these adjustments unless they are not linked. Additionally new column headers and a Quant Var" column have been introduced to highlight quantity discrepancies between original PO data and invoice information offering a more intuitive understanding of variances."

We have enhanced the orders to invoice grid by adding several new fields allowing users to identify variances at the header level more efficiently. These fields include due date to pay receipt balance invoice amount and invoice variance which help compare expected payment amounts with actual invoice amounts. The logic for calculating these fields now aligns with the existing form logic ensuring consistent and accurate data. Additionally the assignment of due date and date to pay columns has been corrected to display accurate information. If relevant data is not available these fields will remain empty. These improvements have been implemented in version 17.03 and onward.

The calculation for the 'Date to Pay' field on direct invoices has been updated to function similarly to purchase order invoices. Now this date is automatically determined based on the vendor invoice date and the specified payment terms. If a discount is applicable the 'Date to Pay' will adjust to reflect the discount terms. This enhancement ensures that when the vendor invoice date changes the 'Date to Pay' updates accordingly. Users still have the option to manually override the calculated date if necessary. Additionally if a vendor has a default term set it will automatically apply streamlining the process and ensuring accurate payment scheduling.

The Unprocessed Invoices form has been enhanced with new functionality to improve usability and workflow efficiency. A Download button has been added to the form providing an alternative method to download selected invoice files from the grid without requiring a double-click action. This gives users a more intuitive and accessible way to retrieve files that need attention. Additionally a new Date column has been introduced to the grid displaying when each file was placed in the failed folder. This column supports filtering capabilities allowing users to sort and view invoices based on their date. The Download All function has also been updated to respect any active filters ensuring that only the currently visible items in the grid are included when performing a bulk download.

• The AI-driven invoicing system has been enhanced to better handle discrepancies between purchase orders and scanned invoices. When the AI process identifies differences between the invoice and the purchase order it now creates variance lines to account for mismatched prices or items not listed on the purchase order. These variance lines are flagged for human review ensuring that only purchase orders with perfect matches are automatically invoiced. Additionally a new feature allows temporary storage of invoices with variances for further inspection. This update ensures that invoice data is accurately recorded and aligned with the AI's findings providing a more reliable invoicing process.
• In the latest update the AI Invoice system has been enhanced to streamline the invoice matching process by focusing solely on numeric data like price quantity and extension rather than part numbers. This change addresses the issue where vendors may use different part numbering systems which previously led to unnecessary mismatches. By relying on intrinsic and verifiable data the system now ensures more accurate invoice processing reducing failures and improving the overall efficiency of the AI-driven invoicing process.
• The AI system has been enhanced to handle invoice due dates more effectively ensuring they match the corresponding Purchase Order in Deacom. If an invoice's due date differs from the expected date on the Purchase Order it will no longer be automatically processed as a perfect match. Instead the invoice will be attached to the Purchase Order and a notification will be recorded in the system to highlight the mismatch. This update improves accuracy in invoice processing and ensures users are informed of any discrepancies in due dates in the invoicing process.
• In the latest update a new feature has been introduced to help users easily locate and manage failed invoices from the AI process. A button labeled Unprocessed Invoices" has been added to the invoice receiving form. When clicked this button opens a new interface displaying a list of file names for invoices that did not process correctly. Users can double-click any file name to download it directly to their "Downloads" folder. Additionally a "Download All" button allows users to download all failed invoices at once as a zipped folder named "Unprocessed Invoices." Furthermore the AI Invoice API Profile URL has been updated to ensure a more reliable connection replacing an outdated URL with new links for both production and testing environments."
• We have enhanced the system to better manage and identify invoices generated by AI. Now when an AI-generated invoice is processed a record stating AI Invoice Entered" is added to the purchase order history. Additionally a new filter option labeled "Inv Entered By" has been introduced in the purchasing invoice form. This allows users to filter invoices based on whether they were entered by AI or a user. We've also added a "Not Entered" status to help users identify orders with no recorded invoice data. Furthermore a new variable in the invoice grid helps identify if an invoice was entered by AI making it easier for users to track and manage AI-generated invoices efficiently."
• The handling of invoice dates in the AI Invoice Automation system has been improved to ensure accurate payment scheduling. Previously the invoice date was automatically set to the current date but now it will be set based on the actual invoice date provided in the scanned document. This update allows the system to better align payment expectations between vendors and customers. If both the invoice date and the due date are present in the invoice PDF automatic invoicing can proceed if the calculated payment terms match the expected schedule. However if either date is missing the system will still record the provided dates but refrain from automatic invoicing ensuring that discrepancies in payment expectations are addressed before processing.
• In this update we have streamlined the AI Invoice process by creating a centralized 'AI Invoice' folder that is automatically generated within the system's 'addins' directory. This change eliminates the need for manual configuration and simplifies access for both cloud and on-premise customers. The 'df_aiinvoicelocation' field and the 'AI Invoice Source Path' option have been removed enhancing the process's efficiency. The AI Invoice system now directly uses this consistent file path for all processing activities ensuring seamless handling of invoices without additional setup requirements.
• A change was made to the AI Invoice Folder Path field within the accounting options. The field previously a text box has been updated to a memo box to allow for more extensive input with a new character limit of 256. Additionally the field's caption has been renamed to 'AI Inv Source Path' to align with standard caption widths. These modifications ensure that the field is consistent with other file path fields.
• In this update the system now automatically assigns the payment due date for AI Invoice submissions based on the due date provided in the invoice itself rather than relying on the terms specified in Deacom. This ensures that the payment schedule accurately reflects the invoice details. Additionally to prevent accidental re-submissions of AI Invoice PDFs the system blocks re-submissions if a temporary invoice receipt value is present on the related Purchase Order. This change prevents orders from being adjusted multiple times by the AI ensuring data integrity and reducing errors in invoice processing.
• The AI Invoice Automation in Deacom has been improved to provide a more streamlined process for handling invoices with high confidence matches. A new feature allows invoices to be automatically applied when they match certain criteria with a confidence level of at least 75% and there are no discrepancies in dollar amounts or quantities. This includes matching fields like PO Number Vendor and Invoice Total. A new checkbox option 'Auto Invoice With No Variance' has been added to enable this functionality for AI invoicing profiles. Additionally a new endpoint and field have been introduced to facilitate these changes ensuring that invoices can be processed and attached efficiently. These enhancements aim to automate the invoicing process further reducing manual intervention and improving accuracy.
• In this update a new field called 'AI Invoice Summary' has been added to the Purchase Order Header. This enhancement allows users to view a summary of AI-generated invoices directly within the Purchase Order or invoice forms provided that AI Invoicing is enabled in the system. When AI invoice processing identifies a match the system now ensures that invoice data is stored and the corresponding invoice document is attached to the Purchase Order. This prevents scenarios where invoice data is present without an attached document or vice versa. The update also ensures that both full and partial matches during AI invoicing result in the correct updating of Purchase Order fields including the AI Invoice Summary. These changes aim to streamline the AI invoicing process and improve data visibility within the system.
• The AI Invoice functionality has been successfully backported from version 17.04 to 17.03. This involved transferring the necessary code and resolving any conflicts that arose during the process. All essential prompts and captions have been re-implemented to ensure seamless operation in version 17.03. The external synchronization component was tested and confirmed to be compatible with the updated version requiring no additional changes.
• In version 17.03.XXX enhancements have been made to the AI invoicing process to improve the accuracy of matching invoice line items with purchase orders. The system now sends additional part and vendor-related information to Nexus AI including the part number part description vendor part number and vendor description for each item on a purchase order. This update allows the AI to consider both internal and vendor-specific part information thereby enhancing its ability to accurately match invoice lines with the corresponding purchase orders. These changes are internal and do not affect the visible behavior of the Deacom system.

The process for submitting AI Invoices has been improved by integrating new logic that collects and converts all received but non-invoiced Purchase Orders into JSON format. This JSON data is then sent alongside AI Invoice file uploads to a new endpoint streamlining the matching process with the necessary Purchase Orders without requiring a direct connection to the Deacom API. This update simplifies the user setup by removing the need for active API credentials. Additionally enhanced error handling has been added to the AI Invoice Automation program to log alerts if the Deacom API is unreachable thus preventing confusing JSON parsing errors from appearing in reports when the connection is unavailable during automatic invoicing.

The Chart of Accounts search endpoint has been successfully integrated into version 17.03 to support the AI Invoice initiative. This update ensures that users can access and interact with Chart of Accounts records through the Accounting module allowing for efficient data retrieval based on various attributes such as ID account number name type and active status. The functionality has been thoroughly validated to ensure accurate and reliable data retrieval enhancing user experience and operational efficiency.

In this update we've enhanced the Purchasing Order History API to better support AI invoicing by including vendor part numbers and descriptions in purchase order lines. This means that when invoices reference our part number the vendor's part number or both the AI can more accurately match these details. The API endpoints now provide vendor item information in the response with a detailed view available in verbose mode and a simplified view in non-verbose mode. We've introduced a new data structure to streamline this information and removed redundant data ensuring more efficient processing and integration with AI systems.

To enhance the clarity and usefulness of the sync report within the Commerce Suite changes have been made to the logging system. Previously frequent 'assembly loaded' messages cluttered the report making it difficult to identify actual issues. Now these events are logged only once per Deacom Service lifetime significantly reducing redundancy and keeping logs concise. Additionally all date and time entries in the report have been standardized to a 24-hour format eliminating inconsistencies and ensuring that all entries are easily sortable and clear. These improvements streamline the reporting process and enhance its effectiveness for users.

The update enhances the integration between the Commerce Suite and Deacom by adding the 's Default Payment Method as optional columns in several grids including Vendor Group Check Run and Manual Checks. This allows users to view and update payment methods directly from the Commerce Suite ensuring accurate and synchronized information across both platforms. Additionally a prior issue with Vendor Groups has been addressed improving the reliability of data synchronization. These enhancements streamline the process of managing vendor payment methods making it easier for users to maintain consistent and accurate records.

We've improved the payment creation process in the Commerce Suite to address issues with payment dates. Previously when users set a payment date for today or earlier the system would automatically schedule the payout date for the following day. Now when creating a payment users will receive a prompt informing them that the payout date will be set for tomorrow if the payment date is backdated or set for today. This allows users to either proceed with the scheduled payout or cancel the transaction. This update ensures clarity and gives users control over the payment scheduling process.

The Commerce Suite Reference (commercesuiteref) and Commerce Suite Status (commercesuitestatus) fields are available in the following Deacom reports and grids.

These fields allow users to view the Commerce Suite payout status and related check or reference numbers:

• Bank Reconciliation (bankrec2)
• Cash Disbursement Detail (checkdtlap)
• Cash Disbursements Summary (viewcashap)

To enhance payment visibility within the Deacom system a new feature has been implemented that introduces the 'Commerce Suite Payment Type' variable to several key grids. This update allows users to view the actual payment method used for transactions directly within the BankRec Cash Disbursement Detail and Cash Disbursement Summary grids. By integrating this variable users can now see the specific payout payment type improving clarity and accuracy in financial records. This change leverages existing API calls to map the payment method ensuring seamless integration with current processes.

The payout process within the Commerce Suite has been refined to better align with updated functionalities from Nuvei and IE. Now when initiating a payout the scheduled payout date which indicates when checks are printed or ACH transactions are initiated will correspond with the payment dates recorded in Deacom. This enhancement ensures that the scheduled payout date matches the date in the PayDate field in Deacom's Paid3 form. Users should note that attempting to backdate payments will result in a failure to create payouts in the Commerce Suite. If backdating is necessary users will be prompted with a notification that the payout will not be created in the Commerce Suite providing them with the option to proceed. This change aims to streamline the payout process and enhance accuracy in date synchronization.

The integration with QuickBooks Online has been successfully migrated to a new external sync system enhancing compatibility with newer integrations. This update restores the login window functionality allowing users to authenticate using either an authorization code or username and password. Additionally improvements were made to address issues with creating and updating terms as well as handling credits for purchase and sales orders. Users will now be directed to the External Sync History report for error messages streamlining the troubleshooting process. These changes ensure a more robust and seamless integration experience with QuickBooks Online.

• We have introduced a new CRM project search feature within the Deacom API. This enhancement allows users to search for CRM projects using specific name fields without needing to fill every field. The update ensures that if certain required fields for specific filters are missing the system will return a clear 400 error message guiding users to provide necessary information. Additionally the endpoint now aligns enums with those used in the main application ensuring consistency in naming and status. These improvements make searching for project data more intuitive and efficient while also enhancing error handling to prevent system crashes when incorrect information is submitted.
• We have enhanced our system's CRM API by updating seven specific endpoints to return more precise data types. Previously these endpoints used a generic response structure. Now each endpoint will provide a response tailored to the type of information requested such as contact project or ticket details. This change improves the clarity and usability of the API ensuring that users receive more relevant and specific information from their queries.

We have introduced new API endpoints for creating and updating CRM contacts enhancing the ability to manage contact information directly through the API. The Create endpoint mirrors the functionality available in our main application allowing for comprehensive data entry including default values and additional grid entries. The Update endpoint enables modifications to existing contact details and their associated data grids supporting operations like adding new entries or removing existing ones when necessary. These enhancements ensure that CRM contact management is more flexible and efficient with robust validation processes to ensure data integrity during updates.

We have enhanced our system's CRM API by updating seven specific endpoints to return more precise data types. Previously these endpoints used a generic response structure. Now each endpoint will provide a response tailored to the type of information requested such as contact project or ticket details. This change improves the clarity and usability of the API ensuring that users receive more relevant and specific information from their queries.

We've enhanced the document management system by incorporating User-Defined Fields (UDFs) into the document reporting grid. This update allows users to add and view custom fields associated with attached documents directly within the grid interface. The system now seamlessly includes these UDFs providing a more tailored and informative document management experience.

We have improved the eCommerce system to ensure that customer-specific part names and descriptions are accurately displayed when a customer part cross-reference exists. Previously the system failed to show these details which could lead to confusion for customers who rely on their own part numbers and descriptions. The update eliminates the need for a specific flag in the Item Master allowing customer part names and descriptions to appear without additional configuration. This enhancement also ensures that multiple cross-references for the same product are correctly managed providing a more comprehensive and user-friendly experience for customers using eCommerce platforms.

We have improved the EDI Import process to ensure that inventory within Master Lots can now be accessed for shipping Sales Orders. Previously inventory in Master Lots was not available for reservation or shipping which posed challenges for certain customers. With the latest update the system now recognizes and utilizes inventory from Master Lots when fulfilling orders via EDI allowing for more efficient order processing. This enhancement was achieved by updating the code logic to include Master Lots in the inventory checks during the shipping process.

To prevent EDI profiles from running in test environments a new configuration has been developed. This update introduces a field called 'Run Condition' in the EDI settings allowing users to specify conditions under which EDI imports should execute. The system will evaluate these conditions before executing any EDI profile. If the condition is empty or evaluates to true the import proceeds as usual. However if the condition evaluates to false the import is halted and an error message is recorded in the EDI Import History. This enhancement ensures that EDI imports are only executed in the intended production environments providing better control and reducing the risk of unintended operations in test setups.

In the Final Staging process users were encountering an error message instead of the expected prompt for a job number when pre-filters were not changed. To resolve this the system now checks for the presence of a job or sales order number early in the process. If this information is missing users will receive a clear prompt indicating the need to fill in the required details. This change ensures smoother operation and helps users provide necessary information upfront.

A new feature has been implemented to enhance the Order MRP report for Sales Orders allowing users to filter results by facility. Users can now choose to view inventory quantities from either all facilities or just the specific facility associated with a Sales Order. This functionality is controlled via a new option 'SO MRP Facility' added to the Sales Options form. The form now includes a dropdown menu with options for 'All' facilities or the default 'Order Facility.' This update ensures that when generating an Order MRP report users have the flexibility to tailor the report to their specific needs either by consolidating inventory data across all facilities or focusing solely on the relevant facility for the order.

An update has been made to ensure that Internet Sales Orders are properly displayed in the drill-down view of the Material Requirements Planning (MRP) system. Previously Internet Sales Orders were excluded from the detailed view even though they were included in the overall demand summary. This issue was causing confusion as planners could not reconcile MRP demand totals within the drill-down view. Now when the Internet Orders filter is set to include these orders the system correctly adds them to the detailed view aligning the summary and drill-down data. This enhancement makes it easier for users to track and manage all types of sales orders directly within the MRP interface.

The issue regarding the PDF file naming convention has been addressed. Previously when printing job reports to PDF the files were named using a generic format that only included the job number. This has been updated to include the specific report name in the PDF file title similar to the naming convention used for sales order PDFs. This change ensures clarity and consistency making it easier to identify the contents of the PDF files at a glance.

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.

We've enhanced the Jobs Search functionality by introducing a new query parameter called 'paginateby' allowing users to control pagination by either Job Header or Job Detail (JobLine). By default pagination is set to Job Header but users can opt for more detailed pagination by selecting JobLine. This improvement provides greater flexibility in managing job search results enabling users to choose how their data is organized and displayed. This change was made to address user needs more effectively offering a refined approach to data retrieval in the system.

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 system has been updated to include the Job Closed Date in the API responses for job-related searches. Specifically the Job Closed Date is now part of the data returned by the Job Requirements Search and Job Routing Search endpoints within the Public Deacom API. This enhancement allows users to access the closure status of jobs more easily when performing searches through these endpoints. While the Jobs Search Detail endpoint remains unchanged a new ticket has been created to address pagination needs in the production jobs search endpoint. These updates facilitate better tracking and management of job statuses in the production process.

The Newtonsoft.json library within the autofinisher component has been updated to version 12.0.3. This update enhances the application's performance and compatibility ensuring smoother operation and integration with other system components. The development team has focused on optimizing backend processes to improve load times and overall user experience. Additionally the application's user interface has been refreshed to align with modern design standards enhancing readability and accessibility. These improvements aim to streamline navigation and provide users with a more intuitive and efficient experience.

The AutoFinisher application now includes a new MSI-based updater that can automatically upgrade or downgrade the client as needed, without any user action required.

• A new installer file, AutoFinisher.Client.Installer.msi, is located in the main Deacom application folder.
• When the AutoFinisher Client starts—and again when a user logs in—it automatically connects to the AutoFinisher service to check for updates. If an update is available, the client will download it, close itself, and relaunch automatically with the updated version.

In this update a bug affecting the handling of boolean fields in AutoFinisher entities was fixed. The issue arose due to a new field that was incorrectly defaulting to true regardless of the actual database values. To resolve this a specific setting was removed from the JSON serializer configurations ensuring that the fields are now correctly interpreted. Additionally a new feature was implemented to manage scale readings allowing for the option to reset the scale to zero between finishes. This ensures accurate recording of finishes whether the scale is in a simulated or actual environment. The changes are effective from version 16.04 and above.

In this update the system now prevents users from copying Purchase Orders (POs) that are associated with inactive vendors. Previously users could inadvertently create new POs from existing ones linked to vendors who were no longer active without receiving any warnings. Now if a user attempts to copy a PO with an inactive vendor a prompt will appear informing them that the vendor is inactive and the copy action cannot proceed. This enhancement ensures that all vendor activity statuses are checked before allowing PO duplication thus maintaining accurate and current vendor information in purchasing operations.

In recent updates we have addressed the absence of Purchase and Pricing Units of Measure in the Blanket Purchases grid view. Users will now find these units readily accessible enhancing the clarity and functionality of purchase order reporting. This improvement ensures the necessary data is displayed without compromising performance aligning with other reports that already feature similar fields.

We have resolved an issue where updating blanket purchase orders was not functioning correctly. Previously when users edited the quantity on a blanket purchase order the Open Blanket" field incorrectly reset to zero and the unit price was removed despite the item being selected. The system now properly maintains the predefined price and updates the "Pricing Method" field accordingly when only the quantity is changed. This ensures that the "Open Blanket" value remains accurate and the unit price is retained. These improvements enhance the reliability and accuracy of managing blanket purchase orders."

In this update we've enhanced the system's purchasing capabilities by porting advanced search functionalities to version 17.03. This includes new endpoints for searching Purchase Orders which now support pagination allowing for more efficient and organized data retrieval. A new data access object has been introduced to improve querying and filtering based on specific request parameters ensuring accurate and relevant search results for users. These improvements aim to streamline the purchasing process and support ongoing efforts related to AI Invoice integration.

Users who previously could not approve quality control (QC) results due to security settings can now do so when all required test results are entered even if they did not input the results themselves. This change ensures that the 'Approve QC' option becomes available when there are complete and valid test results in the system. Additional checks such as ensuring all tests pass are conducted when finalizing QC to maintain quality standards.

A recent update has improved the handling of inventory lots in the Warehouse Management System (WMS) by enforcing user permissions more strictly. Previously users without the appropriate permissions could issue items that were still pending quality control (QC) to jobs. With the new changes users lacking the necessary permissions will no longer see lots that are in a QC Pending status when searching for lots. The system now checks user permissions before displaying lot information ensuring that only lots not pending QC are visible. Additionally the option to view 'Pending QC' lots has been removed for these users maintaining the integrity of the inventory process.

An API endpoint has been introduced to streamline the entry of Quality Control (QC) results for Purchase Orders within the system. This new feature allows users to input QC data directly through the API mirroring the functionality available in the main application. The endpoint supports both standard QC tests and ad hoc tests ensuring flexibility in managing QC processes. Security measures are in place to ensure that only authorized users can submit QC data maintaining the integrity of the system's permission settings. Furthermore the API respects existing configurations such as e-signature requirements and prevents any unauthorized overrides. This development enhances the efficiency of QC data management by allowing seamless integration with external systems supplying test results.

In this update we have improved the functionality of several Quality Event forms by making the 'Name' field both mandatory and unique. Previously users were able to save entries with either empty or duplicate names which could lead to confusion and errors. The forms affected include Quality Event Line Types Quality Event Sources and Quality Event Types. With these changes users must now provide a unique name for each entry ensuring better data integrity and consistency across the system.

The Hazard Class field has been updated to provide users with more flexibility in classifying items. A new blank option has been added allowing users to leave the field empty if needed. Additionally a specific option for Combustible Liquid" labeled as "Comb Liq" has been introduced. These changes enhance the selection process for hazardous materials ensuring compliance with regulatory standards. Users can now easily choose the appropriate classification when managing inventory and maintaining records for dangerous goods."

In response to the request for new fields in the system several enhancements have been implemented. New database fields have been added to optimize product and shipping information management. Specifically fields for 'Cases per Layer' and 'Layers per Pallet' have been introduced to improve inventory tracking while 'Transit Days' fields have been added to both billing and shipping sections to enhance logistics planning. These updates are now integrated into the sales order date calculations ensuring more accurate scheduling and delivery estimates. The changes streamline data handling and improve operational efficiency by aligning product and transit information with sales processes.

We've enhanced the system to improve transaction clarity when using Net1 payments through the Cash Receipts form. Now order numbers will be automatically included in the transaction description making it easier to identify the purpose of each payment. Additionally the 'ca_authcode' field is now accessible in the relevant grid allowing for better tracking and matching of transactions. These improvements ensure that descriptions are clear and concise with a maximum character limit to accommodate multiple orders when necessary.

In this update we have enhanced the sales order process to ensure that the 'Select a Pricing Order' window consistently appears when entering a sales order line. Previously the window did not appear if all applicable pricing order lines originated from the same pricing order. With the new update if a single pricing order contains multiple lines for the same part with different pricing values the system will now prompt users to select the appropriate line. This change improves accuracy by checking matches at the line level and ensures users are always given the correct pricing options.

A technical issue in the Sales Order Reporting system was preventing users from obtaining the expected results when applying custom criteria to filter multiple item categories. Specifically when users attempted to use custom criteria with two item categories they were receiving no results instead of the anticipated combined total. The development team resolved this by ensuring that category filters from the main selection and custom criteria were properly merged into a unified filter set within the query logic. This adjustment allows the system to accurately return results without exclusions thus enabling users to filter on multiple categories successfully. Users can now confidently apply custom criteria for item categories expecting accurate and comprehensive results.

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 integration with Avalara has been updated to accommodate situations where only latitude and longitude coordinates are available without a physical address. Previously tax calculations required a street address to derive these coordinates which posed challenges for deliveries to locations like oil fields that lack traditional addresses. Now if latitude and longitude are provided for a delivery location Avalara will use them directly to determine the appropriate tax rates. Customers must ensure the accuracy of these coordinates as the system will not validate them. This change streamlines tax calculations for areas without defined street addresses enhancing flexibility and efficiency in tax processing.

When processing multiple payments in the Cash Receipts section the system now automatically increments the payment reference number for each transaction. Previously the same reference number was applied to all transactions which could cause confusion. With this update if the initial reference number is numeric it will increase by one for each subsequent payment ensuring each transaction is uniquely identified. This enhancement streamlines the accounting process by providing clear and distinct reference numbers for each payment entry.

The system now allows customization of project number lengths. Previously limited to a year plus four digits users can now configure this to include five or seven digits beyond the year. A new field has been added to the database to manage this setting ensuring project numbers can be tailored to specific needs. The update ensures consistent formatting across all relevant forms and grids enhancing the system's adaptability to large-scale project tracking.

We have improved the way freight-related messages are displayed to users by replacing hardcoded error messages with system prompts. This update not only ensures consistency in messaging but also lays the groundwork for future localization efforts. Users will continue to see the same messages at the appropriate times but these messages are now easier to adapt for different languages and regions.

The sales order API has been updated to include the 'to_confirm' date in the data returned. This enhancement allows users to view the shipping confirmation number in the responses from both the Sales Order Search and Sales Order Header Search endpoints. These changes improve the accessibility and visibility of order confirmation details within the API streamlining the process for users to track their sales orders efficiently.

An issue was identified where forecast demand was not correctly reflecting as indirect demand in certain configurations. This occurred when items were set up to support enhancements related to indirect demand management. To address this the system logic was updated to ensure that products are only considered for removal if all related facilities are marked as not manufactured. This change ensures that indirect demand is properly accounted for when viewing forecast demand across different items and facilities. The update improves the accuracy of demand forecasting by ensuring that indirect demand aligns with forecasted values.

Users who have restrictions at the facility or facility group levels can now view the 'Vendors > Items Supplied' report which previously returned blank results. This issue was resolved by adjusting the query to ensure that users with these restrictions can see vendor parts associated with empty facilities. The system now allows such users to access vendor information without specifying a facility provided the vendor is available to all users or falls within their restriction parameters. This change enhances the accessibility of vendor data for users with specific facility restrictions.

We have integrated the Ally chat bot into Deacom enabling users to interact with an AI-powered assistant directly within the application. This new feature remembers past interactions and can renew tokens for continued sessions. Users will notice a new AI Chat icon on the top right of the Deacom main screen which opens a panel for engaging with the chat bot. This enhancement includes various UI updates such as a new menubar icon and a fly-out panel for the chat feature. Additionally we have added new methods to support AI chat functionalities allowing for seamless communication and information retrieval within Deacom.

In the latest update the title of the AI chatbox within the Deacom system has been changed to AI Assist" to align with marketing and branding efforts. However due to legal concerns the decision was made to remove the title entirely. The tooltip for the AI chat icon has also been updated to display "AI Assist." These changes ensure consistency in how the AI feature is presented across the platform."

A new feature has been introduced that enhances the functionality of the Save button across various forms. Users can now save and close a form by right-clicking the Save button providing a convenient way to complete tasks without leaving the form open. This update allows users the flexibility to choose between saving and continuing work or saving and closing the form immediately. The system automatically detects a right-click and executes the save-and-close action streamlining workflow and improving efficiency.

We have addressed the significant delay experienced when using the Master Lot Search feature during the final staging process. Previously users faced wait times of up to two minutes for search results particularly when dealing with a large number of master lot numbers. To improve performance we've optimized the search process by implementing conditions that reduce unnecessary query executions. This change significantly decreases the time required for the search results to appear enhancing overall efficiency. Users can now expect a more responsive experience with search results loading in approximately 25 seconds streamlining the final staging workflow.

We have enhanced the system to better track when records are deleted by users. A new logging mechanism has been introduced creating a special database table to record details of each deletion including the user responsible the date of deletion and the data that was removed. This allows for comprehensive tracking and reporting on deletions across various parts of the system. The method used to delete records has been standardized ensuring that every deletion is logged consistently. Additionally for certain forms like Job Entry and Sales Orders instead of completely removing records they are now marked as historic preserving their data while indicating they are no longer active. This update improves transparency and accountability in data management.

In the latest updates a new feature has been introduced to enhance how property names are specified within our system. The DBOShortName attribute was created to allow for more concise naming of Data Transfer Object (DTO) properties. If this attribute is not present the system will default to using the DBODescription tag. This enhancement lays the groundwork for future expansions and ensures consistency across different versions. The DBOShortName attribute is now part of the TableModel which will eventually serve as the primary reference for property names simplifying the naming process and improving overall system organization.

We've improved the user experience by adjusting the size of the form used for adding favorites and auto exports. Previously users had to scroll to view the full content when opening these forms which was inconvenient. Now both forms open at a larger size eliminating the need for scrolling and ensuring all necessary information is visible immediately. This enhancement provides a smoother and more efficient interaction for users managing their auto exports.

In response to changes from Gmail and Microsoft we've enhanced our system to support Gmail OAuth and updated our integration with Microsoft by transitioning from the deprecated EWS to the new Microsoft Graph API. This update involves the implementation of the EmailGraphService which now handles all email communications. Users can select their email provider—Microsoft Gmail or Other—through a new system option which enables corresponding configuration fields. This change ensures continued seamless email functionality and introduces new prompts for handling email process failures. Additionally existing method signatures have been preserved to minimize disruption while references across various components have been updated to align with the new service.

To enhance the efficiency of the Performance Diagnostic Utility a new feature has been introduced that allows users to quickly select or deselect all options at once. This improvement addresses the cumbersome task of manually checking or unchecking numerous options in a multi-tenant environment thereby saving time and streamlining the diagnostic process. The addition of 'Check All' and 'Uncheck All' buttons ensures users can efficiently manage multiple instances improving overall performance diagnostics. The buttons are conveniently located at the bottom right of the screen ensuring easy access and functionality across different versions of the Deacom platform.

We have resolved an issue where the system was unable to attach a query tool grid to a trigger email. The system now accurately distinguishes between different types of grids such as query tool grids favorite-published grids and regular grids. This ensures that when setting up a trigger the correct grid type is selected for attachment. We've added specific checks to handle grid information and prevent errors if the grid is not found. These improvements guarantee that the attachment process works as intended allowing users to configure and send emails with the correct grid attachments seamlessly.

To enhance system performance three new indexes have been introduced to the dtstaging database table. This improvement addresses previous performance-related issues by optimizing how data is accessed and retrieved. The indexes focus on key fields within the table ensuring more efficient processing and quicker response times for operations involving this data set.

The process of printing and sending invoices was experiencing significant delays taking several hours to complete. To address this the development team optimized the code by reducing the complexity of a loop from exponential to linear. This was achieved by implementing a dictionary to store unique values which significantly sped up the iteration process. As a result the average time to print documents improved from 12 seconds to 8 seconds per document. This enhancement ensures that invoices can be processed more efficiently reducing the overall time required for completion.

We've streamlined the database logging process to address unnecessary data growth by disabling logging for certain historical entries. Specifically logging for the 'dxexternhist' table has been turned off reducing clutter and enhancing database efficiency. Additionally changes to the 'dtd2' records will now be properly tracked ensuring modifications are accurately recorded without unnecessary updates. Previous issues with record identifiers were already resolved in earlier updates. This cleanup will help maintain optimal performance and prevent excessive data accumulation.

The ImportIntegrationEngineCredentials utility has been enhanced to improve user experience and functionality. Users can now execute this utility directly from the command line allowing for better scripting capabilities. Additionally the utility now supports specifying backup locations and uses more descriptive names for backup files helping to organize and differentiate files when setting up multiple environments. These updates streamline the process and provide clearer file management reducing the chance of confusion or errors.

We have streamlined the company configuration file by optimizing how properties are read and written resulting in a significant reduction of approximately 700 lines of code. This was achieved by refactoring repetitive code patterns and employing expression-bodied properties a feature available in C# 7 to enhance code efficiency. These improvements simplify the file's structure and improve overall system performance.

To enhance the efficiency of new system installations additional data will now be automatically included during the initial setup. This data will not be part of system updates ensuring that new installations benefit from a comprehensive set of initial values that aid in speeding up the implementation process and facilitate training sessions. The development team has integrated these initial values within the system's setup procedures ensuring that upon installation users will find pre-configured data in areas such as accounting purchasing inventory and more. This includes predefined terms payment types financial statement configurations and various maintenance options across different modules all designed to streamline the initial use of the system.

In response to reports of users being unexpectedly logged out while actively using the system the development team has implemented a solution to enhance system stability. The timeout setting for maintaining active connections has been increased to 90 seconds. This adjustment aims to reduce the frequency of disconnections ensuring a smoother user experience.

Users were experiencing frequent disconnections from the Deacom system a longstanding issue that has affected various versions over time. Previous workarounds such as clearing browser cache or adjusting user timeout settings were becoming less effective. To address this the development team implemented a solution by updating the system's keep-alive timeout to 90 seconds. This change aims to provide a more stable and reliable user experience reducing the need for temporary fixes and ensuring users remain connected without interruptions.

Users were experiencing unexpected logouts from the system due to an ASP.NET error which caused their sessions to terminate. The error was traced to a communication issue where the connection was being closed prematurely. To address this the development team increased the timeout setting for the system's keep-alive feature to 90 seconds. This adjustment helps maintain the connection longer reducing the likelihood of users being logged out unexpectedly.

A recent update to the Import Data tool introduced a new feature allowing users to upload data via Excel files. However there was an issue where the tool didn't reload the Excel file after changes were made causing potential errors in data import. To address this the tool has been enhanced to prompt users to re-select the Excel file whenever the LOAD button is clicked. This ensures that any modifications made to the Excel file are captured and the most recent version is used. The RUN button functionality remains unchanged continuing to operate with the data already loaded.

• A new API endpoint 'production/stabilityresultentry' has been developed to streamline the process of entering Stability Quality Control (QC) results into the system. This endpoint allows users to submit both standard and ad hoc QC test results ensuring they align with established QC procedures and security protocols. The API uses the Deacom User permission system to verify user authorization thus safeguarding the integrity of QC submissions. The endpoint is designed to accept only those submissions that are consistent with the configurations and permissions set within the Deacom application preventing any unauthorized overrides such as bypassing e-signature requirements. This enhancement facilitates efficient and secure QC result entries maintaining compliance with existing system configurations.
• An API endpoint has been introduced to streamline the entry of Quality Control (QC) results for Purchase Orders within the system. This new feature allows users to input QC data directly through the API mirroring the functionality available in the main application. The endpoint supports both standard QC tests and ad hoc tests ensuring flexibility in managing QC processes. Security measures are in place to ensure that only authorized users can submit QC data maintaining the integrity of the system's permission settings. Furthermore the API respects existing configurations such as e-signature requirements and prevents any unauthorized overrides. This development enhances the efficiency of QC data management by allowing seamless integration with external systems supplying test results.

The development team has successfully implemented a new feature in the Deacom Public API that allows for the automated creation of Purchase Orders (POs) to facilitate AI-driven invoicing processes. This enhancement provides an endpoint that can be utilized to generate a PO when an invoice does not match an existing order. The AI system can now automatically process expense-type invoices by creating POs and invoices within Deacom minimizing manual data entry. Users will have the opportunity to review and approve these AI-generated invoices before final posting. This initial implementation includes essential PO creation fields with the flexibility to expand field options as needed. The endpoint ensures that default vendor settings are applied when specific fields are not provided streamlining the process while maintaining accuracy. The new functionality is designed to integrate seamlessly with existing systems allowing for efficient invoice management and payment processing.

We have introduced new capabilities to the Deacom Public API allowing users to create and update CRM contact people. These enhancements enable seamless integration with CRM contact records enhancing data management and operational efficiency. The new API endpoints facilitate the creation and updating of contact people ensuring that any changes are accurately reflected within the CRM system. This development supports improved data handling and integration streamlining CRM operations for users.

We have improved the user experience for accessing our API documentation by introducing a new landing page. Previously users were directed to the Accounting controller page but now upon visiting the API documentation URL they will be greeted by the About page. This change provides a more general overview and includes definitions and frequently asked questions related to the API ensuring easier navigation and access to essential information.

We have enhanced the performance of our API by refining the way data is fetched for certain requests. Specifically for the accounting tax region search endpoint we have optimized the data retrieval process by using a single IQueryable approach. This change reduces unnecessary database calls and improves efficiency especially for requests that require detailed information.

In this update the Deacom.API and Deacom.Server projects have been revised to ensure they carry the correct version numbers. The changes include adding these projects to the versioning list which helps maintain consistent versioning across all files. The Deacom.Api project now links its version information files directly to the root directory ensuring that any updates to the root are automatically reflected in these projects. This integration ensures that when a new version of Deacom is installed the versioning of the files is accurate and consistent enhancing reliability and reducing the risk of mismatches.

The API Profile Settings feature has been significantly enhanced to improve user management of API configurations. Two new database tables have been introduced to handle settings and their values without overloading existing structures. A new grid has been added to the API Profile Add form allowing users to view and manage settings and values for selected APIs. This grid supports adding modifying and deleting settings with user-friendly options for custom settings. System settings are protected from deletion to ensure stability. Additionally a new form for managing API Profile Settings is available in the system maintenance section providing options to activate deactivate or delete non-system records with user prompts for potential impacts. These improvements facilitate efficient handling and customization of API settings.

We have introduced a new API endpoint for entering Quality Control (QC) results related to production. This enhancement allows users to input QC data for jobs covering pre-production post-production and ad hoc tests. The API ensures that user permissions are respected aligning with the security measures in the main application. It also enforces the same submission standards as the existing QC Result Entry form preventing unauthorized entries. This development facilitates seamless integration of external systems supplying test results while maintaining the integrity of QC configurations and requirements.

We've enhanced the Purchase Order Search endpoint to allow for more flexible date filtering. Now users can search for purchase orders using null values for both the start and end dates specifically targeting orders that have not been invoiced or have been received but remain uninvoiced. This improvement enables more comprehensive searches accommodating scenarios where dates are not specified thus enhancing the overall utility of the search functionality.

• We have integrated the Ally chat bot into Deacom enabling users to interact with an AI-powered assistant directly within the application. This new feature remembers past interactions and can renew tokens for continued sessions. Users will notice a new AI Chat icon on the top right of the Deacom main screen which opens a panel for engaging with the chat bot. This enhancement includes various UI updates such as a new menubar icon and a fly-out panel for the chat feature. Additionally we have added new methods to support AI chat functionalities allowing for seamless communication and information retrieval within Deacom.
• In the latest update the title of the AI chatbox within the Deacom system has been changed to AI Assist" to align with marketing and branding efforts. However due to legal concerns the decision was made to remove the title entirely. The tooltip for the AI chat icon has also been updated to display "AI Assist." These changes ensure consistency in how the AI feature is presented across the platform."

A new API endpoint 'production/stabilityresultentry' has been developed to streamline the process of entering Stability Quality Control (QC) results into the system. This endpoint allows users to submit both standard and ad hoc QC test results ensuring they align with established QC procedures and security protocols. The API uses the Deacom User permission system to verify user authorization thus safeguarding the integrity of QC submissions. The endpoint is designed to accept only those submissions that are consistent with the configurations and permissions set within the Deacom application preventing any unauthorized overrides such as bypassing e-signature requirements. This enhancement facilitates efficient and secure QC result entries maintaining compliance with existing system configurations.

We have introduced a new CRM project search feature within the Deacom API. This enhancement allows users to search for CRM projects using specific name fields without needing to fill every field. The update ensures that if certain required fields for specific filters are missing the system will return a clear 400 error message guiding users to provide necessary information. Additionally the endpoint now aligns enums with those used in the main application ensuring consistency in naming and status. These improvements make searching for project data more intuitive and efficient while also enhancing error handling to prevent system crashes when incorrect information is submitted.

The APICredentialService for APIProfiles has been enhanced with several new features and improvements. Notably it now supports Identity Insert allowing the addition of profiles with IDs less than zero which facilitates the inclusion of hidden profiles. Additionally URLs and settings have been converted for dictionary access enhancing the service's flexibility. Comparability and equality support have been introduced through IComparable and IEquatable implementations enabling more robust comparisons. Furthermore unit test coverage has been significantly improved ensuring better validation of all public methods and use cases. These updates are part of ongoing development efforts to refine and expand the capabilities of the APICredentialService without introducing a user interface for testing these new functionalities.

Our latest update ensures that API endpoints return the correct response classes enhancing clarity and consistency across the system. Specifically modifications were made to the Accounting and Inventory controllers to replace generic response formats with more specific ones. This adjustment improves the precision of data returned by endpoints such as the Search Chart Of Accounts and Search Facilities functions. Users can expect more accurate and relevant information when interacting with these API endpoints.

To enhance system integration capabilities a new service called APICredentialService has been introduced. This service is designed to facilitate interactions with APIProfile and associated data structures. Key developments include the addition of new business models and interfaces as well as the creation of unit tests to ensure functionality. While there is no immediate user interface impact this service will support future integrations requiring secure API credential management.

The API for issuing jobs has been enhanced to improve its functionality and usability. Previously specifying a job line was mandatory but this requirement has been removed to streamline the process as issues occur at the job level. The updated API now provides more flexibility by allowing optional inventory types such as quarantine and staging in addition to the default inventory. It also includes the ability to specify the quality control status of lots with options for passed failed and pending aligning with the main application features. These improvements enable more precise lot issuance by accommodating mixed inventory and quality control statuses. The code has been refactored for better efficiency and the logic has been adjusted to focus on materials rather than job lines enhancing the APIs capability to handle jobs with multiple lines effectively.

A new search endpoint has been introduced to streamline the process of finding freight types. This endpoint allows users to filter results based on the active status of freight types, with the default setting to show only active ones. While some fields were identified as unnecessary for this release and will be addressed later, the current update includes essential modifications to the purchasing controller and service, along with the creation of a new data access object. These changes enhance the ability to search by various criteria, such as ID, active status, and default settings for accounts receivable and payable. This endpoint supports the AI Invoice feature.

An error was occurring when users attempted to perform a search using the RevisionRouting API resulting in a 500 status code and an unexpected data processing error. This issue was caused by an incorrect handling of data types within the system. The development team has resolved the issue by adjusting the way data is processed specifically by ensuring that the system no longer attempts to improperly convert certain data types. Users should now be able to perform searches without encountering this error.

The versioning for the Deacom API controller has been updated to ensure that it correctly reflects changes made in the root directory. This adjustment allows for automatic updates streamlining the process whenever modifications occur. Users can now verify the accurate versioning by checking the properties of the Deacom.Api.Controllers.dll file confirming that it aligns with the intended version specifications.

To enhance functionality the facility search endpoint was successfully integrated into this prior version. This development ensures compatibility with AI Invoice features. The implementation involved adding new methods to the service layer controller and inventory data access components effectively enabling facility searches within inventory operations.

An API endpoint has been developed to allow users to search for Shifts similar to the existing prefilters and reports in the main Deacom application. The updated Search Job Labor endpoint in the Deacom API now aligns with the main app's form search ensuring accuracy and consistency in results. Improvements include the addition of null checks for specific fields such as Account OverTimeAccount and WorkCrew which help prevent errors when generating detailed responses. These changes enhance the endpoint's reliability by ensuring it returns complete and error-free data aligning with the standards set by EF Core.

The error handling process for API endpoints has been streamlined by implementing a centralized middleware solution. This eliminates the need for individual try-catch blocks in each endpoint method simplifying the code and enhancing maintainability. Additionally the CRUD controller functionality has been improved by automatically including a tag that skips model validation during CRUD operations ensuring smoother data handling.

Recent updates to the Deacom WebAPI have addressed several issues impacting the functionality of specific endpoints. The endpoint responsible for searching order history now correctly applies the 'Vendor' filter ensuring that search results accurately reflect the vendor specified by the user. Additionally the production job line requirements search endpoint has been fixed to prevent errors when no revision is associated with a chosen job line. Lastly an error that occurred while filtering on-hand inventory data by location has been resolved ensuring smooth execution without interruption. These improvements enhance the reliability and accuracy of the APIs production purchasing and inventory functionalities.

An update was made to the API's job requirements search endpoint to enhance its performance when filtering by date. Previously specifying start and end dates in search requests led to degraded performance due to excessive SQL queries. The endpoint now utilizes improved date filtering techniques significantly reducing the number of database queries executed. This update ensures that search requests with date parameters are processed efficiently improving response times. Additionally cached table models have been integrated to further streamline database interactions ensuring that searches return results promptly without unnecessary load on the system.

We have improved the AI Invoice Automation system to ensure that error messages from the Deacom API are accurately logged. Previously any error encountered during operations was replaced with a generic message about connectivity issues. With this update specific error messages from the API are now captured and recorded providing clearer insights into any issues that may arise. This enhancement allows for more precise troubleshooting by retaining relevant details about the errors such as those related to date discrepancies in invoices.

Previously users were unable to finalize staging for at-risk materials using the Warehouse Management System (WMS) although it was possible in the main application. This issue has been resolved allowing users to now complete the final staging process for at-risk lots in WMS. The solution involved adjusting the QA status filtering within WMS to include both approved and at-risk lots ensuring that all relevant materials are accessible for staging. This change harmonizes the functionality between the main application and WMS providing a consistent user experience across platforms.

In recent updates we addressed excessive memory usage in the Warehouse Management System (WMS) and web services on Deacom Cloud servers. The issue involved stuck print jobs and inefficient memory caching. To resolve this we removed the Microsoft Print to PDF printer from scanner options to prevent memory wastage. We also optimized the user session location cache in WMS to store only necessary data and ensured it clears upon logout. Additionally we modified certain processes to release memory more efficiently such as adjusting how grid cursors are managed. These changes help maintain performance without impacting essential functionalities.

In this update we've made it easier to create new count sheets directly from the scanner interface. Previously users were required to first create a count sheet in the .NET system before it could be accessed on a scanner. To streamline this process a new option has been added to the worksheet list allowing users to select <New...>" to open the Add Sheet form directly from the scanner. This enhancement ensures that users can efficiently manage physical inventory without needing to switch between systems improving workflow and reducing unnecessary steps."

A new logging feature has been added to the Warehouse Management System (WMS) to enhance debugging capabilities during development. This involves the introduction of a dedicated Logger class which facilitates the operation of the system in DEBUG mode. The Logger class is designed to interact with a Logger DLL file enabling reflective method calls that streamline debugging processes. This development aims to provide more effective troubleshooting tools for developers working with the WMS.

In the latest update an issue was fixed where cleared transactions in the Bank Reconciliation form were not disappearing from the list after being saved. Previously saving the form would automatically refresh the list and remove these cleared transactions. The solution involved adjusting the system to ensure that the form correctly recalculates and applies the necessary filters so that only the correct values are displayed. This adjustment guarantees that the cleared transactions are removed from the list upon saving regardless of user permissions. This fix builds upon a previous update to address all user scenarios.

The issue with account overrides not applying correctly on the Inventory Move form has been resolved. Previously when changing facilities the system did not update the source account as expected. Now when a new part number or facility is selected the system uses the updated facility settings to calculate the correct source and new account values. Specifically if a 'Purchase To' account exists for the item it will be used; otherwise the default source account will be applied. These changes ensure that the account values align correctly with the selected facility and item improving accuracy in inventory management.

Users encountered an issue in the bank reconciliation process where cleared items remained visible in the report even after saving disrupting workflow efficiency. The problem required users to close and reopen the tab to refresh the view. The development team resolved this by adjusting how the system recalculates values upon saving. Now when users save their changes the system correctly updates the display removing cleared items without needing to close and reopen the tab. This fix enhances user experience by ensuring a smoother and more efficient bank reconciliation process.

An issue was identified where receiving catchweight parts in purchase orders led to incorrect postings in the accounting system. Specifically the purchase variance was being posted to two different accounts due to a miscalculation in the system which resulted in inaccurate quantities being recorded. This problem stemmed from an unnecessary second multiplication in the weight calculation. The development team resolved the issue by removing this erroneous multiplication ensuring that the purchase variance is now correctly calculated and posted to the appropriate account. This fix prevents the occurrence of excessively large numbers in the General Ledger aligning the functionality with standard accounting practices.

An issue was identified where clicking on specific rows in a financial statement led to incorrect general ledger summaries being displayed. This problem was traced to a user interface glitch that occurred when users scrolled through the financial statement grid. The development team addressed this issue by aligning the drill-down functionality to ensure the correct accounts are displayed when selected. The resolution involved adjustments similar to those made in a previous related issue ensuring that the general ledger summary now accurately reflects the selected account regardless of scrolling actions.

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.

An issue was identified where the material burden did not appear in the General Ledger details after a purchase order was received. This issue has been resolved by implementing changes that ensure the material burden is updated when a vendor part is added. Specifically certain parameters need to be set before proceeding to ensure the material burden posts correctly even if the inventory costing method is not set to Standard Cost. This fix will be available in a future version aligning with the resolution of a related ticket. Users can expect the material burden to appear correctly in the financial records following the receipt of a purchase order.

An error was previously occurring when users selected the All" checkbox while performing a search on the Manual Checks page. This issue has been resolved by refining the data retrieval logic used in grid displays. Specifically the system now avoids applying temporary columns in the final report which prevents a Logged System Error (LSE) during filtering. This improvement ensures that only valid data is used when filtering thereby eliminating the error when moving orders between grids. This fix aligns with a similar issue resolved in a previous update focusing on filtering rather than grid refreshing."

An issue was identified where the system was not correctly converting the pricing unit from the item master to the vendor part number when posting Standard Freight costs. This resulted in incorrect freight charges being applied. The development team has resolved this by updating the calculation logic to ensure the conversion is handled properly. Now the system accurately calculates the freight cost based on the correct pricing units ensuring that charges reflect the actual weight and rate as expected.

We have resolved an issue where the cash account was not updating correctly on the Payment on Account and Regular Payments reports when a payment type with a defined cash account was selected. Now whenever you change the payment type the cash account will automatically update across all report types to match the one specified in the selected payment type. This change ensures consistency and accuracy in financial reporting aligning the cash account field with the designated payment type to prevent discrepancies.

In this update we've resolved an issue where sales representative splits on customer part cross-references were not posting correctly for the Cost of Goods Sold (COGS). Previously when sales reps were assigned splits at the customer part level the system incorrectly posted COGS resulting in discrepancies between the intended and actual postings. Now the system accurately reflects the sales rep percentages for both revenue and COGS. For a 50/50 split both revenue and COGS are correctly divided between the designated accounts. Similarly for a 0/100 split the entire COGS is allocated to the correct sales rep ensuring accurate financial reporting and sales rep incentives. This correction alleviates the manual burden previously placed on staff to identify and rectify posting errors.

An issue was reported that the record history banner for journal entries was missing key details such as the name date and time. This issue arose due to changes in the journal posting process which inadvertently prevented the creation of necessary log entries. The development team addressed this by modifying the system to ensure that log entries are created when journal entries are posted thereby restoring the missing information in the record history banner. This update ensures that users can view complete history details for journal entries maintaining transparency and traceability in accounting processes.

The issue causing incorrect General Ledger entries when mass updating lot costs for staging types has been resolved. Previously additional lines were mistakenly added causing compounded totals in the ledger. This was due to a problem in balance calculations where the list of gains was not cleared before processing each lot leading to repeated additions. The solution involved clearing this list before each calculation ensuring that the balances are accurate and preventing the issue of unexpected penny variances. As a result the General Ledger now correctly reflects the intended debits and credits without erroneous additional entries.

A formatting issue in the Deacom system has been resolved where a prompt was missing a space between words. Previously the message incorrectly displayed AccountsReceivable" as a single word. The system has been updated to correctly display "Accounts Receivable" or "Accounts Payable" depending on the context. This ensures the prompt text is clear and correctly formatted for users."

The issue where the document count indicator was not appearing on the invoicing screen has been resolved. Previously when users navigated to the Purchasing > Invoice page and added a purchase order the blue indicator that shows the number of attached documents was not displaying correctly. This issue has been addressed by moving certain variable settings and merging the document counting functionality to ensure the indicator accurately reflects the number of attachments. Now when users add an order to the invoice page the blue indicator should correctly show the number of attached documents enhancing the user experience by providing immediate visual feedback.

We have addressed an issue in the Bank Reconciliation tool that affected currency conversion. Previously when generating a report with a specified foreign currency any subsequent changes such as adding a cleared date to a transaction would cause the report to switch back to the default currency. This has been resolved by updating the system to retain the selected currency filter consistently even when the report is refreshed or modified. These improvements ensure that the currency setting remains stable providing accurate and reliable financial reporting.

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.

A technical issue was identified where prepaid inventory entries were incorrect when payments were made in a foreign currency specifically when dealing with back orders. The problem arose because different exchange rates were being applied to the remaining pre-payment causing discrepancies in the accounting records. To resolve this adjustments to purchase order invoices will now use the exchange rate at the time of receipt ensuring consistency and accuracy in the entries. This change ensures that all related financial transactions are recorded at a single consistent rate thereby preventing discrepancies in prepaid inventory accounts.

The issue with the drill-down feature on financial statements where it was incorrectly displaying accounts has been resolved. The underlying logic was adjusted to ensure that the sequence of records is maintained accurately even after filtering out zero-value records and grid columns. This update ensures that when users double-click on the Year-To-Date (YTD) actuals for specific accounts the correct account details are displayed. This fix enhances the reliability of financial statements by ensuring accurate account referencing.

An issue was identified where users encountered an error when attempting to run the Accrual Detail report for commissions and rebates. The problem was traced to a missing column in the data structure that the report relies on. To resolve this the system now checks for the presence of the required column before accessing its value preventing the error from occurring. This update ensures that users can generate the report without encountering any interruptions.

We have resolved an issue where using the 'Invoice All' button in the purchasing system did not correctly apply the vendor invoice date. Previously when invoicing multiple orders at once the system would default to the current date rather than the specified transaction date. This behavior has been corrected and the transaction date entered in the pre-filter will now be accurately reflected in both the system and vendor invoiced fields. Users can expect the vendor invoice date to match the date set during the invoicing process ensuring consistency across reports and system entries.

A problem was identified where emails sent with a PDF attachment via a trigger did not include the attachment. This issue occurred when attempting to send a remittance report PDF at the time of payment. The problem was traced to a failure in applying currency filters which caused the attachment process to silently fail. To resolve this a new method was introduced to correctly apply currency filters ensuring the PDF is attached successfully. Additionally logging was enhanced to provide better diagnostic information. After implementing these changes the system now successfully sends emails with the intended PDF attachment included.

When voiding a payment made in a foreign currency an issue was identified where gain/loss entries were incorrectly recorded causing an imbalance in the accounting records. This occurred because values were being posted to both the local and foreign currency credit fields. The solution involved adjusting the system to ensure that when an exchange rate adjustment line matches the last entry the foreign currency credit field is set to zero. This change ensures that only the local currency credit field is populated maintaining balanced journal entries.

The issue was identified in the Sales Order Detail report where the calculated field 'acttot' was not reflecting accurate values due to a discrepancy in currency conversion compared to the Profit Detail report. The development team resolved the problem by ensuring that the currency conversion applied to the Profit Detail report matches that of the Sales Order Detail report. This adjustment ensures consistency in the calculation of the 'acttot' field across both reports providing accurate financial data for users.

A recent update addresses the issue where users could undo inventory adjustments in closed accounting periods inadvertently altering past financial data. The solution involves adding a verification step that checks the posting date against the period's status ensuring adjustments cannot be made to periods that have been officially closed. This change prevents unauthorized modifications to historical records maintaining the integrity of financial reporting. Users attempting to undo adjustments in closed periods will now receive a notification indicating the period is locked thus preserving the accuracy of past accounting data.

The Payables Detail report has been updated to ensure that all necessary variables are correctly displayed. Previously users experienced issues where certain variables such as invoice date and vendor were not available resulting in Invalid Expression" errors in version 17.03. This problem has been resolved by retrieving data through a specific method that includes all required fields ensuring that variables like actinv antcash invdate invvend inventered and topay are now accessible and correctly printed in the report."

We have addressed an issue where the General Ledger (GL) Override account on a Sales Order was being incorrectly altered after the order was shipped. The system now correctly maintains the specified GL Override account throughout the shipping process. This fix ensures that the designated GL account remains consistent and accurate when viewing order details post-shipment.

A generic error was occurring when users attempted to view invoices on the Check Run and Manual Checks screens due to a missing API type. This issue has been resolved by implementing a safeguard to handle cases where the Commerce Suite" API Type is not present. The system now checks for null values preventing errors from arising when the specified API Type is absent. As a result users can now access the Manual Checks and Check Run forms without encountering errors regardless of the API configuration in their environment."

In the CRM Ticket Reporting system users encountered a technical issue where selecting any value from the Ticket Search filters caused an error disrupting the reporting process. This problem has been addressed by updating the logic used to match search terms with headers ensuring compatibility with previous system versions. The development team modified the search functionality to prevent errors when users select search criteria allowing the reports to run smoothly without interruption.

A system error was occurring when users attempted to add a category in CRM ticket reporting due to missing search number values in certain search boxes. This issue has been resolved by manually updating the relevant files to include the necessary values ensuring that the error no longer appears when interacting with the category field.

An issue was identified in the CRM Ticket Reporting feature where attempting to open a ticket after viewing its summary would result in an error. This occurred specifically in certain software versions and was reproducible with specific ticket numbers. The error was traced to a problem with how picklists were being handled during the ticket opening process. To resolve this the development team updated the system to ensure that items are checked for duplication in picklists before being added. This change prevents the error from occurring allowing tickets to be opened without issue after viewing their summaries.

After a recent update to the eCommerce backend users encountered issues starting the console and service due to a license error. This problem was initially reported by a customer and then replicated internally. The error messages indicated that a valid eCommerce license could not be found preventing the console and service from starting. To resolve this the development team identified and corrected a version mismatch that was causing the license errors. Some DLL updates were reverted and additional logging was implemented to better capture any future failures when checking for eCommerce licenses. These changes ensure that the console can now launch successfully without errors.

• We have addressed an issue where user-defined fields (UDFs) were being saved as blank entries in the database by default. This primarily affected sales orders processed through Electronic Data Interchange (EDI) where many user fields were not mapped correctly. The system has been updated to prevent empty UDFs from being stored ensuring only meaningful data is retained. This change eliminates unnecessary data clutter and enhances the efficiency of data management within the system.
• We have resolved an issue where the EDI system was incorrectly generating duplicate User Defined Field (UDF) records for each customer order. Previously UDF data from different orders was being mixed due to shared lists at the method level. To address this we introduced separate UDF list properties for 'Ship To' and 'Bill To' within each order object. This ensures that each order maintains its own distinct set of UDF records preventing data from different orders from being combined. This fix ensures that only one UDF record is created per customer order eliminating the previous duplication issue.

The issue where the 'fi_catchwgt' field was not updating during EDI imports has been resolved. The development team implemented changes to ensure that this field is correctly imported when receiving purchase orders through the EDI system. This enhancement allows the 'fi_catchwgt' values as specified in the EDI profile to be accurately reflected in the order details. The update required adjustments to the import function ensuring that weight information is properly processed and included in the purchase order records.

We have resolved an issue where the EDI system was incorrectly generating duplicate User Defined Field (UDF) records for each customer order. Previously UDF data from different orders was being mixed due to shared lists at the method level. To address this we introduced separate UDF list properties for 'Ship To' and 'Bill To' within each order object. This ensures that each order maintains its own distinct set of UDF records preventing data from different orders from being combined. This fix ensures that only one UDF record is created per customer order eliminating the previous duplication issue.

An issue was identified with the import of EDI 850 files where the system failed to recognize a valid date format causing import errors. This was specifically linked to promotions applied to the orders which did not affect manual order creation. To resolve this the development team implemented a change using a more robust date parsing method ensuring that empty date fields do not cause import failures. This fix allows the EDI files to be processed successfully even when promotions are involved without manual intervention.

The system experienced a crash when users attempted to view a Bill of Materials (BOM) with specific filter criteria in the inventory module. This occurred when a filter was applied to display all columns including those with empty values. To resolve this issue the development team optimized the filtering process by excluding columns that contain only empty values. This enhancement improves system performance and prevents crashes ensuring a smoother and more reliable user experience when viewing BOMs with comprehensive filters.

We have addressed an issue in the Bill of Materials (BOM) Lines report where part numbers were being duplicated when using the 'Compare To' functionality. The report has been updated to ensure that any duplicate lines are now consolidated with their quantities combined for clarity. Additionally if the base part does not have a BOM line that is present in a secondary part the base part's quantity will be displayed as zero. This update ensures a more accurate and streamlined reporting process.

An issue was resolved where the Issue/Reserve form would unexpectedly close when users changed the type from 'Sale' to 'Staging/Sales' in the Daily Sales Calendar. This problem occurred when the form was accessed through the calendar interface. The development team has implemented changes to ensure the form remains open improving the user experience and functionality in the sales calendar module.

The issue with the Physical Inventory Worksheet timing out during creation has been resolved. Previously the worksheet took too long to load which resulted in a timeout error. The resolution involved optimizing the query to significantly improve performance reducing the load time from 16 minutes to under 1 minute. Additionally the timeout settings for the print process were adjusted to accommodate a higher page processing rate ensuring smoother operation. These changes enhance the speed and efficiency of generating physical inventory worksheets providing a better user experience.

The functionality for lead times on facility relationships has been improved to ensure that the appropriate lead times are applied when creating inter-company transfers. Previously the system did not correctly retrieve lead times resulting in incorrect ship and dock dates on orders. The recent update addresses this issue by modifying the underlying queries to accurately calculate the due ship date and due dock date based on the configured lead times and safety days. Users can now expect that the lead times set on facility relationships will take precedence and be reflected correctly in order entries.

An issue was identified where notes added during inventory adjustments were not appearing in the Inventory Adjustment report. This problem has been resolved by ensuring that the notes field correctly displays the information entered during the adjustment process. Development changes were made to prevent the overwriting of the notes data allowing users to see their input in the report as expected.

After upgrading to a new software version users experienced difficulties with printing specific BOM reports as the system failed to recognize them. This issue affected only the BOM reports while other types of reports printed without any problems. The problem was traced to job print substitutions lacking the necessary BOM report layouts in their assigned groups. To resolve this the development team ensured that job print substitutions now include the relevant BOM report layouts allowing these reports to print correctly across all output formats. This fix will be implemented in both earlier and upcoming software versions ensuring consistent functionality.

The issue with the 'Lots Received' report not properly filtering items has been resolved. Previously when a specific item number was selected the report would incorrectly display additional items from the same purchase order. This was particularly problematic for raw materials as the report would include all items sharing the same lot. The development team has updated the system to ensure that the filter now correctly restricts the report to only the specified item in this case item I1107. This fix ensures accurate reporting by applying the correct filters so users can expect to see only the intended items in their reports.

We addressed an issue where incorrect lots were being staged from quarantine during the inventory management process. The resolution involved implementing a series of development changes to enhance system functionality and user experience. Key improvements include a redesigned user interface for better accessibility performance optimizations to reduce load times and enhanced security measures to protect user data. Additionally we resolved legacy bugs to ensure stable operation and introduced new features such as improved search capabilities and personalized settings. These updates aim to provide a seamless and reliable platform for users.

Users previously faced an issue in the item inquiry feature where the 'Next' button was disabled preventing forward navigation through the grid results. The 'Previous' button however functioned correctly allowing backward navigation. This issue has been resolved by ensuring that both 'Next' and 'Previous' buttons are enabled when there are multiple items to navigate within the grid. Users can now seamlessly browse through item records using both navigation buttons enhancing the usability of the item inquiry process.

A recent update has addressed an issue where all inventory was incorrectly staged to a single order leading to errors in product selection for sales orders. The system now ensures that inventory lot groups are properly distinguished according to their respective sales orders or jobs during pre-staging or staging-specific operations. This enhancement improves the accuracy of historical reporting by maintaining correct references to the original sales orders or jobs. With these changes each inventory lot now accurately reflects its associated sales order or job ensuring more reliable reporting and inventory management.

An issue where the unit weight value was being cleared from the Item Master when changes were made to the Bill of Materials (BOM) has been resolved. Previously modifying a BOM and changing its active status would inadvertently reset the unit weight to zero. This problem was addressed by applying a fix from a related ticket ensuring that inactivating a BOM no longer affects the unit weight value in the Item Master. Users can now modify BOMs without losing the unit weight information maintaining data consistency across the system.

An issue was identified where changes to inventory counts made through the 'View Counts' option were not immediately reflected on the Edit Worksheet Page. Previously users had to close and reopen the page to see updates. This has been resolved by implementing a refresh function that automatically updates the grid with the latest count changes. Now users can simply click the Refresh button on the Edit Worksheet page to see their modifications without needing to navigate away from the page.

We have resolved an issue where the indented Bill of Materials (BOM) view was not functioning correctly for a specific part number. The problem arose due to a calculation error that was treating all BOM lines as if they were subject to a degradation calculation causing a divide by zero error when the calculation factor was set to 100. Our development team has refined the calculation logic to ensure it correctly applies the appropriate method based on the BOM calculation type. This fix ensures that the indented BOM view updates as expected without errors.

We have resolved an issue where the Physical Inventory Count Sheet was not automatically including lot expiration dates. This problem required users to manually input expiration dates which are essential for inventory items with expiration requirements. With the update the system now automatically retrieves and displays the expiration date when a lot is selected or scanned both in the main application and the Warehouse Management System (WMS). This enhancement ensures accurate tracking and validation of inventory items thereby improving the reliability of inventory management processes.

Previously predefined notes categorized under 'Inventory' were not appearing in the 'Notes' field on the Adjust Inventory Move Inventory and Produce Assembly screens. This issue has been addressed by updating the form layouts for these screens to ensure that notes with the 'Inventory' category are displayed correctly. Now when entering notes in these fields users will see all relevant predefined notes including those categorized as 'Inventory' and 'All.' This enhancement ensures better visibility and accessibility of predefined notes across these inventory management functions.

In this update we have addressed an issue where inventory was incorrectly reserved and zeroed out when a shipped sales order was linked to a purchase order even if the received part was not part of the sales order. Now users will no longer be able to link a purchase order to a shipped sales order. Additionally when receiving a purchase order linked to a sales order only the lots of parts that are present on the sales order will be reserved while others will be received as normal. We have enhanced the search functionality for sales orders on the purchase order header to only include unshipped sales orders and added a validation to ensure that linked sales orders contain the relevant parts.

The issue with the Inventory Usage Detail report displaying move transactions incorrectly was resolved by refining the filtering logic. Previously the system only recognized actions labeled precisely as Inventory move" which caused transactions with slight wording variations to be incorrectly included in the report. The development team updated the filter to accommodate these variations such as additional characters or dashes ensuring that only relevant transactions are displayed. This adjustment allows the report to accurately reflect inventory usage without including unintended move transactions."

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.

Previously certain user fields were not displaying correctly within the Bills of Material (BOM) update module when using the Implosion/Single Level BOM view. This issue has been resolved by integrating these fields into the main query and ensuring they are consistently included in the grid layout. As a result users will now see the relevant user fields automatically populate when accessing the Implosion/Single Level BOM providing a seamless experience without the need for additional adjustments.

An issue was identified where users encountered an error when trying to create a Favorite" in the Inventory Reporting section. This problem was traced back to a complex piece of code that sometimes failed to find necessary sequences leading to an error. To resolve this the development team simplified the code by replacing the complex logic with a more straightforward approach ensuring that sequences are properly identified before attempting to use them. This change not only improved the code's readability but also eliminated the error allowing users to create favorites without issues."

An issue was identified where the Issue/Reserve screen would close unexpectedly when users attempted to change the 'Type' field from 'Job' to 'Staging/Job' directly from the Job Entry screen. This problem has been resolved by adjusting the logic that handles the search box elements. The system now correctly identifies whether a search box is part of a dialog before attempting any operations on it. This prevents the parent form from closing unexpectedly when it's a modal. Users can now change the 'Type' without the screen closing ensuring a smoother workflow.

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. This ensures that all deal details are accurate and up-to-date.

An issue was identified where the inventory quantities issued in multiple production reports were not being calculated correctly. This discrepancy was evident when using the 'View Reqd' feature which showed incorrect issued quantities for certain jobs despite materials being issued. To resolve this the query responsible for calculating issued and relieved inventory quantities was updated. This ensures that both the 'View Reqd' report and the inventory reporting accurately reflect the correct quantities providing consistent and reliable data for users.

An error occurred when attempting to add a specific part number to a Bill of Materials resulting in a system error. The problem was traced to a divide by zero error during the conversion of units in the BOM process. This happened when the count of items on the parent row was zero causing the calculation to fail. The development team resolved the issue by updating the system to return zero for the conversion when the count is zero preventing the error from occurring.

We resolved an issue where users encountered errors when receiving inventory transfers due to mismatched currency settings between accounts and facilities. Previously accounts required a matching currency with the facility to process transactions which led to errors if the account had no specified currency. The update now allows accounts without a specified currency to be used in any facility regardless of the facility's currency. This change provides more flexibility in handling transactions across different currencies ensuring smoother inventory transfer processes.

In version 17.03.009.0007 the Usage Detail report was incorrectly including additional transaction types leading to discrepancies in the totals. Specifically the report was showing both Issued and Reserved Inventory as outgoing transactions along with Shipped Orders which caused an overstatement in the out totals. The report has been updated to exclude these Issued and Reserved actions focusing instead on accurately representing usage through the Relieve Job action. This adjustment ensures that the report reflects true inventory movements aligning the in and out totals correctly.

We have addressed an issue where users encountered an 'Insufficient Inventory' prompt when issuing lots with a non-zero density value even though there was sufficient inventory available. This was due to density being incorrectly factored into inventory calculations. To resolve this we have removed the density check from the inventory issuance process for this specific customer as their use of density is unique and does not affect other customers. This change ensures that inventory can be issued without errors regardless of the density value.

We addressed an issue where users encountered 'Insufficient Inventory' errors when attempting to post changes on inventory worksheets. The problem stemmed from the system incorrectly handling inventory quantities with decimal values. Specifically the system was treating these quantities as whole numbers which led to errors. This has been corrected by ensuring that the system now accurately processes decimal values for inventory quantities. As a result users should no longer experience errors related to insufficient inventory when posting updates to the physical inventory.

The issue where modifying the lot expiration date did not update the job inventory screen has been resolved. Previously changes made to the expiration date of inventory lots were not reflected in the job inventory screen causing discrepancies. The system has been updated to use a different field for inventory status updates ensuring that any modifications to lot expiration dates are accurately displayed in the job inventory section. This change ensures that the inventory reflects the current state of the lot providing more reliable and consistent information.

We have resolved an issue where the system was unable to process returns for serialized catch weight items due to an error regarding existing serial numbers. The development team has implemented changes to allow these items to be shipped on a return order. Specifically two new validations were introduced: one ensures that the shipment quantity is appropriate for a return and another filters out items with missing serial numbers. These adjustments enable the correct processing of serialized catch weight returns ensuring that returned lots retain their lifecycle tracking information for potential resale.

An issue was identified in the Deacom mobile app for Android tablets where changes to the selected printer in the app's settings were not being saved. This was due to a server-side problem where the form ID was not being validated correctly during the settings retrieval process. The development team has corrected the server-side logic to ensure proper validation of the form ID. This fix resolves the error message issue and ensures that printer selections are saved correctly. Users should now be able to change their printer settings without encountering repeated prompts to discard changes.

An issue was identified where users encountered an error when checking inventory availability in the Instant-MRP feature for specific items. The error occurred when the system attempted to retrieve part details from a single-row grid resulting in an invalid parameter error. Developers have resolved this by ensuring the system correctly retrieves the part ID from the selected row when only one item is displayed. This fix allows users to successfully access inventory availability without encountering errors.

A typographical error in the Deacom MRP pre-filter options has been corrected. Previously the option was incorrectly displayed as Exclude During Lead TIme" with an incorrect capitalization in the word 'Time'. This has now been fixed to correctly read "Exclude During Lead Time". The update involved adjustments to the form and database entries to ensure consistency across the system."

We have addressed an issue in the Material Requirements Planning (MRP) system where it failed to provide suggestions when forecast demand was set to cause the on-hand quantity to become negative. The problem occurred when both the Facility and Facility Group filters were left empty. With the latest update the system now accurately calculates and provides necessary suggestions to prevent negative inventory levels ensuring smoother inventory management and planning.

The application was experiencing a crash when users attempted to create a job from the Material Requirements Planning (MRP) module for certain items. This issue manifested as the application becoming unresponsive necessitating users to terminate their sessions to regain control. The problem did not occur when jobs were created manually for the same items. The underlying issue was identified as an infinite loop causing the application to hang. Development has resolved this by ensuring that the spinner does not continue indefinitely allowing users to create jobs from MRP without encountering application crashes.

Previously when creating an intercompany transfer (ICT) via the Job MRP feature only one item was included in the order even if multiple items were selected. This issue has been resolved. Now the system correctly generates an order that includes all selected items. The development team identified and rectified the filtering logic that caused only the highlighted row to be processed reverting a specific change to ensure that all selected items are included in the ICT. This update has been implemented in the latest software branch ensuring that the functionality now works as intended.

The issue with the Material Requirements Planning (MRP) system not providing suggestions when inventory levels are negative has been resolved. Previously when the 'Exclude During Lead Time' option was selected MRP failed to generate supply suggestions for future demand resulting in negative inventory levels. The solution involves adjusting the logic to account for the lead time of items ensuring that suggestions are generated in advance to prevent negative inventory. Now when the lead time pushes requirements to a previous month MRP will provide additional suggestions to cover the demand adequately using the item's lead time and bucket type settings as references. This ensures that inventory levels remain positive even when demand is forecasted months ahead.

A recent update addresses an issue where multiple job lines were created for the same item when generating jobs from Material Requirements Planning (MRP). Previously if there was overdue demand combined with future demand the system would create separate job lines for the same item instead of consolidating them into a single line. This update includes a change that now consolidates job lines with the same part number facility and due date into one ensuring more efficient job creation and clearer scheduling. The solution also incorporates a consideration for lead times further enhancing the accuracy of job scheduling.

A problem was identified where the Material Requirements Planning (MRP) system was creating jobs with incorrect quantities for certain parts. The issue was traced back to a part miscalculation and a condition that prevented proper distribution of materials across sub-assemblies. This led to a significant discrepancy in the planned quantities for certain parts. The development team resolved the issue by adjusting the code to ensure that the quantities are accurately calculated and distributed across all jobs. Now when creating a job the quantities for parts will align correctly reflecting the intended Bill of Material ratios.

We have addressed an issue where the Material Requirements Planning (MRP) availability screen incorrectly displayed inventory transfer quantities (ICTs) at the origin facility instead of the destination facility. Previously the availability screen showed ICT quantities as available in the facility from which they were shipped causing confusion. This has been corrected to align with MRP functionality ensuring that ICT quantities now appear in the destination facility's column on the Basic Item Availability grid after being shipped. This update ensures consistency and clarity in inventory reporting reflecting the actual status of inventory in transit.

An issue was identified where the system ignored incremental purchase order quantities when creating purchase orders (POs) through the Material Requirements Planning (MRP) module. This problem particularly affected items purchased in different units than they are sold or stocked. The system should have adjusted the PO quantity to match the incremental value specified but it failed to do so resulting in incorrect quantities. To resolve this enhancements were made to prevent system hang-ups caused by clicking on 'Manual PO' without a suggested quantity. Additionally the system was updated to ensure that PO quantities automatically adjust to reflect the specified incremental values thereby preventing discrepancies in order quantities.

In the latest update the system has been refined to ensure that when users apply a facility filter in the Instant or Time-Phased MRP reports only forecasts with the specified facility will be displayed. Previously forecasts without a facility assignment were incorrectly appearing in the MRP results despite the application of a facility filter. The development team addressed this by implementing logic that accurately filters forecasts based on the selected facility ensuring that only relevant data is presented in the MRP grid. This enhancement guarantees that users see precise and facility-specific forecasts improving the accuracy and relevance of the MRP data.

We have resolved an issue where documents were not printing in the correct order as configured in the Document Group settings. Previously when printing from the Sales Order Reporting module the system did not adhere to the specified sequence causing Document Category documents to print before Sales Reports. The development team has updated the system to ensure that documents are now printed in the precise order defined within the Document Group. This adjustment ensures that Sales Reports such as the Sales Picklist and Packing List are printed first as intended. Users can now expect their documents to be printed in the correct sequence when using a physical printer.

A system error was occurring when users attempted to print a specific document group within the production job reporting section. This issue has been resolved ensuring that printing now functions correctly without triggering an error. The fix has been implemented in both the main software release and a targeted update providing stability and preventing the error from reoccurring. Users can now print the 'Document Group - Production Papers' to the screen without encountering any issues.

An issue was identified where printing from the sales order screen while the cash register was open led to duplicate sales order entries. This occurred when printing a receipt after modifying a sales order and entering a cash payment. To resolve this a check was added to ensure that a record lock is in place before printing. If an attempt is made to print while a lock is overridden users will now receive a message box notification. This update prevents the creation of duplicate records ensuring smoother operation and accurate sales order management.

We have addressed an issue where printing sales order labels would sometimes display incorrect master lot information. This problem occurred when a lot was assigned to two different master lots causing the system to pull the wrong data. The resolution involved updating the logic used to filter label data ensuring it now includes the master lot number as a criterion. This change ensures that the correct master lot information is retrieved even when a lot is associated with multiple master lots providing accurate labels for sales orders.

Users experienced an issue where master lot labels could not be printed from scanners in the system specifically when using the Issue Job and Issue Master Lot screens. Although the system indicated a label would be printed no label was actually produced. This problem did not occur when printing from the Find Inventory screen. The issue was resolved by updating the printing logic to accommodate multiple master lot labels. Previously the system incorrectly restricted the print function to a single label record. Now all applicable label records are processed with those having a label quantity of zero being excluded from printing. This ensures that all necessary labels are printed as expected.

An issue was identified where emailing invoices to document groups resulted in only one email being sent despite multiple orders being queued for invoicing. The resolution involved refining the 'Print All' functionality to ensure that only one document is processed and marked as printed at a time. This prevents multiple documents from being erroneously marked as printed and removed from the grid. The development team adjusted the system to align with the intended behavior ensuring that only the document actually sent via email is marked as printed while the others remain in the queue.

Following a recent update an issue was identified where lot labels were not printing correctly specifically affecting the visibility of part numbers on the labels. When receiving a part in multiple lots only the first lot label displayed the part number and subsequent labels lacked this information both in human-readable form and as a barcode. To resolve this the development team reverted changes made in previous updates and adjusted the method for identifying print rows. By switching from using a method intended for aligning forms to lots to one that accurately identifies print rows the issue was successfully corrected. This ensures that all lot labels now consistently display the part number both visibly and in barcode format.

A security issue was identified where users could modify documents in the Document Management system even without the necessary permissions. This occurred when users accessed the Tools - Document Reporting feature. The issue has been resolved by implementing a security check that ensures the modify button and the double-click action on documents are disabled for users lacking the appropriate permissions. Now only users with the correct security settings can modify documents maintaining the intended access restrictions.

A technical issue was identified where users encountered a system prompt when attempting to print reports that included user fields marked with the 'Part Forms Only' property. This prompt prevented the successful printing of reports. To resolve this development adjustments were made to ensure that user fields with the 'Part Forms Only' designation are correctly included in job report printouts. This change allows these fields to be displayed properly in printed reports resolving the printing issue and aligning with the original intent of the 'Part Forms Only' functionality.

We have resolved an issue that prevented master lot labels from printing correctly during certain stages of sales order processing. The problem stemmed from the system incorrectly handling data types specifically when the 'or_quant' field was mistakenly treated as a string instead of a decimal. This error occurred when processing sales orders with multiple master lots. Our development team updated the system logic to ensure that data types are assigned correctly based on the field type thereby preventing the error message and ensuring successful label printing across all stages of order processing.

Some users experienced issues with printing where attempts to print would result in a loading circle and the inability to proceed affecting multiple facilities. The problem was traced to the server's default printer setting often set to 'Microsoft Print to PDF' which prompted a server-side file dialog that users could not interact with causing the printing to stall. To resolve this additional checks were implemented in the server's printing code to ensure that the printer selected on the Paid3 form is always used thereby avoiding the file dialog issue. As a temporary workaround users are advised to manually select their desired printer on the Paid3 form at least once per session to prevent defaulting to the PDF printer. This adjustment must be repeated after each login or session restart.

An issue was identified where labels printed during the staging process incorrectly displayed the original lot quantity instead of the actual quantity staged to a job. This occurred when parts were staged one at a time and a new label was printed for each part. The problem was resolved by updating the logic that sets the issued quantity on labels. Now when the 'Commit on Scan' option is unchecked the system correctly assigns the actual staged quantity to the label ensuring accurate representation of the quantity committed to the job. This adjustment allows the label to reflect the correct issued quantity regardless of whether the quantity is scanned or manually entered.

An issue with printing the QC History Report was identified where users encountered errors due to invalid column names in the SQL command. This prevented the report from generating correctly. The development team resolved the issue by removing obsolete fields from the main query allowing the report to be generated without any prompts or errors. Users can now print the QC History Report successfully by selecting the job number and following the standard print procedure.

An issue was identified where the system prompt window would appear behind the print window during the production of assemblies making the print window unresponsive. This problem typically occurred immediately after logging into the system. To resolve this changes were made to the frontend logic to ensure that any hidden prompts are brought to the forefront when attempting to close the print window. This improvement allows users to address the prompt before closing the modal ensuring smoother interaction with the system.

We have addressed an issue where attempting to change the quantity for printing Sales Order (SO) Labels led to a blank line appearing and an error being thrown when the print button was clicked. The system now correctly updates the sequence numbers when labels are added preventing the creation of dummy rows that caused these errors. Users can now modify label quantities and print without encountering these issues ensuring a smoother and more reliable printing process for SO Labels.

An issue was identified where the quantity of labels printed for purchase orders did not align with the user-defined expressions. This was due to unnecessary logic for printing by lot and a problem where the same quantity was applied across all parts. The development team has resolved this by removing the redundant printing logic and ensuring that the system accurately updates the quantity for each part individually. Now when printing purchase order labels the system correctly uses the user expression to determine the quantity even when dealing with multiple lots or lines within a single order.

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.

An error occurred when attempting to print a specific group of documents within the sales order reporting feature. This was due to the system trying to access a column that sometimes did not exist leading to the error message. The development team resolved the issue by adding a validation step to check for the presence of the column before using it ensuring that the printing process can proceed without errors while retaining all existing functionalities.

An issue was identified where the default copy numbers in reports were not aligning correctly with the actual number of copies present. For example adding a new caption to a report might incorrectly show an increased copy number even though fewer copies existed. The development team has resolved this by implementing logic that only increments the copy number when a new printing default is created ensuring that the copy numbers now reflect the correct sequence. This change prevents the disruption of order when modifying existing lines maintaining accuracy in report layouts.

The issue where the default print quantity on CPCR part forms was being ignored has been resolved. Now when printing labels for customer parts the system correctly uses the default quantity specified for each part. This improvement ensures that the specified number of copies is accurately reflected during the print process enhancing the reliability of label printing for customer orders.

A technical issue was identified where the Deacom web service would crash when users attempted to print to a cloud local printer after initially printing to the screen. To resolve this a necessary component called 'pdfium.dll' was integrated into the web service. This addition ensures that documents can be printed correctly without causing the service to fail. The update addresses the printer-related error and enhances the stability of the document printing process within the application.

In previous software versions users were able to print ticket reports directly from the Modify screen but this functionality was not available in the current version. The issue was resolved by updating the software to correctly recognize the print command in the Modify screen. Specifically a change was made to ensure the print button in the toolbar functions as intended allowing users to print without needing to exit to the View screen. This update restores the expected print dialogue box functionality and enhances user experience by simplifying the printing process during ticket modification.

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. This adjustment ensures that all intended labels are produced during the receipt process resolving the confusion previously encountered.

In this update we've addressed an issue where certain printouts were incorrectly listed as available in the Deacom system despite the user not having the necessary licenses. Users were seeing options for reports such as POS Receipt Sales Configurators 1-7 and Sales Engineering which they could not access. To resolve this we implemented a new method to verify license types and filter out printouts that are not licensed for the user. This ensures that only the reports relevant and accessible to the user are displayed.

Users were experiencing significant delays when printing job labels especially for jobs with numerous finishes or system lots. This issue has been resolved by optimizing how quality control (QC) data is handled during the printing process. The development team improved the performance by grouping QC data on the server which significantly reduced the amount of data being processed. This change decreased the printing time from 24 minutes to just 25 seconds. Additionally the method of removing rows from the cursor was enhanced to clear the table more efficiently contributing to faster label printing.

The issue where documents were not printed during the pre-staging of inventory has been resolved. The development team adjusted the system to ensure that printouts are generated when inventory is marked as reserved. This fix specifically targets the location type during the printing process bringing the functionality in line with its intended purpose. Users can now expect to receive pre-staging and final staging pick lists as part of the inventory management process enhancing the workflow and ensuring that necessary documentation is available.

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.

A technical issue was identified where attempting to print documents for orders with multiple discounts of the same part number resulted in an error message about duplicate keys. This problem occurred because the system used both part ID and lot ID as keys leading to conflicts when discounts shared identical information. To resolve this the system's code was updated to manage duplicate keys by grouping entries and selecting the first occurrence ensuring smooth document printing even when multiple discount lines are present. This change eliminates the error message and allows users to print document groups without issues.

Users experienced an issue where attempting to modify the print quantity for job labels resulted in an error due to an unintended extra line being added to the print forms grid. This caused a missing part number error when printing. The issue has been resolved by applying a fix originally developed for a later software version to earlier versions. Users can now update print quantities without encountering errors as the system correctly updates the selected line without adding unnecessary entries.

In previous versions users encountered an issue where the layout button was unavailable when attempting to edit the Bill of Materials (BOM) form layout. This was due to the button's visibility and enablement properties being inaccessible. The problem was resolved by updating the form configuration which now allows the layout button to be visible and functional.

We have resolved an issue where changing the status of a job inadvertently removed assigned users from workflow steps. This occurred due to a process that did not consider the assigned user during data recovery. The fix involved adjusting the data recovery process to ensure that the assigned user remains intact when a job status changes. This update ensures that workflow assignments are preserved maintaining consistency in job status management.

A problem was identified in the Job Material Cost Detail Report where ingredients were incorrectly duplicating when a job contained multiple item numbers. This issue arose after changes in the system disrupted the previously correct display of consumed quantities which should appear as a single line per ingredient. To resolve this the development team decided to revert the recent changes that caused the duplication. This reversion restores the report's functionality to correctly display the total consumed quantity for each ingredient on a single line as it did in earlier versions. The fix ensures that multi-item jobs are now properly supported eliminating the duplicate lines and correctly calculating costs at the job level.

A critical issue was identified when attempting to create or edit jobs in the system resulting in an error. This was traced back to changes made in a previous update which inadvertently caused the problem. To resolve this the development team reverted some of the recent modifications to restore the system's original functionality. Users can now successfully add or modify job entries without encountering errors. Additionally it's important to note that while the system allows for the addition of a job lot user field it does not enforce uniqueness unless specifically configured to do so.

The Job Material Cost Detail report was previously showing incorrect quantities due to inventory movements between facilities after items were issued. This resulted in inaccurate data being displayed for specific job numbers. The development team has addressed this issue by ensuring that the system now accurately reflects the correct quantities. Users can now view the report and see the correct actual quantity for items ensuring that the net quantity aligns with the expected values.

An issue was addressed where modifying a Sales Order linked to a Job caused the Sub-Assembly line to disappear from the Job. This was due to sub-assemblies not being properly recognized during updates and duplicate entries being removed incorrectly. The development team resolved this by updating the data transformation process to ensure sub-assemblies are correctly included and modifying logic to prevent duplicate removal of valid sub-assembly lines. As a result sub-assemblies now remain intact when a Sales Order is updated ensuring accurate job line retention.

An issue where jobs were disappearing after re-phasing sales order lines has been resolved. The problem was traced back to a previous update that incorrectly assigned job line numbers based on sales order line numbers. This incorrect logic was identified and removed restoring the visibility of jobs in reports. The fix ensures that all job types particularly those for Walls are now correctly displayed in job reports. This resolution allows users to view and modify all relevant job details seamlessly in the system.

In previous versions changes to user fields on jobs were accurately reflected in the record history but an issue arose where these updates were no longer visible. This problem was resolved by modifying the way user-defined fields are linked to job records. Instead of relying on an ID the linkage now uses the job number ensuring that any changes made to user fields are correctly recorded. This update guarantees that the record history will now display all modifications made to user fields restoring the expected functionality.

We have resolved an issue where incorrect quantities were displayed on the Job Pick List report particularly when multiple job lines were linked to different sales orders. This problem was caused by an incorrect method of obtaining issued lots for the report which led to inaccuracies in the pick list details. The development team has updated the report generation process to ensure that job lines are correctly identified resulting in accurate display of issued materials. Users should now see the correct quantities on the Job Pick List report after issuing materials ensuring clarity and accuracy for all job-related documentation.

We addressed an issue where jobs were incorrectly duplicated on the front end after re-phasing sales order lines causing confusion as only one job existed in the database. The problem stemmed from errors in line number assignments where duplicate line numbers were being generated. To resolve this we revised the system to organize and reassign line numbers based on existing data ensuring data integrity and preventing duplication. Additionally we fixed an issue with the deletion of lines that no longer belonged to a job phase ensuring they are correctly removed and reassigned. These changes ensure that job data is accurately displayed without unnecessary duplicates.

We have resolved an issue where partially unfinishing a lot with an original quantity of 1 caused it to disappear from the Production Detail report. This occurred due to a condition that mistakenly removed job completions with a quantity equal to one. This condition has been removed ensuring that when you unfinish a lot with a quantity less than 1 the correct remaining quantity is displayed in the report without disappearing. This adjustment ensures consistency and accuracy in the Production Detail report.

We have resolved an issue where modifying the description or priority in the Job Calendar inadvertently cleared the Job Dates 1-5 values. Previously when users made changes to these fields the date entries would disappear due to a lack of available data in the context of the Edit Data form. To address this we have implemented a safeguard to prevent the update of user date fields when editing descriptions or priorities ensuring that date values remain intact.

In the latest software version users experienced an issue where the planned quantity on the 'Job Material Cost Detail' report was calculated incorrectly compared to previous versions. This discrepancy was due to the report not considering a specific flag related to scaling custom additions with the job finish quantity. The development team addressed this by updating the code to include the flag allowing the report to dynamically select the correct data based on its status. As a result the report now accurately reflects the planned quantities resolving the issue.

In this update an issue was resolved where user-defined date fields 1 through 5 were not being saved in the Job Entry form. Previously when a new job was created and these date fields were set they would disappear upon saving and reopening the job. This problem has been addressed by adjusting the system to ensure that these date fields are preserved correctly after saving. Users can now confidently set and save dates in these fields without them being wiped out ensuring that all job-related information is retained accurately.

We have resolved an issue where the planned quantities for components of inventory relief phantom parts were not appearing in the Job Material Cost Detail report. Previously these quantities were missing which led to inconsistencies when compared with the Explosion/Indented BOM report. The system has been updated to ensure that planned quantities for phantom components are now correctly populated in the Job Material Cost Detail report aligning them with the calculations seen in the BOM report. This change ensures more accurate and consistent reporting of material costs across different reports.

In previous versions the Job Picklist encountered an issue where it failed to display details if the same item appeared on a job more than once. This was due to the system inadvertently overriding repeated item entries. The development team has resolved this by updating the system to recognize and correctly handle multiple instances of the same item within a job. Now when materials are issued the Job Picklist will accurately display all requirement lines ensuring that no details are lost regardless of item repetition.

A glitch was identified in the production jobs process where materials were being un-relieved in double the quantity when reopening a job multiple times. This was due to a logic error that incorrectly summed previously un-relieved materials. To resolve this the development team adjusted the logic and queries used in the 'Re-Open Job' feature. This change ensures that only relevant materials are considered during calculations preventing duplication errors. As a result the system now accurately manages the un-relieving process maintaining consistency in material quantities regardless of how many times a job is reopened.

We have resolved an issue with the Job Pick List report where a rework item specifically a Custom BOM part was not appearing after being issued to a job. This problem occurred in scenarios where multiple lines of the same item were present in a job. The development team made changes to ensure that once a part is issued it still appears correctly on the Job Pick List. This fix ensures accurate reporting and inventory management allowing users to see all required and issued materials in the pick list as expected.

An issue was identified where pallets were incorrectly marked as 'Failed' in the Auto Finisher client despite the finishes being successfully recorded in the database. This problem arose after changes were made to the system which affected the handling of items that are not set up as serialized or catch weight. The development team resolved this by updating the methods responsible for processing pallets ensuring that non-serialized and non-catch weight items are properly palletized. As a result the status of these pallets now correctly updates to 'Complete' after processing.

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.

An issue was identified where individual finishes marked as complete in the AutoFinisher application were not appearing in the main application causing discrepancies in inventory records. This was due to a problem where failed finishes were incorrectly shown as complete. The development team addressed this by updating the process to ensure that any failure in inventory posting or relief is accurately detected. Now the system will reliably report a failure if a job finish does not fully complete ensuring consistency between the AutoFinisher and the main application.

We addressed an issue where creating maintenance jobs resulted in duplicate entries. Previously selecting 'Order All' to generate jobs for grouped maintenance tasks led to multiple jobs being created some of which repeated tasks. The system has been updated to consolidate all related tasks into a single multi-line job. This change prevents unnecessary duplication by removing excess job creation logic and introducing a condition to handle task grouping effectively. Users can now expect a streamlined process with one comprehensive job being created for all selected tasks.

An issue was identified in the Master Production Calendar where events were displayed on incorrect dates if users navigated to the previous week before the calendar fully loaded. Specifically this problem affected date transitions across month boundaries causing events like the Christmas Shutdown to appear incorrectly. To resolve this the development team replaced the method used for setting dates with a more reliable approach ensuring that dates are accurately rendered even when users switch views rapidly. This update prevents race conditions and ensures that navigating between weeks reflects the correct dates and events enhancing the calendar's reliability and user experience.

An issue was identified where the Production Calendar would crash when attempting to move a job to a different date. This was due to missing data columns and improper code handling which led to errors when trying to update job positions. The development team resolved this by adding necessary columns to the calendar's data queries and refining the code logic to ensure all required information is processed correctly. This fix allows users to move jobs within the calendar without encountering errors enhancing the overall functionality and reliability of the production scheduling tool.

A technical issue was resolved where a worker's details were not appearing on the master production calendar even though the option was available. The underlying problem was that the worker ID was not being properly updated in the system's data structures leading to inconsistencies. To address this the development team modified the system to ensure that the worker ID is consistently updated across all relevant data points whenever changes occur. This fix ensures that the assigned worker is correctly displayed on the master production calendar maintaining accurate and reliable scheduling information.

The issue with the Master Production Calendar has been resolved ensuring a smoother transition between 'week' and 'day' views. Previously switching from a week view to a day view would incorrectly display the Monday from the previous week instead of the current one. Now when users switch from a week view to a day view the calendar correctly displays the Monday of the week currently in view. This improvement enhances the user experience by providing consistent and expected navigation within the calendar.

When creating multiple jobs through the MRO system users experienced an issue where job quantities were incorrectly inflated. The expected quantity for each job was one but the system was generating larger quantities. This problem has been resolved by implementing a check to determine if jobs are related ensuring that quantities are summed only for related jobs. As a result each job created now reflects the correct quantity aligning with user expectations.

In the latest update an issue was resolved where the note message format from the scale setup was not being transferred to the notes field during the final staging process. This problem affected the implementation and quality control processes by leaving the notes field empty when using scales in version 16.07.054. The development team has now ensured that the note message format is correctly passed through so users will see the expected note messages such as tare and gross weights appear in the notes field during final staging. This fix enhances the accuracy and completeness of the documentation associated with staged inventory.

We have addressed the issue of delayed printing with the AutoFinisher by optimizing the database. This was achieved by adding new indexes to improve the performance of the autofinisher and autorun tables. These changes ensure that the system processes print jobs more efficiently reducing the time it takes for labels to be printed and preventing production delays. The new indexes are incorporated into the system during installation or updates and a SQL script is available for deployment in cloud environments. This should resolve the issue of recurring delays without the need for server reboots.

The issue with Purchase Order workflows not updating correctly when backorders are modified has been resolved. Previously workflows did not automatically adjust to the correct sequence when changes were made to the quantity or total value of a backorder. This was addressed by refining the code responsible for handling workflow sequences and ensuring that workflows are correctly set to copy to backorders based on default settings. Development changes included updating the function responsible for managing workflow copies allowing for accurate sequence updates when a Purchase Order becomes a backorder. Now workflows will automatically populate to the appropriate sequence after modifications ensuring smoother processing and accurate workflow tracking.

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. This change ensures that the report runs smoothly without errors allowing users to view purchase order details seamlessly.

In version 17.02.019.0001 of the software an issue was identified where adding the 'pu_notes' field to the grid in Order Reporting caused an error. This was due to a duplicated reference in the system which led to a logic sequence error when attempting to reload the report. The development team resolved this issue by removing the redundant 'pu_notes' field from the query ensuring that the grid now loads correctly without errors. Users can now add 'pu_notes' to their grid layouts and view the notes without encountering any issues.

A technical issue was identified where the email address from a previous vendor was incorrectly retained and used when generating purchase order confirmations for a different vendor without an email setup. This could lead to purchase orders being sent to the wrong vendor. The development team resolved this issue by ensuring that the email field is cleared before each new email is generated. This fix prevents previous vendor email addresses from being mistakenly used in new transactions ensuring that the correct email address or no email at all if none is configured is used for each vendor.

An issue was identified where purchase order (PO) header notes were not saving correctly when receiving a PO through the Warehouse Management System (WMS). This occurred regardless of whether notes were added via WMS or left blank. To resolve this a new 'Lot Notes' field was introduced to manage specific notes related to lot records while 'PO Notes' now correctly update and save to the PO header ensuring that all notes are preserved during the receiving process. This development ensures that PO header notes entered in the main application are retained and accurately reflected after receiving the PO in WMS.

After upgrading to version 17.3 some users experienced an issue where disbursements for certain vendors were not displaying correctly. This was due to a limitation in the data type used for storing large numbers. The development team resolved this by changing the data type from 'INT' to 'BIGINT' allowing the system to handle larger values and display all disbursements accurately. As a result users should now see complete and up-to-date records when sorting disbursements by date.

Previously when changing the facility on a purchase order the line item prices would update but the total order amount would not automatically adjust to reflect these changes. This discrepancy could lead to inaccuracies in the order totals. The issue has been resolved by ensuring that any change in facility now triggers a recalculation of the order totals so that both the extension price and the overall order amount are correctly updated. This automatic adjustment eliminates the need for manual recalculations streamlining the process and ensuring consistency in order reporting.

We have resolved an issue that occurred when receiving a 'Transfer and Hold' Purchase Order (PO) with non-Deacom items. Previously users encountered errors when processing these types of POs. The system has now been updated to correctly handle the receipt of such POs. On the first receipt items are received into the holding facility and on the second receipt they are transferred to the production facility. These changes ensure that the process runs smoothly without errors. Users can find more information in the Help System documentation.

An error occurred during the purchase order receiving process due to a mismatch between quality control (QC) groups linked to items and the QC groups displayed in the system. This resulted in errors when attempting to copy QC data. The issue was traced to the system displaying incorrect QC group results particularly when multiple QC assignments were present but only one had the correct flag set. To resolve this the system now filters results more accurately before opening the QC copy form ensuring that only the correct QC group data is shown. This adjustment prevents errors during the copying process streamlining the purchase order receiving workflow.

A recent update resolves an issue where modifying a Quality Control (QC) Group resulted in duplicate test entries during subsequent QC result entries for raw materials. Previously after changing a QC Group users experienced a loss of initial test results and encountered duplicate tests requiring them to re-enter results for all tests. The system now correctly updates records to reflect the current QC Group ensuring only the relevant tests are displayed without duplication. This change ensures a smoother and more accurate QC process by maintaining the integrity of test records after modifications to QC Groups.

An issue was identified in the Quality Control (QC) Detail report where incorrect results were displayed when filtering by job number. This discrepancy was due to the report pulling data from multiple jobs that shared the same lot number rather than isolating results to the specific job in question. The development team has resolved this by adjusting the query logic to ensure that QC data is accurately matched to the correct job lines. With this update users will now see consistent and accurate results when filtering the QC Detail report by job number.

An issue was resolved where job quality control (QC) documents were not displaying all tests after production had started or QC results were entered. Previously these documents would only show completed tests but now they consistently include all expected tests and targets regardless of production status or QC entries. This ensures that job labels always display comprehensive QC data facilitating accurate tracking and reporting throughout the production process.

After an update to the production environment an automated process inadvertently altered quality control fields for several inventory lots which led to issues with stability testing. Specifically the system changed certain fields from 'Yes' to 'No' affecting the approval status of these lots. This was traced back to a function that did not correctly sort quality control entries by date causing the system to reference outdated information. To resolve this the function was modified to ensure that it uses the most recent quality control entry when determining if a stability test is due. This correction has been applied to the current version and retroactively to previous versions improving the accuracy of stability testing processes.

In response to lots getting stuck in QC Pending due to a setup mismatch between the Bill of Materials (BOM) and item master the system has been updated to prevent this issue. Now if a lot is produced before the QC group is added to the BOM a prompt will alert users guiding them to add the QC group to the current BOM revision before moving the lot to QC Pending. Alternatively the system will allow the move if the QC group is only present in the item master and it will automatically open the QC group as PO QC Testing. These changes ensure that lots are properly tracked and managed without requiring manual interventions or data programs to release stuck lots.

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

In certain cases the Quality Control (QC) Group was not correctly connecting to job lines causing a recurring issue that required daily intervention. This problem was particularly prevalent in two specific QC Groups. The resolution involved ensuring that when lots are successfully QC'd and incorporated into regular inventory the system properly clears the at-risk status for all related records. Development changes focused on preventing lots from being mistakenly retained in an at-risk state after QC completion which was the root cause of the QC Group not attaching correctly. This fix ensures that the QC Group now consistently connects to job lines without requiring manual updates.

A technical issue was identified where Quality Control (QC) Group updates were incorrectly applied to open jobs even when users opted not to update them. This was resolved by storing the relationship between job lines and their associated QC Groups at the time of job creation. Now if a user chooses not to update open jobs the previous QC Group version will remain associated with the job. Conversely if a user decides to update the new QC Group is applied and any unposted QC results are removed to ensure data integrity. These changes ensure that jobs maintain the correct QC parameters based on user selections preventing unintended data alterations.

In the Deacom system there was an issue where Quality Control (QC) Groups were not being properly applied to all system lots on the Purchasing QC Entry Screen. This problem occurred when only the first system lot would correctly display QC Groups while subsequent lots did not. The development team resolved this by updating the process to ensure that QC Groups are consistently gathered for user lots even when they are split and have multiple QC Groups assigned. The solution involved adjusting the sequence sorting by both user lot and QC name allowing for accurate handling of parts or revisions with multiple QC Groups. This fix ensures that all system lots associated with a user lot now correctly display their QC Groups enhancing the reliability of the QC process in the system.

An issue was identified where incorrect Bill of Materials (BOM) revisions were applied to job lines causing products to be manufactured without the correct Quality Control (QC) groups. This occurred when a QC test group was updated and users chose to apply the changes to open jobs resulting in a mismatch of revision IDs across job lines. The resolution involved ensuring that each product retained its specific QC group and associated BOM revision during updates. Development changes were made to maintain the integrity of product-revision relationships preventing errors and ensuring that only the correct QC group is applied to each job line. This improvement helps streamline production processes and reduces the need for manual checks and relabeling of products.

A configuration issue was identified that prevented all quality control (QC) test groups from printing on specification sheets when multiple groups were added to a customer part. The system was set to display only QC tests from the item master excluding those from customer parts. This resulted in incomplete information being printed. The solution involved addressing the configuration setup rather than making any development changes. The issue was resolved by clarifying the correct configuration approach as a training matter ensuring that all relevant QC tests are now correctly included on specification sheets for customer parts.

In this update users can now successfully move a produced lot back to 'Pending QC' status even if the formula only includes pre-production quality control (QC) measures. Previously an error occurred when attempting this action due to the lack of QC groups attached to the lot's revision. The development team addressed this by modifying the software logic to utilize the QC settings from the Item Master when no QC groups are specified in the bill of materials (BOM). This ensures that lots originating from jobs can be moved to QC without error as long as the Item Master has a QC group assigned and the BOM does not include post-production QC groups.

We have addressed an issue where drop shipment sales orders were incorrectly being marked as backordered even after the linked purchase order was fully received. This was due to a configuration error in the system that did not allow backorders for certain parts. To resolve this we introduced an additional validation step to ensure the backorder amount is calculated correctly. This change has been implemented across various versions of the software to ensure consistent functionality.

A technical issue was identified in the Sales Order Entry system where modifications could be lost if a workflow task was selected while the order was still saving. This was due to a column ID being set to null during the save process. To resolve this a safeguard was implemented to check for null values before opening the workflow form ensuring that no actions occur until the save is complete. This fix prevents loss of data and ensures that the workflow task form can be accessed successfully after saving.

An issue was identified where the default settings in the sales order reporting were incorrectly altering the 'rank by' field from 'Bill to company' to 'Bill-to Territory'. This occurred despite the settings being initially saved to rank by 'Bill to company'. The development team has resolved this by updating the method responsible for setting the 'rank by' field values when the Order reporting form is loaded. Now the system correctly uses the saved values from the Rank list ensuring that user preferences are maintained without unexpected changes.

A bug was identified where an incorrect prompt appeared when increasing the number of sales decimals from one to two. The prompt mistakenly warned users about decreasing decimals which could impact various system areas like lot quantities and open orders. The issue was resolved by updating the code to ensure it uses real-time data from the active form rather than outdated database information. This change allows the system to accurately validate the most current input preventing incorrect warnings and ensuring smooth user experience.

An issue was identified where copying a sales order with the 'Retain Original Price' option led to incorrect unit conversions particularly affecting cases where items are stocked in bulk but sold individually. This problem has been resolved by addressing a rounding error in the system ensuring that unit conversions remain accurate when this option is selected. The fix has been implemented in version 1607 and later ensuring consistent and reliable calculations for sales orders.

In the latest update an issue was identified where multiple selections were allowed in the sales order entry feature selection even when the 'Multiple Selection' option was not enabled. This was due to endpoints not being removed from the list which led to multiple selections being displayed. The development team resolved this by ensuring that only one selection is permitted at a time. If a new selection is made the previous selection is automatically deselected and removed from the feature list preventing the display of multiple selections. This fix restores the expected behavior ensuring that only single selections are saved when 'Multiple Selection' is not set to true.

A bug was identified where changing the unit price of a feature item in the sales order resulted in incorrect pricing calculations. The system was mistakenly adding the entered price to the existing feature price leading to inflated totals. This issue has been resolved by updating the system to allow users to directly set the unit price bypassing any automatic feature price calculations. Now when users manually input a new unit price the system correctly reflects this change without adding any additional amounts.

A recent update caused an issue where users with Sales Group restrictions could no longer see the 'All' option in the Sales Rep Filter within Sales Order Reporting. This was due to a conflict with previous restriction logic changes. The development team adjusted the logic to restore the 'All' option while maintaining compatibility with other system updates. This ensures that users can once again view all sales orders as intended without restrictions affecting their access.

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 with drop shipment orders where canceling a purchase order (PO) linked to a sales order (SO) could inadvertently cancel the entire shipped order. This problem occurred when a sales order with multiple lines was associated with multiple purchase orders. If the PO tied to one of these lines was canceled after part of the order had been shipped the entire sales order was marked as canceled. To resolve this the system was updated to better manage the relationships between sales orders and purchase orders. Now if a PO is canceled and the sales order has other lines linked to different POs the link to the canceled PO is removed without affecting the shipped status of the sales order. Additionally a new prompt was introduced to handle situations where a sales order cannot be canceled ensuring more reliable and accurate order processing.

A Logical System Error (LSE) previously occurred when users attempted to pay multiple orders using the NET1 payment method especially when these orders spanned different facilities. The issue stemmed from the system's inability to resolve a single facility for processing leading to complications in generating the necessary Bill-To Facility data. The development team addressed this by adjusting the logic to accommodate scenarios where a single facility cannot be determined allowing the payment processor to be set at the Bill-To level instead. As a result users can now process payments for multiple orders across different facilities without encountering an LSE streamlining the payment process in the system.

A problem was identified where certain DXA files were not importing correctly into sales orders specifically when processed consecutively. This issue occurred without any error messages leading to missing order lines. The development team resolved this by addressing a silent failure in the import process. Now all relevant lines from DXA files import as expected ensuring that sales orders are complete and accurate after the import process.

In the latest update discrepancies in the Commissions/Rebates Line Level Detail Report have been addressed. The issue stemmed from inconsistencies in how payments were calculated and displayed across different versions. The development team resolved this by removing an unnecessary default date range filter and refining the calculation logic to ensure accurate summation of results without duplication. Additionally rounding discrepancies have been minimized by implementing a more precise rounding method at the line level. These changes ensure that payment values are accurately reflected in reports aligning them more closely with the intended commission rule settings.

A problem was identified where promotional discounts were incorrectly calculated when the same item appeared on different lines of a sales order. This issue occurred specifically when using a promotion type based on an expression. The development team resolved this by adjusting the calculation method to account for multiple lines of the same product. As a result promotions now accurately apply the intended discount ensuring consistent and correct pricing across sales orders. This fix enhances the accuracy of promotional tariffs providing reliable discount calculations for customers.

An issue was identified when modifying the search box for 'Part Number' in the Sales Order Line entry form which resulted in an error. The problem stemmed from legacy code that was incompatible with SQL Server causing execution issues. To resolve this the development team replaced the outdated code with a static value ensuring smoother operation and compatibility. This change prevents errors when adjusting the layout of the 'Part Number' field allowing users to modify search box parameters without issues. Other searchboxes such as 'Cust Part Number' were unaffected and continue to function correctly.

We fixed an issue in the Sales Order Reporting feature where using the 'Clear' function caused duplicate entries to appear in the Order Summary report. This problem occurred when users selected 'Clear' before setting their report filters and viewing the results. Our solution ensures that all variables are properly reset with new values after the 'Clear' button is used preventing duplicate results and allowing the report to accurately display a single entry as intended.

We have resolved an issue where invoice adjustments for milk purchases were incorrectly using the stock unit instead of the purchase unit leading to inaccurate pricing extensions. The system now properly applies unit of measure conversions during invoice adjustments ensuring that pricing calculations align with the purchase and pricing units. This update includes significant changes to the form layout aligning the quantity price and extension fields to reflect accurate invoice details. These improvements ensure that the calculated values for milk purchases are precise and consistent with the intended pricing structure.

A technical issue was identified where promotional discounts applied to sales orders were not correctly reflected in the total due amount after the order was shipped. The problem occurred when promotions were configured to apply upon shipment causing discrepancies in the calculation of the total order amount. To resolve this the logic for applying promotions was improved by refining the criteria used to match promotional lines with specific order lines. This enhancement ensures that promotions are accurately applied across different lines of the same part correcting the total due calculation. As a result the system now correctly reflects promotional discounts in the final order amount after shipment.

We have resolved an issue where promotions requiring a minimum order quantity were not being applied correctly. Previously even when the ordered quantity exceeded the minimum requirement the system failed to recognize it preventing the promotion from being added automatically. This fix ensures that when the promotion setup specifies a minimum quantity the ordered amount is accurately considered allowing the discount to be applied as intended. This adjustment aligns with the documented logic ensuring that promotions are seamlessly integrated into sales orders when criteria are met.

In this update we've addressed an issue where deal pricing was not being retained when copying sales orders. Now when you select the 'Retain Original Prices' option during the order copy process the original sales order prices will be accurately carried over to the new order. This was achieved by introducing a new property to ensure that the pricing information is consistently passed throughout the copying process. Additionally adjustments were made to maintain manual pricing settings and to skip sales tax calculations during the copy. These changes ensure that the copied sales order accurately reflects the original pricing enhancing the reliability of order management.

A technical issue was identified where selecting a UPC code on a sales order line would inadvertently clear the quoted cost field. This problem has been resolved by implementing a development change that ensures the quoted cost remains intact when a UPC code is selected. Users can now select UPC codes without affecting the quoted cost maintaining the integrity of sales order information.

A technical issue was identified where leaving the 'Modify Info' form open during the shipping and invoicing of a sales order could result in the ship and invoice dates being cleared. This also affected the order history which did not reflect the shipping and invoicing events. The resolution involved adjusting the sequence of operations to ensure the locking mechanism is applied correctly. This was achieved by repositioning the lock validation to occur after the sales order has been saved ensuring that the lock is applied to the most recent record. This change ensures that the ship and invoice dates as well as the order history are accurately maintained.

We have addressed an issue with the UPC number field on the Edit Sales Order Line form where the default UPC number was not automatically appearing when selecting a part number. Additionally if the part number was changed the UPC number did not update accordingly causing mismatches. To resolve this we made changes to ensure that the UPC number is now correctly populated when a specific part number is searched. This update also applies when an item is accessed through the customer part ensuring that the UPC number updates appropriately to reflect the correct item information.

A technical issue was identified where users encountered a prompt when selecting items with restricted selling categories even though the facility was configured to allow these categories. The resolution involved ensuring that facility-level overrides were correctly accounted for preventing unnecessary prompts. Development changes included optimizing the method used to handle user prompts avoiding redundant initialization that slowed down the process. This fix ensures that users can add items from restricted categories without interruption when facility settings permit it.

We have resolved an issue where saving an order with multiple promotions for the same item would cause an error. Previously when two promotional discounts were applied to the same item the system would incorrectly assign the same identifier to both promotions leading to conflicts. To fix this we have changed the way promotional lines are identified by assigning a unique identifier to each promo line. This change ensures that multiple promotions can be applied to the same item without causing errors allowing for seamless order processing.

In the latest update a technical issue was identified where certain features that were set to default options were not being correctly applied when entering sales orders for feature items. The development team has resolved this issue by adjusting the integration process. Specifically they ensured that the correct feature link is added and matches the intended configuration. With these changes the system now correctly pre-selects the appropriate features restoring the expected functionality for sales order entries.

In the sales order reporting system there was an issue where user-defined fields (UDF) on sales order lines were not displaying correctly in the Allocations/Simple report. The columns for these fields appeared but the values were missing despite being filled in. This was caused by a mismatch in the database field reference where the system incorrectly used a field identifier that did not correspond to the correct data. The development team resolved this by adjusting the query to reference the correct field ensuring that UDF values now display as expected in the report.

A fix has been implemented to address an issue where sales orders were posting revenue to incorrect general ledger accounts. Previously when a user manually selected a specific credit sales account on a sales order line the system would sometimes ignore that selection and instead post to the item's default revenue account even when no GL overrides were configured on the customer facility or other related records.The resolution clarifies and corrects the expected behavior for GL override handling. When a GL override is present anywhere in the configuration hierarchy the override will take precedence over any user-selected credit sales account on the order line. However when no GL override exists the account manually selected by the user on the sales order line will now correctly flow through the invoicing process and be used for the general ledger posting. A new tracking mechanism was added to properly identify whether a GL override is present and to ensure the appropriate account is used based on that determination.

An issue was resolved in the sales reporting system where custom criteria filters would malfunction when more than one criterion was applied using both AND" and "OR" logic. Previously this caused the filter to ignore the specified criteria and return all data instead of the intended filtered results. The development team has fixed this by ensuring that filters are correctly applied based on the logic specified allowing users to combine multiple criteria effectively. This improvement will ensure that reports generated with complex criteria combinations now display accurate data as intended."

In the Order Entry system users previously encountered an issue where duplicate lines appeared in the Basic Item Availability window causing confusion when checking stock levels. This problem has been resolved by refining the underlying query to ensure unique results are displayed for each facility. Users can now view accurate item availability without encountering repeated entries enhancing the overall efficiency and reliability of the order management process.

When a sales order was un-shipped the system inadvertently reassigned License Plate Numbers (LPNs) for certain lots leading to confusion in inventory tracking. This issue arose from a script that automatically assigns LPNs when a sales order is saved which was triggered during the un-shipping process. The development team has addressed this by ensuring that LPNs remain unchanged when a sales order is un-shipped maintaining consistency in inventory records. This fix prevents duplicate lot entries and incorrect LPN assignments ensuring accurate inventory reporting and tracking.

An issue with the Feature" function where changing a feature from "no" to "yes" was not working as expected has been fixed. This problem was due to features linked to parts not being correctly included in the feature list. The development team resolved this by updating the validation process to ensure that all relevant features are captured and displayed appropriately when a part is selected. As a result users can now successfully change the feature status and save their selections without encountering errors."

A recent issue with credit card transactions was identified and resolved where users encountered errors when attempting to void transactions. The problem stemmed from the use of Zero Dollar Authorization" settings which are not supported by the VikingServices processor. To address this the system has been updated to disable Zero Dollar Authorizations for Viking aligning it with other processors like Moneris. Users should now set transaction terms to "With Authorization" to ensure smooth processing and authorization of orders. This change prevents authorization failures and ensures compatibility with Viking's supported transaction methods."

We have addressed an issue where selecting a workflow on the sales order view detail form was slow caused screen flickering and did not close after a selection was made. To resolve this the option to select a workflow type via the sprocket has been disabled as changes cannot be saved in this view. This adjustment ensures a smoother user experience without unnecessary delays or visual disruptions.

In response to issues with importing engineered items improvements have been made to enhance the user experience during the import process from Alpine HomeBASE databases. The system now bypasses unnecessary folder checks simplifying the import procedure. Additionally if the required database or views are missing users will receive clear and informative prompts reducing confusion and potential errors. These changes ensure smoother operations when using the import feature particularly in environments where these databases are utilized.

In the latest update we have addressed an issue where users received a prompt incorrectly stating that selected features were no longer available when multiple feature items were added to a sales order. This pop-up message was misleading as users could dismiss it and continue with their order without any actual impact on the features or Bill of Materials (BOM). Additionally recalculating rules did not affect the availability of features as suggested by the prompt. The development team has implemented changes to ensure that features are correctly matched with sales order lines preventing unnecessary alerts. Now when recalculating expired quotes with multiple feature items the system accurately reflects available features and users will only be notified if a feature is genuinely unavailable.

We have resolved an issue where default order details were not automatically populating when a new shipping address was selected during sales order entry. Previously when a new 'Ship-To' address was created and selected fields such as Freight Ship via Broker Division Territory Price Code Discount 1 and Discount 2 were not being filled in as expected. To address this we implemented a check to ensure that fields are only replaced when they contain valid information preventing them from being overwritten with empty data. This change ensures that all necessary order defaults are correctly applied when a new 'Ship-To' address is used in the order entry process.

An issue was identified where a blank line appeared in the Order History when a sales order was copied and the 'Re-calc Prices' option was selected before saving. This has been resolved by updating the system logic to prevent unnecessary blank lines from being added. The solution involved implementing a conditional check to ensure that a blank line is not inserted if the Order History field is empty. This update ensures that the Order History displays correctly preserving the accuracy and integrity of the sales order information.

An issue was identified where attempting to ship a locked sales order could lead to confusion. When users tried to ship an order that was locked for editing and chose not to cancel their changes elsewhere the system incorrectly opened a window to print shipping documents suggesting the order had been shipped when it had not. This has been resolved by ensuring that if a user decides not to cancel their changes the shipping process does not proceed and the print window does not open. This prevents any misleading prompts and ensures clarity in the shipping process.

In the Promotions and Discounts screen an issue was identified where the 'For Name' field was not displaying correctly. This field intended to show specific billing company names was instead showing 'All Bill to Companies' or was left blank. The problem was traced to an earlier setup where the 'For Name' field defaulted to a generic value and wasn't updated properly when changes occurred. The solution involved updating the logic to ensure the 'For Name' field accurately reflects the billing group or company name based on the selected criteria. Users experiencing this issue should edit and resave existing records to correct any previously inaccurate entries as the functionality now operates as intended.

We have addressed an issue where User-Defined Fields (UDFs) were not being copied correctly when using the 'Copy Order' function in Sales Order Entry. Previously the UDFs were only partially copied due to an incorrect handling of the original Sales Order ID resulting in data loss. The development team resolved this by ensuring the original ID is correctly retained and linked during the copy process allowing all UDFs to be accurately transferred to the new order. These changes ensure that when a sales order is duplicated all associated information including UDFs is preserved as expected.

A technical issue was identified where changes made to a sales order during shipping could be inadvertently overridden resulting in a sales order header missing important shipping information. This occurred when multiple users interacted with the same order simultaneously bypassing the system's lock mechanism. To resolve this a new verification process has been implemented to ensure that the lock status of a sales order is accurately checked before printing. This enhancement prevents unauthorized changes and maintains the integrity of the order's shipping details even when multiple users are involved.

In the sales order entry process there was an issue where feature items were removed when a promotion was selected before saving the order. This problem led to difficulties in printing documents as the system reported missing feature parts. The development team resolved this by ensuring that features are preserved when promotions are added. The solution involved synchronizing the sales order with the feature form before applying promo lines so that all selected features remain intact on the order. This change ensures that the printed documents correctly reflect the chosen features preventing any loss of information.

A technical issue was identified where an error occurred when generating sales calendars particularly when the 'Ship Via Phone' option was selected in the sales options screen. This was due to inconsistencies in how phone numbers were formatted in the database leading to errors during processing. To resolve this the development team enhanced the system's ability to handle multiple phone number formats by utilizing utility functions that can manage various formats such as '123-123-1234' and '1231231234'. This change ensures that the sales calendar can be generated correctly without errors regardless of the phone number format used.

When creating a new sales order by copying an existing one that includes feature options and a linked header job the header job would mistakenly transfer to the new order. This issue has been resolved so that the header job remains linked only to the original sales order. A new attribute has been added to track order copying actions ensuring that header jobs do not transfer during the process. Users can now confidently copy sales orders without affecting the linkage of header jobs to the original order.

We have addressed an issue where a system prompt would incorrectly appear when updating a sales order linked to a production job. The problem was caused by a missing check for null values in the process which could lead to errors. To resolve this our development team added a verification step within the system's code to ensure that all necessary parameters are present before proceeding with operations. This update ensures that users will no longer encounter unexpected prompts when modifying sales orders enhancing the stability and reliability of the order management process.

We have resolved an issue that was preventing users from adding items from restricted categories to sales orders even when the customer had the category listed in their Restricted Selling tab. This fix ensures that items from restricted categories can only be added if they are specified in the customer's Restricted Selling tab. Additionally users without the appropriate security settings to override restricted selling will no longer see these items in the part number filter during order entry. This change corrects a previous update and aligns the system behavior with the intended functionality ensuring proper enforcement of sales restrictions.

A recent update ensures that custom fields associated with billing information are now correctly considered when calculating promotions and discounts. Previously promotions relying on these user-defined fields did not apply correctly leading to pricing errors. The development team addressed this by updating the system to include these fields in the promotion calculations ensuring that discounts are applied as intended. This change allows for accurate application of promotions based on specific billing criteria enhancing the reliability of promotional pricing.

A technical issue that prevented customers from setting up Deal Pricing based on item search fields has been resolved. Previously users encountered an error message when attempting to save a new deal due to a constraint violation. The development team addressed this by correctly mapping the 'Deal On' name to the appropriate tables which affected several item search fields. This fix ensures that users can now successfully save deals without encountering the previous error.

We have addressed an issue with the Sales Order API where certain line item details such as category subcategory item planner and various user-defined fields were missing from the response. The development team resolved this by adjusting the item creation process to use a more comprehensive response generation method. This ensures that all relevant data fields are correctly populated in the API response. Users can now expect complete and accurate information when posting new sales orders through the API.

A recent update has resolved an issue where users encountered an authentication error when saving sales orders with certain FedEx shipping methods. The problem stemmed from the customer's FedEx account not having the Service Availability API enabled which is necessary for validating all FedEx service types. The update includes improvements to the system's handling of FedEx service requests ensuring that users are notified if a facility cannot be found during the validation process. Additionally the update addresses a previous error related to null references enhancing the system's reliability when processing shipping methods.

The issue where sales dates were not updating when job dates changed has been resolved. Previously even with the synchronization option enabled changes to job dates did not reflect in linked sales orders if the sales order was locked. The system now provides a prompt when attempting to save a job if the linked sales order is locked preventing unsaved changes. Additionally unnecessary transaction calls were removed to ensure that changes are only saved if no errors occur during the save process. This update ensures that date synchronization between jobs and sales orders functions correctly improving workflow efficiency.

There was an issue with the MatAdd form layout where users encountered an incorrect permission requirement. The system mistakenly required the 'Item Master – add new' permission instead of the correct 'Toolbar – edit form layouts' permission to modify the form layout. This error resulted in an 'Access denied' message when attempting changes without the unnecessary permission. The development team resolved the issue by implementing a conditional check to ensure that only the appropriate permission is required for modifying the MatAdd form layout. Users can now modify the form layout without needing the 'Item Master – add new' permission ensuring smoother access and functionality.

A security access issue has been resolved for users creating sales orders with line jobs. Previously users without the necessary permissions to edit production jobs encountered errors when attempting to save sales orders with a 'Create Line Job' option checked. This resulted in a blank edit form when trying to modify the sales order line. The system now correctly handles permissions allowing users to create jobs from a sales order line without losing information even if they lack editing permissions. This improvement ensures seamless sales order processing without unexpected prompts or blank forms.

In this update we addressed an issue where users with permission to edit sales deal pricing were unable to add or modify deals because the options were inaccessible. The problem stemmed from the system not recognizing the correct security permissions for sales-related deal pricing. We have revised the security logic to ensure that it now properly checks for both sales and purchasing permissions allowing users with the appropriate sales permissions to access and modify deal pricing as intended. This change ensures that access is aligned with the user's security level resolving the issue effectively.

We have resolved an issue in the Master Security grid where rearranging columns and double-clicking on them inadvertently altered permissions for different roles than intended. This problem occurred when users attempted to adjust column widths and then changed permissions causing unexpected modifications. To address this we have refined the workflow to ensure that permissions are correctly updated only for the intended columns. Additionally we have improved the system's communication and technology integration to support these changes ensuring a more reliable and efficient user experience.

An issue was identified where running Favorites 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.

We have addressed an issue concerning the emailing of purchase orders with attached documents. Previously when selecting the option to print attached documents emails included all document versions including historical ones which was not intended. This has been resolved by updating the system to only include attachments with a valid status. Now when you choose to email a purchase order with attachments only the current and relevant documents will be sent preventing any confusion caused by the inclusion of outdated versions.

Users encountered an issue where attempting to view the record history for any User Group resulted in an error message. This problem was caused by a missing condition in the system's code. The development team has resolved this by adding the necessary logic to handle User Group records correctly preventing the error from occurring. Now when users select the Record History option for a User Group the history will display as expected without any interruptions.

The issue of emails not launching properly in the new Outlook when using the 'Print to Email' feature has been resolved. Updates have been made to the system to ensure compatibility with the new Outlook desktop. The installer has been enhanced to include necessary components that facilitate the creation of preformatted email templates. This allows emails to be sent correctly and ensures that a draft window opens as expected. Users should ensure they have the latest version of the Deacom installer to benefit from these improvements.

We have resolved an issue where specific category variables were not appearing in the transaction report grid. This problem occurred when users attempted to include certain fields in their reports but the fields failed to display. To address this we updated the selection query to ensure these fields are correctly included and visible in the report.

Fixed an issue where the Deacom Query Tool was failing to interpret queries which contain semicolons in a string utilized in the WHERE clause.

An issue was identified where scheduled events were not functioning correctly for syncing data with Salesforce in the second company environment. Although manual execution worked properly the automated process failed to update a specific field leading to duplicate data being sent. To resolve this a fallback mechanism was introduced to ensure the correct company database is referenced during automated operations. Optional parameters were added to relevant methods to support this adjustment. These changes ensure that scheduled events now correctly populate the necessary field maintaining data consistency across both manual and automated processes.

An issue was identified when trying to add a new company database resulting in an error message and the database being marked inactive. This problem was caused by a conflict with an existing table name. To resolve this the development team implemented checks to validate the presence of table names in the database before creating new entries. If a table name already exists a clear prompt now informs the user preventing the error from occurring. These changes ensure smoother operation when adding new company databases.

An issue was identified where users were unable to edit the 'Control Source' field when attempting to pre-filter customer queries using the Management Reporting tool. This field was mistakenly marked as required preventing users from saving their queries. The problem arose when the wrong pre-filter type was opened leading to the inability to select a control source. This has been resolved by ensuring the correct pre-filter type opens when users click the Pre-Filter button allowing the 'Control Source' field to be properly filled and queries to be saved successfully.

A recent update ensures that when a part number is changed within the system it now consistently updates across all relevant documents including purchase orders. Previously while the updated part number would reflect correctly in sales orders jobs and bills of materials purchase orders would still display the old part number. This discrepancy has been resolved ensuring uniformity and accuracy across all document types when part numbers are modified.

In previous versions users could set favorites to automatically use the first of the month as a start date without needing to manually input the date each time. However a recent update caused favorites to prompt users for a start date disrupting this functionality. To resolve this developers rolled back changes from a previous update and adjusted the code to ensure that when favorites are used the system correctly recognizes the start date as the first of the month. This fix restores the expected behavior allowing users to set favorites without additional prompts for start dates.

We have addressed an issue where resizing columns in a grid could cause the data rows to misalign with the headers when scrolling. This fix ensures that when you adjust column sizes both the headers and data remain synchronized. Additionally if a grid does not fill its section horizontally the rows will now correctly extend with the appropriate background color. These improvements provide a smoother and more consistent user experience when interacting with grid layouts.

The issue with the 'Unique' setting in form layouts which was not functioning as expected has been resolved. Previously regardless of the selected option records were saved without any prompts or restrictions when duplicate entries were made. The solution involved updating the logic to ensure that the system correctly identifies non-null values and determines when a prompt should be displayed or when saving should be prevented. This adjustment ensures that users are now properly notified or restricted when attempting to save duplicate entries aligning the system's behavior with the intended functionality of the 'Unique' setting.

The issue where users marked to change their password at the next login were not prompted to do so when accessing Deacom Mobile or Deacom WMS has been resolved. Previously this functionality only worked on the main application potentially allowing users to continue using insecure passwords. To address this the development team has implemented changes that ensure the password change requirement is now enforced across all platforms including mobile and WMS. Users will be prompted to update their password upon their next login enhancing security and consistency across the applications.

In the latest update an issue was resolved where email addresses were not being populated when attempting to send combined invoices via email. This problem reoccurred after a recent hotfix. The development team identified that the code responsible for grouping emails did not correctly include the necessary recipient addresses. The solution involved updating the method responsible for handling email outputs to ensure that all required addresses are included when grouping emails. With these changes users should now see the correct email addresses populated in the 'To' field when sending combined invoices.

We have resolved an issue where automatic exports set to run weekly would only execute successfully the first time and then fail to run on subsequent scheduled dates. The problem was traced to an incorrect query condition that mismanaged the execution schedule by comparing the last export date incorrectly. This has been corrected to ensure that weekly and monthly auto-exports now execute consistently as scheduled. Users can now rely on these exports to run on the correct day without needing to manually trigger them or adjust their settings. The fix ensures that the process does not inadvertently repeat on the same day providing a more reliable and predictable export functionality.

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.

In this update a fix has been implemented to address an issue with the user email field not decrypting correctly when navigating through user accounts using the 'Next' or 'Previous' buttons. Previously the email field would remain encrypted unless accessed directly. The system now ensures that the email field is properly decrypted when cycling through user accounts providing a seamless experience. This enhancement improves the reliability of the user management interface by ensuring consistent decryption of sensitive information.

Attachments with a comma in their file names were not downloading correctly causing them to be saved as an un-openable file type. This issue has been resolved by modifying the system to automatically remove unsafe characters including commas from file names before downloading. This ensures that all files regardless of their original naming are downloaded in a format that can be opened and viewed properly.

An issue was identified where exporting data from Deacom to Excel did not maintain the correct number of decimal places as displayed in the application grid. Users experienced discrepancies with exported Excel files showing fewer decimals than intended. The development team resolved this by implementing a formatting mechanism that ensures the exported Excel files reflect the exact number of decimals as shown in Deacom. This improvement guarantees that numerical values in Excel match their grid representation enhancing data accuracy and consistency for users.

An issue was identified on a server experiencing high traffic resulting in 500 errors due to a concurrency exception. The problem was traced to the API logger's interaction with the database where operations were expected to affect a certain number of rows but didn't. To address this the development team modified the TransactorContext to create a new scope specifically for the API logger. This change aims to prevent the concurrency issue and ensure the server operates smoothly under high traffic conditions with authentication requests and endpoint responses functioning correctly.

A recent update to the Warehouse Management System (WMS) now allows for successful scanning and counting of Catch Weight Items with expired Master Lots during physical inventory. Previously users encountered errors when attempting to scan expired lots but the system has been adjusted to include these lots in the inventory process. The expiration date format on Master Lot labels has been standardized to ensure compatibility with scanning devices. Additionally guidance has been provided on the correct workflow for entering System Lot and Master Lot details ensuring that all associated lots are accurately counted and recorded. These improvements address previous issues and enhance the accuracy and functionality of physical inventory tasks within the WMS.

An issue was identified where the Warehouse Management System (WMS) reserved more items for a sales order than confirmed causing discrepancies during shipping. This problem has been resolved by reworking the reservation process for substituted items. Now when multiple sub parts are reserved to a single sales order line the correct reserved quantities are reflected in the main application during shipping. A new class was introduced to accurately track substituted parts ensuring that the order quantity aligns with the sales unit of the parent part. This update ensures that the reserved quantities are consistent and accurate allowing for correct shipping of orders without excess or incorrect quantities.

In the latest update an issue was resolved where the barcode scanning functionality in the Warehouse Management System (WMS) was not correctly excluding vendor numbers and remapping part numbers during the Purchase Order (PO) receiving process. Previously barcodes using Application Identifier (AI) 90 for vendor numbers were incorrectly processed causing errors when matching parts to orders. The development team has corrected the logic for handling GS1 Application Identifiers ensuring that vendor numbers are properly excluded and part numbers are accurately remapped. This fix ensures smooth barcode scanning and accurate inventory tracking during PO receipt.

There was an issue where the Warehouse Management System (WMS) did not consistently apply the default finish quantity specified in the item master during production input. This inconsistency led to incorrect default quantities being displayed. The development team has resolved this by ensuring the WMS now correctly honors the default finish quantity aligning it with the stock unit of the part. Additionally unnecessary unit conversions or events will no longer occur when loading new part information ensuring quantities are set accurately by default. Users can still change the finish unit if needed with conversions executing properly thereafter.

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. These changes ensure accurate inventory management and improve the functionality of reserving and issuing items in the WMS.

Users were experiencing an error message when attempting to de-issue from a master lot using scanners in the Warehouse Management System (WMS). The error occurred because the system was not properly handling the selection of issue types leading to a reference error. The development team resolved this by updating the process to automatically bypass the issue type selection when dealing with master lot transactions. This change ensures that users can now de-issue master lots without encountering any errors allowing the transaction to proceed smoothly.

A recent update to the Warehouse Management System (WMS) has resolved an issue where users were unable to move an entire lot without being prompted to select a specific system lot. Previously when attempting to move all lots sharing the same user lot for a part the system incorrectly required a selection of a system lot despite the Use Entire" option being set to "User Lot." The development team has implemented a check that prevents this prompt allowing the move to proceed smoothly when the entire user lot is selected. This enhancement ensures that inventory moves can be conducted without unnecessary interruptions streamlining the process for users."

We have addressed an issue where users were unable to select lots by location in the WMS Reserve Sales Order process unless they had permission to issue substitutions. This was problematic as substitutions involve different part numbers not different lots. The solution involved restoring the WMS Substitute Lots functionality without requiring additional licensing allowing users to choose lots without needing substitution permissions. This change ensures that Essentials clients can access the Lots chooser seamlessly while Enterprise clients can manage lots without needing substitution permissions maintaining the intended security settings.

A recent update to the Warehouse Management System (WMS) resolves the issue where production jobs with multiple lines of the same part were not advancing correctly after completing the full quantity on a line. Users can now input production jobs with multiple lines for the same part without encountering issues. The system has been enhanced to differentiate job lines by their unique identifiers ensuring each line progresses correctly once the quantity is completed. This change allows for proper handling of separate pre-production quality control results for each batch preventing overproduction on a single line. The solution ensures that all job lines are displayed and completed as expected providing a seamless production input experience.

We have resolved an issue where users were unable to move inventory into containers using the Warehouse Management System (WMS). The problem was related to the logic setting the selected item back to the destination container field which has now been corrected. With this fix users can successfully move lots to containers through the WMS Move Inventory form. The system will now accurately reflect inventory moves in the appropriate containers ensuring seamless tracking and reporting of inventory adjustments.

The issue preventing users from issuing expired items to master lots in the Warehouse Management System (WMS) has been resolved. Previously a system prompt error occurred due to a missing part number resulting in a null reference error. The development team addressed this by implementing a check to handle cases where certain values may be null ensuring that expired lots can now be issued correctly without errors. This fix allows users to proceed with issuing expired lots seamlessly aligning the functionality of the WMS with the main application.

We have resolved an issue within the Warehouse Management System (WMS) that prevented purchase order lines with only a description and no part number from being successfully received. Previously users could not process these lines which led to disruptions when handling orders containing non-inventory parts. The system has been updated to correctly recognize and process these lines allowing for seamless receipt of items described without a part number. This enhancement ensures that all parts regardless of their inventory status can be handled efficiently during the receiving process.

A technical issue in the Warehouse Management System (WMS) was causing errors when users attempted to issue substitute master lots for jobs. The system failed to recognize the substitute part during the initial scan of the master lot label prompting users incorrectly. This has been resolved by allowing users to issue substitute lots when scanning a master lot label provided all lots in the master lot contain the same part. Development changes included updating the system to validate if a part on the job exists in the master lot and checking if it can be a valid substitution. This ensures accurate processing of scanned inputs allowing seamless issuance of substitute master lots to jobs.

An issue was identified where catch weights entered in the Warehouse Management System (WMS) would revert to default values instead of saving the user-inputted values. This problem occurred because the system was incorrectly prioritizing the default item master weight over the user-entered weight. To resolve this the logic that involved the 'Include Tare Weight in Catch Weight' setting was removed. Now the system will always honor the weight entered by users during the input production process ensuring that the catch weight reflects the user's input regardless of tare weight settings. This change guarantees that user-entered weights are accurately recorded and displayed in inventory reports.

A problem was identified where the scanner in the Warehouse Management System (WMS) only displayed the last three digits of an item quantity when scanning labels specifically affecting quantities over 999. This was traced back to the way quantities were formatted on the lot label part form not an issue with the WMS itself. The solution involved updating the label format to show six digits before the decimal point ensuring the full quantity is visible when scanned. This adjustment required no changes to the underlying code only a modification in how the quantity is expressed on the label.

Users faced difficulties selecting specific lots when attempting to de-issue from a master lot in the Warehouse Management System (WMS). Previously clicking the 'lots' button did not open a selection screen hindering the de-issue process for multiple lots within a master lot. The development team has resolved this issue by ensuring the necessary form loading functions are executed correctly before checking for items on the form. This adjustment addresses the non-responsive behavior encountered in earlier Android WMS versions. Now users can click the 'lots' button to access a lot chooser screen allowing them to select and de-issue specific user lots from a master lot without any interruptions.

In the Android version of the DEACOM Warehouse Management System (WMS) there was an issue where scanning barcodes with the prefix 'BUTTON+' did not trigger the intended actions. This problem was due to the system incorrectly retaining button scan events after a form was closed mistakenly associating them with the login screen. The development team has fixed this by ensuring that all button scan events are properly cleared when a form is closed. Now when you scan a 'BUTTON+' barcode the application correctly responds by executing the appropriate action enhancing the functionality and reliability of the barcode scanning feature.

In the Warehouse Management System (WMS) used on Android devices there was an issue where lot information such as the expiration date would not automatically fill in during the physical inventory process if the oldest record for a lot was located in a different facility. This problem led to the Deacom app crashing on emulators although it remained stable on physical scanners despite the missing data. The development team resolved this by adding a feature that alerts users when a lot is unavailable in the selected facility preventing the app from crashing and ensuring users receive necessary feedback. This enhancement improves the user experience by providing clear notifications when expected data is missing.

An error was identified in the Automation Console when using Android WMS devices with specified versions. Users encountered a message indicating that the app could not update to the correct version despite being on the correct version. This issue did not affect the functionality of the scanners but caused confusion among users. The root cause was related to the shared project setup and has been resolved by removing the shared project and implementing versioning for the Deacom WMS. This change ensures the system correctly recognizes the app version eliminating the erroneous update message.