Search Results for

    Show / Hide Table of Contents

    Acctivate Version 12

    Version 12.0

    QuickBooks Online integration, Purchase Order Manager, Product List Transactions tab, Picklist improvements, Microsoft 365 email integration

    12.0 sp1

    Version 12.0 sp1 was made generally available on March 14, 2023 (Build 6455)

    ⭐ = Features and improvements

    Create Company

    • Fix the error "Acctivate error (91:0x5B) Object variable or With block variable not set" that would occur during the customer import portion of the Create Company process. The error is caused customer ship to addresses that have no "name" (i.e., Location ID). Instead, those locations will be ignore during the import.

    Custom Fields

    • Fix a bug where control characters such as Ctrl+C (copy) and Ctrl+V (paste) wouldn't work in numeric custom fields. If a non-numeric value is pasted into a numeric custom field, the value will be cleared when saving the related record.

    Customer

    • Fix an issue where QuickBooks Desktop Acctivate companies could receive the error "Could not get Intuit access token: HTTP 400: {"error":"invalid_request"}" when opening a customer.

    Data Presentation

    • Fix issue where deleted product warehouses would continue to show in the Inventory tab of the Product List.
    • Fix an issue where the Transactions List would cause Acctivate to not respond when viewing a transaction with a large number of detail lines. Also, fix an issue where the "Draft" text may be hidden behind transaction lines.

    EDI

    • Prevent errors from occurring when opening the Process EDI window by ensuring that EDI partner mailbox paths are constructed and formatted properly when used by Acctivate.

    Email

    • Fix an issue where the Connect button for Microsoft 365 in the user section of the Configuration Manager could incorrectly be displayed as "Disconnect" even though the user's Microsoft 365 account had not been connected.

    General

    • Attempt to prevent the the error "Cannot access the Acctivate data directory. Your system administrator must add permissions…" that may occur when launching Acctivate when an antivirus program is scanning the AcctivateData directory. To test that the workstation has access to the AcctivateData directory, a temporary file is created in the AcctivateData folder and then deleted by the workstation. If the file is being scanned by an antivirus program the delete may fail, causing the error. Instead, Acctivate will retry the deletion three times before reporting an error.

    Installation

    • When performing an Acctivate installation, a different message will be shown if the AcctivateData directory is not accessible versus an Acct.ini file not being present in the AcctivateData directory. This fixes an issue where an ambiguous message was displayed when the installer could not complete.
    • Fix an issue where the /layout command line option would upgrade Acctivate rather than generate an offline copy of the Acctivate installation files.

    Inventory

    • Fix the color theme of the Void Inventory Session window to match the theme used throughout Acctivate.

    Mobile

    • When transferring lot/serial products using the Android Transfer module, the lot/serial number's total transfer quantity will be compared against the lot/serial number's quantity on hand to prevent over selecting of a lot/serial number.
    • When picking lot/serial products using the Android Order Picking module, the lot/serial number's total transfer quantity will be compared against the lot/serial number's quantity on hand to prevent over selecting of a lot/serial number.
    • In Android Sales Order picking, when attempting to over pick an order line, a warning sound will occur and a message stating that the quantity picked cannot exceed the quantity to pick. The qty will then revert to the quantity picked.
    • In the Acctivate app for Android, on screen messages that auto hide will now stay visible on screen for six seconds, however tapping the message will dismiss it sooner. Previously, these messages would stay on screen for only one second which was too brief in most cases.
    • Make changes to the audible feedback in the Acctivate Android app so that they are more consistent. Warning messages, such as the message "The quantity ordered of product 'SomeProduct' has already been fulfilled", will play three ascending tones. Error messages, such as "Product not found", will play a harsher sound. If the error is related to missing or invalid barcode information, the error sound will play and the barcode info screen will display in an attempt to give more context to the error.
    • Fix "Invalid value for Sql parameter" error that would occur when using the product lookup in Acctivate on Windows Mobile devices.
    • Fix an issue where it wasn't possible to enter a decimal point in some of the weight and quantity fields of order picking, picklist picking, inventory receipts, and inventory transfers on Acctivate Mobile for Android.
    • In Android Sales Order picking, if a lot/serial barcode is scanned while in the Add/Edit Lot # window and the line has its full qty already picked, the scanned lot/serial number is added and the qty is changed to zero. Previously, these zero qty lot/serial lines would get added to the order. Now, when the Add/Edit Lot # window is closed the zero qty lot/serial numbers will not be added.

    Payment

    • When processing an Authorize.net payment for multiple invoices, the invoice numbers will be transmitted with a quantity of one and the invoice's total amount will be sent as the Unit Price/Item Total, rather than sending $1 as a placeholder amount.
    • When creating a payment from the Enter Sales Order window, the cursor will start in the Payment Amount field of the Enter Payment window. When typing or looking up a customer, the cursor will move to the Payment Amount field after the customer is found.
    • Fix an issue in QBO Acctivate companies where payments created in a model company would get deleted.

    Product

    • ⭐ Create a new data view, ProductUnitFactor, which includes the unit factor relationship between a product's stocking unit and its primary sales, purchasing, and packaging units.
    • Fix "Sort order cannot be applied" error that would occur when viewing the Lot/Serial tab of the Edit Product window.
    • Increase the performance of product related queries by removing the Unit, UnitFactor, FactorBasis, Basis fields from the Product view for the product's sales, purchasing, and packaging units. These fields were added in 12.0, but resulted in a decrease of the Product view's performance. Also, add the NOEXPAND table hint to the ProductWarehouseSummary data view, where necessary, to ensure its indexed views are used to maximize the data view's performance.
    • Add an index to increase the performance of the LotSerialInventory data view to and prevent time outs when viewing the lot/serial tab of the Edit Product window and Product List.

    Sales Order

    • Fix the error "Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record." that may occur when viewing an invoice in the Customer Invoice / Credit memo window.
    • Fix an issue where the Tax field in the Customer Invoice / Credit Memo would appear blank.
    • When cancelling a quote, the workflow status will be set to Cancelled. This prevents the error "Cannot set workflow status on Quotes."
    • Fix issue where lot or serial numbers could not be viewed and selected in the Enter Credit memo window.

    Sales Tax

    • In QuickBooks Online US Acctivate companies, only sync the Tax and Non tax codes. This prevents the sync error "Valid line TaxCodes for US should be TAX or NON." that would occur when an unsupported tax code was made available in Acctivate.

    Shipping

    • ShipStation requires the qty to ship be an integer, therefore scheduled sales order quantities that include decimal will be rounded up to the nearest integer. This fixes an issue where the error "The request is invalid. Could not convert string to integer" would be returned when orders are sent to ShipStation.

    Synchronization

    • Disable the QuickBooks Online background sync for Model companies.
    • Fix an issue where applying a payment to a journal in QBO would cause the journal to have double its amount in Acctivate. Also, support has been added to sync charges from QuickBooks online during the background sync.
    • Increase the max length of tbCharge.RefNumber to 21, to match QuickBooks Online's Journal no. field length. This resolves the QuickBooks Online sync error "Cannot set column 'RefNumber'. The value violates the MaxLength limit of this column."
    • Support syncing customer refund checks from QuickBooks Online to Acctivate.
    • Fix a problem where payments in a QBO Acctivate company may have been re-synced from Acctivate to QBO after upgrading to version 12.0. Instead, Acctivate will perform a one time sync of payments from QBO to Acctivate to ensure all payments have the most up to date information in Acctivate.
    • Don't attempt to sync $0 payments that aren't linked to any other transaction in a QBO Acctivate companies. This resolves the QBO sync error "Business Validation Error: Enter a transaction amount to continue."
    • Add support for syncing QBO check transactions that are related to a customer. This fixes the sync warning "A payment line for payment 0adddc33-9248-4a95-95e8-a2f8c652c89b is linked to an unsupported transaction type Check".
    • Increase the max length of tbActivityLog.Reference to 500 characters. This prevents the error "String or binary data would be truncated in table 'Acctivate$AdvancedQBO.dbo.tbActivityLog', column 'Reference'." that would occur when saving a customer ID that is over 200 characters in length in QBO Acctivate companies.
    • When the invoice date of an Acctivate invoice is changed in QuickBooks Online, the sync will display a warning message that the date has changed and the invoice date will be reverted back to match the Acctivate invoice date. This fixes an issue where the sync error "System.NullReferenceException: Object reference not set to an instance of an object." would be returned instead of the warning.

    Web Store

    • If none of the order lines in a shipment are associated with BigCommerce order lines, then the shipment information will not be sent to BigCommerce; instead, a message will be logged. This avoids BigCommerce rejecting the shipment with the error "BigCommerce returned HTTP Status 400: Bad Request. The required field 'items' was not supplied."
    • When syncing with WooCommerce, if the web server returns a 5xx http status then the sync will pause ten seconds and retry again, up to four more times. This prevents the sync from abruptly ending due to intermittent web server issues.
    • When a "502 Bad Gateway cloudflare" error is returned by WooCommerce the sync will pause ten seconds and retry again, up to four more times. This prevents the sync from abruptly ending due to intermittent web server issues.
    • Fix an issue which caused the order fulfillment lines sent to Shopify to be empty, which Shopify interprets as the entire order being fulfilled. Now, only the fulfilled items and quantities will be sent to Shopify.
    • In BigCommerce V2 web stores, if the web store option "Export Carrier when exporting shipments" is enabled, a shipment's carrier will be exported as tracking_carrier to BigCommerce instead of shipping_provider. tracking_carrier supports a multitude of carriers, whereas shipping_provider only supports shipping service providers.
    • When the web store sync looks for orders pending redaction, it will not consider open Business Activities related to the customer but not related to the sales order. I.e., Acctivate will redact sales orders that have their directly related records completed (i.e., the order has no open invoice, Business Activities, Shipments, etc.), but if a customer has open Business Activities not related to the order, it will not prevent the completed order from being redacted. Redaction will occur in batches of up to 100 after each web store sync.
    • Fix a bug where the web store sync error "HTTP Status 400: Bad Request" returned by WooCommerce wasn't being treated as a warning as intended. This error is commonly due to the Web Order Number field on the Sales Order not corresponding to a WooCommerce Order ID. Instead, the warning "WooCommerce reported invalid order id: xxxx (Subdocument 'shipment')" will be returned and the sync will continue.

    12.0

    Version 12.0 was made generally available on January 30, 2023 (Build 6444)

    Business Activity

    • ⭐ Add support for multiple forms/reports for Business Activities. Reports assigned the Document Type "Business Activity Form" will be available to print from the Activities List, Enter Business Activity window, or Reports → Business Activity → Forms.

    Configuration

    • ⭐ Allow editing the Branch ID of an existing Branch.
    • ⭐ Copy warehouse GL accounts when copying an existing warehouse in the Create Company wizard or in the Configuration Manager.

    Create Company

    • ⭐ As part of the Create Company process, the Acctivate GUIDProduct will be recorded with the QuickBooks Item name in the table [tmpQBProd].
    • Fix an issue where choosing the Create Company option "Preserve Item Hierarchy when generating Acctivate Product IDs" while also importing in sales orders from QuickBooks would cause the orders to be imported with non-standard lines rather than linking to the related Acctivate product.

    Customer

    • In the CYMA edition of Acctivate, block changing the accounts receivable account of a Branch if there are customers or invoices that use that Branch. If customers should be using a new A/R account, then a new Branch can be created.

    Data Presentation

    • ⭐ Add the ability to print inventory transactions from the Transactions List.
    • In the Product List filter window, rather than show filter values by their short code, display the filter value's description.
    • Display the full transaction type description rather than the abbreviated transaction code in the Transaction list filter window. For example, the Transaction Type filter will now show "Receipt" rather than "R".

    Database Maintenance

    • Fix issue where the Database Maintenance window would close with the error "Run-time error '6': Overflow" when maximizing the Backup/Restore window within a maximized Database Maintenance window.
    • Improve the speed of a database update by batching insert scripts into groups of 100 to minimize the number of database calls that need to be made.

    Email

    • ⭐ Add support for sending email using Microsoft 365's REST API.
    • Fix an issue where the save/undo buttons weren't enabled when using the Insert Field button to insert a field into a message template.

    General

    • ⭐ Add "Close All" function to the Window menu in Acctivate. When selected, all open windows in Acctivate will be closed.
    • ⭐ If Acctivate's data directory permission check fails due to an error Acctivate will attempt to show more information on why the permission check failed.

    Import

    • ⭐ Add the ability to import in a location's position using the Warehouse Locations import. A position is the footprint in the warehouse the extends vertically and is occupied by multiple locations.
    • ⭐ In the Customer section of a customer import and the Order section of a web store import, allow mapping either a salesperson's name or salesperson ID for the Salesperson field.
    • ⭐ Add a "Skip import validation step" option to the data imports. When unchecked (default), a data validation step will occur which allows reviewing errors and editing certain data fields prior to import. When unchecked, the data validation step will be skipped, however invalid data will still be rejected and the user will be given the opportunity to save failed import data in a spreadsheet for re-importing.
    • In the Ship To section of a customer import and the Detail section of a web store import, allow mapping either a warehouse description or warehouse ID for the Warehouse field.
    • When an Inventory Receipt import template has the option "Post transactions" enabled and the receipt can't be posted due to duplicate serial numbers, a user friendly message will be displayed which includes information about the Product ID and duplicate serial numbers and the receipt session will not be created.
    • If a product is serial numbered, but doesn't use the Actual cost method, the Balanced Adjustment import would incorrectly give an error that the "Quantity must be 1, 0, or -1 for serial numbered products". Now, the import will not give the error, however a Balance Adjustment for a serial numbered product must be for the total on hand quantity as of the transaction date; only the value can be changed. This matches the behavior of the Enter Balance Adjustment window.
    • If a product is being created by the Product import and the item type is Inventoried or Special Order Only, require that a warehouse be provided.
    • When updating a product's bill of materials using the Product import, the validation that occurs now mimics the validation that occurs within the Edit Product window. This fixes an issue where the Product Import may unnecessarily block the updating of a product's bill of materials with the message "Assembly Type: Cannot change assembly type because the product is referenced by a sales order."
    • Fix the scenario that caused the error "InventoryControlType: Control Type is required" by removing the check for a mapped Control Type when using the import to update other fields of an existing product.
    • If a product is lot numbered, but doesn't use the Actual cost method, the Balanced Adjustment import would incorrectly give the error "LotNumber: Lot/Serial number is required." Now, the import will not give the error since a Balance Adjustment for a lot numbered product must be for the total on hand quantity. For products configured this way, the quantity or lot number fields should either not be mapped or, if they are mapped, should not contain any values. Only the unit cost or value can be changed for these types of products.
    • When importing inventory transfers, the stocking unit will be used if a unit is not mapped. When importing in inventory receipts, the stocking unit will be used if a PO number isn't mapped. If a PO number is mapped, the unit from the purchase order line will be used.
    • Fix a bug where the new customer Branch default set in the Configuration Manager was not being used when creating new customers using the customer import.
    • When importing a Balance Adjustment, block items that are not inventoried from being added to the transaction. If a product that is not inventoried is included in the import source file, the error "The product's Item Type must be Inventoried or Special Order Only." will be returned.
    • Rename Pager and Pager Description to Other and Other Description in the customer and sales order imports.
    • Prevent non-inventoried products from being imported with a List Price Type of Average Cost + Percent (C%) or Average Cost + Amount (C$).
    • When updating a product's bill of materials using the Product import, the validation that occurs now mimics the validation that occurs within the Edit Product window. This fixes an issue where the Product Import may unnecessarily block the updating of a product's bill of materials with the message "Cannot change assembly type because the product has inventory transactions."
    • When performing a product import the Control Type will be validated. This fixes an issue where products that aren't inventoried could be created with a Lot Numbered, Serial Numbered, or Numbered when invoiced Control Type.
    • When using the Product import to update a product's item type, check to see if the product has existing transactions before allowing the change.
    • When attempting to update a product's control type using the Product import, you will no longer be blocked from making the change due to the product being a component as long as the product does not have transactions and the new control type is valid.

    Inventory

    • ⭐ Use indexed data views to improve the performance of the ProductWarehouseSummary data view.
    • Modify the UnpostedTransferLotSummary database view to filter out posted transfers transactions.
    • Include Draft Inventory Transfer transactions in the LotSerialInventoryWithoutLastReceipt data view.
    • Modify the LotSerialInventory data view so that intra-warehouse transfers aren't considered when determining the last posted transaction date that added quantity to the lot/serial number (i.e., LotSerialInventory.TransactionDate).

    Inventory Accounting

    • ⭐ When Prior Period Adjustment transactions are created, use the related receipt transaction's GUIDPODetail and PONumber. Also set the original receipt's GUIDINVTransactionDetail as the adjustment's GUIDAssociatedITD.

    Inventory Assembly

    • ⭐ Improve certain assembly messages by including the affected assembly transaction number.
    • Fix "Object variable or With block variable not set Error" that would occur when opening the Enter Assemblies when the Windows Region settings are set to a region which has a number format where the decimal character is a comma instead of a period.
    • Fix error "There are fewer columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement." that would occur when opening the Enter Assemblies when the Windows Region settings are set to a region which has a number format where the decimal character is a comma instead of a period.

    Inventory Count

    • When a count session is generated and multiple location control is enabled, the count session will now include lot/serial numbers that have zero on hand if it has locations that have non-zero on hand. The "Include Empty Warehouse Locations" count option will include all locations used by that lot/serial number if checked and only those with non-zero on hand if unchecked. This allow correcting bin locations with incorrect on hand quantities.

    Inventory Receipt

    • ⭐ Add support for multiple forms/reports for Inventory Receipts. Reports assigned the Document Type "Inventory Receipt Form" will be available to print from a Posted or Draft Inventory Receipt.
    • ⭐ Allow printing the Put Away List for Inventory Receipt form for a Draft or Posted Inventory Receipt. The Put Away list can be printed from the Enter Inventory Receipts window.

    Inventory Transfer

    • ⭐ Create a new database view, UnpostedTransferLotLocationSummary, which includes unposted transfer records for lot/serial controlled products. The data view also includes the From warehouse location.
    • Fix a bug where the UnpostedTransferLocationSummary database view would use the product's primary location rather than the unposted transfer's From location.
    • Modify the Available calculation for the LotSerialLocationSummary data view. The availability for lot/serial locations is calculated by getting the quantity on hand, subtracting the quantity on open order lot/serial lines are not on an open picklist, subtracting quantities on open picklists, subtracting quantities on unposted assemblies, and subtracting quantities on unposted transfers.
    • Modify the UnpostedTransferSummary database view to ignore transfer detail lines that are not associated with a transfer session.

    Mobile

    • ⭐ Add support for the mobile picking option "New line for each lot number scan" when Picklists are enabled. The option can be enabled in the Mobile Order Picking section of the Configuration Manager.
    • ⭐ Add support for parsing GS1 encoded Data Matrix symbols on Android devices. This fixes an issue where the application identifiers were not parsed and the encoded data was interpreted as a single string of text.
    • Fix error "Could not get product information InvalidCastException" that would occur in Windows Mobile when adding a product to the an order in the Order Entry module.

    Product

    • ⭐ Add the default Sales, Purchasing, and Packaging factor units and factor basis type (e.g., Standard, Product Specific, etc.) to the Product data view.
    • ⭐ Add a Transactions tab to the Product List which includes all open, sales, purchasing, and posted inventory transactions. The Transactions tab includes the ability to hide/show certain columns and perform advanced filtering.
    • ⭐ In the Edit Product window, sort the Price Category field alphanumerically.
    • Return a user friendly message explaining that a lot/serial number already exists if an existing lot/serial number is being renamed to an existing lot/serial number.
    • Change the query used to populate the Lots (or Serial #'s) tab of the Edit Product window to match the query used to populate the Lot/Serial tab of the Product List.
    • Fix "Object variable or With block variable not set" error that would happen when creating a new FIFO product, opening additional windows, then clicking on the FIFO tab of the Edit Product window before saving the product.
    • If a location has zero quantity available and on hand, then the location will not be shown in the Locations card found on the Product List's Inventory tab. However, the primary location will always be displayed.

    Purchasing

    • ⭐ Add the Purchase Order Manager.
    • When multiple purchase invoices are created for a PO line that has inventory receipts in a closed period, first try and delete any previously prior period adjustments and create a new prior period adjustment for the sum of all prior period adjustments. If prior period adjustments can't be deleted, then a new prior period adjustment will be created for the adjustment amount of the invoice being created.
    • Prevent a Purchase Order from being reverted to the Entered status if the Entered status is not enabled in the Configuration Manager.
    • Block a user from reopening a Purchase Order if they do not have permission to issue POs and the default PO status is the Issued status.
    • Fix issue where Acctivate may crash when Avalara address validation is configured and an invalid address is entered in the Enter Purchase Order window.
    • Modify the Vendor and PO list window timelines to use the posted date for receipt and landed cost transactions. This fixes an issue where the session's created date was used rather than the posted date.

    Reports

    • ⭐ Add catch weights to customer facing sales order forms (Order, Pack List, Invoice). The total line weights are suppressed and could be un-suppressed if necessary.
    • ⭐ Improve the Put Away List for Inventory Receipts report. If multi-location tracking is enabled then the report is sorted by the warehouse location sort order. Otherwise, the report is sorted by the receipt line location.
    • Fix bug where the "Print Pack Lists for Picklists" button in the Picklist window would cause the Picklist to print. Now, the Pack List form for a Picklist is used.
    • If lot/serial numbers have been pre-selected for an order, show the lot/serial warehouse location. If only some, or none, of the lot/serial numbers have been selected then show the location from the sales order line as a reference for the picker.

    Sales Order

    • ⭐ Allow filtering on a sales order's Marketing Code in the Sales Order Manager window.
    • ⭐ Add a "Shipment Due Date" field to the Sales Order Manager which corresponds to the Promised Ship date if set; otherwise, it's the customer's Requested Ship date.
    • ⭐ Add the Last Shipment Date field to the Sales Order Manager window as an optional column.
    • ⭐ Add the Web Order Number field to the Sales Order Manager window as an optional column.
    • ⭐ Add the individual ship to and sold to address lines to the Sales Order Manager as optional columns.
    • ⭐ Add a Line Count field to the Sales Order Manager window as an optional column. Line Count represents the number of order lines (excluding components).
    • ⭐ Include non-inventoried products in Picklists. Non-inventoried products are tangible products that still need to be picked, but their inventory and locations are not tracked in Acctivate.
    • ⭐ Add the Amount Paid and Payment Method fields to the Sales Order Manager window as optional columns.
    • ⭐ Add the Total Amount field to the Sales Order Manager window as an optional column.
    • ⭐ Add an option to control the priority of which locations are selected when creating a Picklist. "Highest available first", the default, maintains the existing behavior of selecting locations with the most availability first in order to minimize the number of locations visited. Alternatively, the option "Lowest available first"", will prioritize locations with the lowest availability, allowing you to deplete secondary/overflow locations first. When multiple locations have the same availability, the location selected will be based on the location sort order (in the Locations section of the Configuration Manager) and then by location name.
    • ⭐ Allow clicking the Create Invoice button in the Enter Sales Order window while in edit mode. When clicked, the user will be asked if they want to save any changes and create the invoice. Once in the Create Invoice window, the Available Credits button will show the number of credits after any have been selected and applied to this invoice.
    • Remove the minimize button from the Enter Lot/Serial window and Component window of the Enter Sales Order window since it is a modal window and you must close it in order to work with other windows. This also prevents an issue where Acctivate would crash when minimizing the lot/serial window. The window can still be maximized and restored.
    • Fix an issue where a product's sales order pop-up note may not pop-up when the Product ID is typed into an order detail line rather than being added by using the Lookup window.
    • When preparing shipments from an order, invoiced quantities that have not been packaged will be excluded from the quantities added to the shipment. Also, if a kit's components have already been packaged, then the parent kit item will not be included any packages created later.
    • When changing a sales order's line type to Special Order (S), the line's outstanding quantity will be backordered and the warehouse will be changed to the special order warehouse associated with the order's branch, if one exists. When changing from an "S" line to a "P" line, the warehouse will be changed back to the Branch's warehouse and the line will be re-scheduled.
    • When Picklists are enabled, the Enter Sales Order window's lot/serial location will not be pre-filled. When you create a Picklist, the Picklist will assign the location(s) to be picked from. If you assign a location on the lot/serial line, the Picklist will use the location provided.
    • Make a correction to the message displayed when trying to update a sales order to an invalid workflow status; e.g., changing a Booked order to Ready to Pick.
    • Improve the warning message that would appear when invoicing a line with no scheduled quantities. Instead of "Order A1234T has no billable lines.", the message now states "Order A1234T has no lines with a scheduled quantity." Also, this warning is no longer logged to the Acctivate Exception log.
    • Increase the width of the On Hand and Available columns in the Lot/Serial selection window of the Enter Sales Order window.
    • Fix label and appearance issues in the Generate Serial #s window. Also, when the Generate Serial #s window is opened it will now open centered over the Enter Lot or Serial #s window.
    • Fix a bug where the Print Invoices window did not pass the invoice number range entered by a user to the report. Also fix a bug where using the "Print unprinted invoices" option may include more invoices than it should.
    • Add support for typing a Tax Category in the Enter Payment window to find a match. Once a typed character results in no match, the Tax Category list will display so that a selection can be made.
    • When cancelling sales order or quotes using the Sales Order Manager, change the workflow status to "Cancelled" to match the behavior that occurs when canceling a sales order from the Enter Sales Order window.

    Sales Order Import

    • Fix a bug where the Import Sales Order utility would freeze during the sales order import step if both a source file field and default value was mapped. Now, the import will complete and the mapped field will be used if a value exists in the file, otherwise the default value will be used.

    Shipping

    • When using the Package Shipment function in the Package Shipments window, kit items will be packaged rather than the components. This fixes an issue where the kit item and components would be packaged, resulting in the message "This shipment contains one or more items with shipped quantities greater than the quantity ordered.
    • Fix the error "Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record." that would occur when using the Packaging Shipment button in the Package Shipments window when the shipment was created from a Picklist containing kit components.
    • Fix "Object variable or With block variable not set" error that would occur when creating and packaging a shipment created from a Picklist containing kit components.

    Synchronization

    • ⭐ Add support for integrating Acctivate with QuickBooks Online Plus and Advanced plans in the US and non-US regions.
    • ⭐ In order to construct the recommended address format in QBO companies, the Company name field in QBO will sync to Acctivate's Company field and address line 1 if address line 1 in Acctivate matches the Company name. If the customer doesn't have a Company name defined, then the customer's Display name will be used as address line 1 if address line 1 in Acctivate matches the customer's Display name. If Address line 1 in Acctivate doesn't match the Company or Display name in QBO, then updates to the Company/Display name field in QBO will not be synchronized to Address line 1 in Acctivate. Edits to Address 1 in Acctivate will never sync back to QBO. The customer's street address 1 and 2 in QBO will by synchronized to address 2 and 3 in Acctivate (and updates in Acctivate will sync back to QBO with these mappings as well).
    • Fix "Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record." error that would occur during the payment portion of the QuickBooks sync.
    • Fix an issue that prevented changes to payments in QuickBooks Desktop from syncing back to Acctivate.

    User Interface

    • ⭐ Increase the height of the Sales Order and Purchase Order manager rows to match the height of the sales order and purchase order grid rows. The horizontal grid lines that separate rows have been removed as well.
    • Center various pop-up windows over the window it was opened from or over the main Acctivate window. This fixes an issue where a pop-up window may open on a different monitor in multi-monitor environments.

    Web Store

    • Add UpdatedDate and UpdatedBy fields to tbINVRegister to record the last updated date of an inventory session and the user who performed the update. A new field, LastINVUpdatedDate, was added to the ProductAvailabilityByTemplate and ProductKitSummary views. LastINVUpdateDate is the most recent updated date from unposted assembly components and inventory transfer sessions. The LastModifiedDate from ProductAvailabilityByTemplate is used to determine which products have been updated since the last web store sync. LastModifiedDate is the most recent of LastTransactionDate, LastVoidedDate, and LastINVUpdatedDate. These changes should result in a more accurate inventory availability export to web stores.
    • When the web store option "Provide confirmation before importing sales orders" is enabled, customer records will not be created until the related sales orders have actually been imported in. This fixes a bug where the customer would be created even if the import hasn't been confirmed.
    • Downgrade the WooCommerce error "woocommerce_rest_shop_order_invalid_id" from a 400 Bad Request to a logged warning. This error is probably due to the Web Order Number field on the Sales Order not corresponding to a WooCommerce Order ID.
    • When importing guest customers from a web store, the web order's Sold To Name will be used as the customer's Company Name, if provided. This fixes a bug where the Company Name in the Edit Customer window would always be set to the order's Customer ID.
    • Fix the error "The specified key 'customer_email' does not exist in the ExpandoObject" that would occur when running a Shopify sync.
    In This Article
    Back to top © 2023 Alterity, Inc. All rights reserved