Sage 300 2022 Release Notes

Product Update 7 program fixes

The following sections describe program fixes included in Product Update 7.

Intercompany Transactions

Fixed a problem that prevented the user from processing the Update Company function. (Reference #8009773509)

Product Update 6 program fixes

The following sections describe program fixes included in Product Update 6.

Banking

Fixed a problem in bank reconciliation where a withdrawal amount would get stuck in the withdrawal field after reversal. (Reference #8009658363)

General Ledger

Fixed a problem with the printing object in Financial Reporter. (Reference #8007288528)

Common Services

Fixed a problem in Common Services to avoid fiscal periods from prior years become unlocked after upgrade. (Reference #8009502528)

Product Update 5 program fixes

The following sections describe program fixes included in Product Update 5.

System Manager

Fixed a problem for which the user incorrectly receives a message indicating the maximum number of concurrent users have been reached even though there is sufficient user counts available. The issue appears to occur when there is an increase in activity via third-party add-on. (Reference #8009476339) (Reference #8009583454) (Reference #8009580890)

Fixed a problem on Web Screens where relevant information may be missing during import failures (Reference #8009467685)

Accounts Payable

Fixed a problem for which the Aatrix upload function does not take into consideration Vendor 1099 Tax Number Type.  (Reference #8009462978)

Fixed a problem for which the Aatrix Upload function uses Vendor Name instead of Legal Name (Reference #8009491289)

Inventory Control

Fixed a problem where Inventory Control Internal Usage does not display Location Segment Override G/L Account (Reference #8009363711)

Order Entry

Fixed a problem in Credit/Debit Note Entry web screen where the data may get corrupted when the Credit Note number is manually entered instead of letting the system generate the number. (Reference #8009481877)

Project and Job Costing

Fixed a performance problem when drilling down to a Job Costing Timecard Entry from the Job Costing Billing Worksheet. (Reference #8009529899)

Lot Number

Fixed a problem in O/E Shipment Entry web screen to correct the lot expiry date of an item if the Qty Shipped field for the item is zero (Reference #8009571355)

Intercompany Transactions

Fixed a problem where Finder crashes when selecting Vendor on 2nd Entry of Invoice Batch (Reference #8009464750)

Product Update 4 program fixes

The following sections describe program fixes included in Product Update 4.

General Ledger

Fixed a problem where the Journal Entry import does not check if the Entry Date is valid or not in the import file, causing it to import invalid dates in the details.

Purchase Order

Changed the behavior in P/O Invoice Entry. Previously, P/O Invoice Entry allowed the user to post the invoice even when there is a duplicate invoice number. Now, it will give an error when the invoice for the vendor already exists.

Item Inquiry

Fixed a problem that may cause slow performance when navigating to the Bill of Material tab on the I/C Item Inquiry screen.

Accounts Receivable

A change was made to Sage 300cloud web screens A/R Invoice printing. It now defaults to the last invoice report file you printed.

Product Update 3 program fixes

The following sections describe program fixes included in Product Update 3.

Retrieving records that include a G/L account number

In many Sage 300cloud web screens, transactions or records that include a G/L account number are retrieved faster. (Reference #8009246827)

Bank Services

Fixed a problem on the Reconcile Statements screen that prevented you from clearing transactions for a customer or vendor if you posted the transactions and then changed the customer/vendor number before clearing the transactions. (Reference #8009184903)

Accounts Payable

Fixed a problem on the Payment Entry screen in Sage 300cloud web screens that could occur when adding a detail line in the table. When you clicked Add Line, instead of adding a new detail line, some information in existing detail lines would be changed to incorrect information. (Reference #8009274937)

General Ledger

Fixed some problems that could prevent you from using Financial Reporter. You can now use Financial Reporter if:

• You do not use Optional Fields. (Reference #8009120576)
• There is a space in the path of the Sage 300 program files.

Order Entry

• Fixed a problem in Sage 300 desktop screens that could prevent you from approving prices or credit checks if your system is set up to require complex passwords. (Reference #8009196429)
• Fixed a problem on the Copy Orders screen that could occur if you use Pricing Unit as the Default Order UOM (this is set on the Processing tab of the O/E Options screen), which prevented you from copying orders for a customer if an inventory location is not specified for the customer (on the Invoicing tab of the A/R Customers screen). (Reference #8009215442)
• Fixed a problem on the Order Entry screen in Sage 300cloud web screens, which could prevent comments and instructions for order details from being saved. (Reference #8009231401)

Sage CRM Integration

• In Sage CRM, the following fields on the A/R Customer screen now use the current date by default (instead of the Sage 300 session date):
  • Statistics tab: Fiscal Period and Fiscal Year fields
  • Comments tab: Date Entered field (in the table)
  • Credit Status tab: Age As Of field

  (Reference #8008611017)

• If you create a new company in Sage CRM by importing a Customer from Sage 300 (either manually or using automatic synchronization), the correct contact information appears for the company in Sage CRM. (Reference #8009130716)

Item Number Change

Fixed a problem that could prevent you from combining item numbers. (Reference #8009233392)

Product Update 2 program fixes

The following sections describe program fixes included in Product Update 2.

Printing Reports in Web Screens

Fixed a problem that could cause Sage 300cloud web screens to stop responding if you printed a large number of reports. (Reference #8008991907)

Changing the Session Date

Fixed a problem in Sage 300cloud web screens that could prevent you from changing the session date.

Note: If you change the session date, the new date is not used in screens that are currently open. To use the new session date in these screens, you must close the screens and then open them again.

Emailing Documents

When you email documents from Sage 300 using SMTP, emails are now sent using TLS 1.2. (Reference #8008914787)

Bank Services

On the Bank Reconcile E-Statements screen, when manually matching a deposit by deposit slip, the Match Transaction to Bank screen opens faster. (Reference #8008948886)

Accounts Receivable

• If you use multicurrency accounting, the Outstanding Balance email message variable ($OUTSTANDING_BALANCE) shows amounts in the customer’s currency, not the functional currency. (Reference #8009066514)
• Fixed a problem in multicurrency systems that could cause mismatching functional-currency amounts for the shipment clearing account to be sent to G/L from an O/E Shipment and the corresponding A/R Invoice. (Reference #8008969611)

Accounts Payable

In Sage 300cloud web screens, when you export the Aged Trial Balance report in Excel Record format, information on the report is aligned correctly. (Reference #8008906831)

Order Entry

Fixed a problem in Sage 300 desktop screens that occurred if you use Ops Inquiry, which prevented you from drilling down to Ops Inquiry screens from O/E transaction entry screens (Order Entry, Shipment Entry, Invoice Entry, Credit/Debit Note Entry). Now transaction entry screens show the Item Drill button, and they also show drilldown buttons beside the Last Shipment No and Last Invoice No fields. (Reference #8008969429)

Customer Number Change

Fixed a problem that occurred if you use the Multiple Contacts (M/T) program, which caused some contact information for a customer to be lost when you changed the customer number. (Reference #8008991541)

Vendor Number Change

Fixed a problem that occurred when you combined two vendor numbers, which caused some information (such as payments) to be lost for one of the vendors. (Reference #8008735717)

Product Update 1 program fixes

The following sections describe program fixes included in Product Update 1.

Printing Checks

When printing checks from the Print Checks screen (for example, for an A/P payment or an A/R refund) using Checks Then Advices as the stock type, two fields – Check Form and Advice Form – appear allowing you to specify a check form and an advice form. (Reference #8008374342)

General Ledger

• On the Journal Entry screen, Sales Tax and Purchases Tax journal entries automatically include optional fields that are set up to be auto-inserted for transactions. (Reference #8008834226)
• Finders in Financial Reporter now work when using Microsoft Excel 64-bit.

Inventory Control

On the Location Details screen in Sage 300 desktop screens, you can now see longer item descriptions (beside the Item Number field). (Reference #8008841968)

Order Entry

• In Sage 300cloud web screens, emailing quotes and orders from the Order Entry screen is now faster. The increased speed is most noticeable if you have a large database. (Reference #8008803761)
• On the Order Entry screen in Sage 300cloud web screens, the order discount (shown in the Less Order Discount fields on the Totals tab) is always updated if the order subtotal changes. Previously, the order discount was not updated if you changed the order subtotal and immediately posted the order without first viewing the Totals tab. (Reference #8008851326)

Project and Job Costing

Fixed a problem on the Contract Maintenance screen that could prevent you from importing a contract. (Reference #8008895155)

Ops Inquiry

Item descriptions appear on the BOM tab of the IC Item Inquiry screen. (Reference #8008228043)

Sage 300 2022 program fixes

Sage 300 2022 includes program fixes for some problems that exist in the most recent previous version (Sage 300 2021 Product Update 2). The following sections describe these program fixes.

Signing in to Web Screens

Fixed a problem that could occur when signing in to Sage 300cloud web screens, which required you to sign in twice.

Accounts Receivable

• Fixed a problem on the Create Interest Batches screen that occurred if you have optional fields that are set up as required. Regardless of whether or not you entered information in these fields, an “optional field is missing” message appeared and prevented you from creating interest batches. (Reference #8008709438)
• Fixed a problem on the Receipt Entry screen in Sage 300cloud web screens, which could prevent you from viewing or modifying optional fields. (Reference #8008699063)

Accounts Payable

• Fixed a problem on the Clear History screen that prevented you from clearing history for fully paid documents. (Reference #8008608203)
• Fixed a problem in Sage 300cloud web screens that could occur on the Invoicing tab of the Vendors screen, which prevented you from entering information in the Distribution Code, Distribution Set, or G/L Account field (if one of these methods is specified in the Distribute By field). This problem occurred for vendors who are part of a vendor group that has no default method specified (on the Invoicing tab of the Vendor Groups screen) for distributing invoice amounts to general ledger accounts. Reference #8008607790)

General Ledger

• Fixed a problem on the Create Allocation Batch screen in Sage 300cloud web screens, which could prevent you from making a selection in the Create Batch For field. (Reference #8008256472)
• Fixed a problem that occurred if you use multicurrency accounting, which caused incorrect exchange rates to be entered in G/L transactions for bank entries. (Reference #8008689707)
• In Sage 300cloud web screens, when you export the Transactions Listing report in Excel format, information on the report is aligned correctly. (Reference #8008805145)

Inventory Control

• If you select the Allow Fractional Quantities option on the I/C Options screen, when you save your changes you are asked to confirm that you want to allow fractional quantities. (Reference #8008728369)
• On the Lot Numbers Inquiry screen, the Lot Number Finder displays correct information in the Quantity Shippable and Quantity On Order fields. Previously, these fields displayed incorrect information if the Use the Qty Ordered field in OE for the Allocation of Lot Numbers option is selected on the Lots tab of the I/C Options screen, which also caused related data integrity check errors. (Reference #8008757900)

Order Entry

Fixed a problem that could prevent an item’s unit price (specified in Inventory Control) from being automatically entered in the Unit Price field for details in O/E transaction entry screens. This problem occurred only if:

• On the Processing tab of the O/E Options screen, the Default Order UOM field is set to Pricing Unit.
• On the I/C Item Pricing screen, the item is set up as follows:
  • On the Prices tab, the Base Price Type field is set to Base Price Calculated Using a Cost.
  • On the Discounts tab, the Selling Price Based On field is set to anything other than Discount or Markup on Markup Cost.

(Reference #8008665468)

Sage CRM Integration

• In Sage CRM, you can enter and change information on the Customer Bill-To Address screen. (Reference #8008598406)
• In Sage CRM, the Company A/R Promote and Company A/P Promote security authorizations control which features users see for promoting customers and vendors to Sage 300:
  • Users with neither security authorization do not see the Promote to Sage 300 tab.
  • Users with at least one of the security authorizations see the Promote to Sage 300 tab where they can open the Promote to Sage 300 screen, and on that screen they see the features they are authorized to use (for example, a user with Company A/R Promote security authorization sees features for promoting customers to Sage 300 but does not see features for promoting vendors).
• Fixed a problem that occurred if you changed the address for a company while promoting that company from Sage CRM to Sage 300, which prevented the address change from appearing in most Sage CRM screens (though the address change did appear in Sage 300).

Compatibility changes in this release include:

• Sage 300 supports Windows 11.

Installing product updates

After installing a product update:

• If you use Sage 300cloud web screens, you must use Database Setup to configure the Portal database again.
• If you use Sage CRM integrated with Sage 300, you must upgrade your CRM integration as follows:
  • Install the Sage CRM integration for Sage 300, which is available on Sage Knowledgebase article 45434.
  • Uninstall and then reinstall the Sage CRM Synchronization Component. (Use the Sage CRM Workstation Setup screen in Sage 300 to install the Sage CRM Synchronization Component.)
• If you use Sage Intelligence Reporting Cloud, you must customize some Sage 300 program files, and then you must reset IIS. For more information, see Sage Knowledgebase article 84722.
• You should clear your browser’s cache. (Some fixes included in the update may not take effect until you do.)
• On any workstations you use, you must reinstall workstation setup as the Windows administrator user if:
  • The product update includes changes to workstation setup.
  • An earlier product update includes changes to workstation setup, and you have not previously installed that product update or any other subsequent product update.

    Example: Suppose that the current Product Update is 5. Product Update 2 includes changes to workstation setup, and the other product updates do not. You have been using Product Update 1. You did not install Product Update 2, 3, or 4. You have now installed Product Update 5. To update your workstations with the changes to workstation setup that were included in Product Update 2, you must reinstall workstation setup.

  The following product updates include changes to workstation setup:

  • Product Update 2

Sage Intelligence Reporting Cloud

Sage Intelligence Reporting Cloud is a financial reporting tool integrated with Sage 300cloud.

To use Sage Intelligence Reporting Cloud:

• You must customize some Sage 300 program files, and then you must reset IIS. For more information, see Sage Knowledgebase article 84722.
• Each user who will use Sage Intelligence Reporting Cloud must be assigned to a security group with Financial Reporter security authorization for Sage 300 General Ledger and Sage 300 Web API security authorization for Sage 300 Common Services.

We recommend that you configure Sage 300cloud web screens to run in a secured environment using digital certificates. If you do not, warnings will appear in your browser each time you start Sage Intelligence Reporting Cloud. For more information, see Sage Knowledgebase article 84797.

Sage 300 Software Development Kit

This section lists improvements and fixes for the Sage 300 Software Development Kit (for desktop screens) and the Sage 300 Web Software Development Kit (for web screens).