Overview

 Contains all binary and X++ changes for the App Update 7.3.1 release.

To see the list of features included in this monthly update, see the "What's new or changed" topic found here:  Microsoft Dynamics 365 for Retail roadmap

Refer to the following details about the bug fixes included in this update.

Accessibility

Improvements have been made to the Narrator screen reading experience by adding more name and role values. Navigation now includes additional keyboard shortcuts and tooltips have been added to make elements more readable.

BI reporting

Fixed an issue with Retail Channel Performance Power BI content pack refresh caused by a missing TaxOverrideGroup column.

Call center

• When attempting to delete a call center sales order, the system would not allow the order to be deleted if a payment record existed on the order. A notification now explains why the order cannot be deleted if there are existing payments.
• The following upgrade scripts for the call center have been added to ensure complete data upgrade:
• preSyncUpdatePriceDiscTable
• preSyncUpdatePriceDiscAdmTrans
• preSyncUpdateMCRPriceDiscAdmTable
• preSyncUpdatePriceDiscAdmName
• preSyncUpdatePriceDiscAdmTransfer
• preSyncUpdateMCRPriceHistory
• preSyncUpdateRetailPricingSimulatorPriceDiscTable
• preSyncUpdatePriceDiscGroup
• preSyncUpdateMCRPriceDiscGroupCustomer
• preSyncUpdateMCRPriceDiscGroupItem
• When call center sales orders with credit card payments fail or are declined, the call center parameters Retry on Submit and Reauthorization Limit are acknowledged now. The system now recognizes the parameter settings and sets the payment status to declined after the maximum number of retries on the same card have been processed using the sales order submit function.
• Users are allowed to define email addresses for the main customer account, or through advanced set up one can define different email addresses by address/location. The call center fraud rules engine now checks email associated with both customer party and address/location records to attempt to find a match against fraud rules that are related to email addresses.
• Users are unable to change the prepay slider selection when entering a payment other than credit card. This meant that users cannot change the "prepay" flag from Yes to No for cash and check payments in call center payment entry for sales orders.

Accidental usage of setting prepay to No created a financial imbalance on orders that were paid by these methods because the system would not post these payments to the customer's account even though they were physically received.

If customer is going to send a check or pay cash later, a prepayment method of payment such as cash or check should not be used. A payment method set as a type Customer should be used to indicate future payment. The Prepay slider was intended for modification when paying by credit card, which meant that either the system would authorize and capture this information immediately or authorize up front and capture only at invoicing. Some businesses prefer to capture prepayment of credit cards up front before the product ships. The prepay slider was only intended to control the payment type and should not have been editable for other methods of payment because financial posting processes are not designed to capture/post payment at invoicing for any other method of payment but credit card when prepayment is set to No.

CDX and data management

• Commerce Data Exchange (CDX) job execution is more robust with new tables and columns. This hotfix alters the CDX jobs to ensure that tables that are not present in the offline or Channel database are skipped instead of blocked, as a result of an older version of POS being run at the headquarters.
• A Modern POS offline database can be associated to the Default channel database.
• Logic was improved so that job synchronization avoids skipping all records if any orphaned records exist. This will allow future synchronization jobs to continue without error or getting stuck in a pending state.

Extensibility

• Partners can now create and use their own TVPs by pre-pending the schema to the TVP name. Previously, the commerce runtime (CRT) schema would be automatically pre-pended to custom TVPs created in ext ended  schema. When calling the custom TVP, CRT looks for that TVP in CRT schema instead of ext schema, which resulted in SQL exception during runtime. Now partners can call their own TVPs from extension code. For example,["Your TVP NAME"].
• POS serial number input workflow has the overridable request for customers/partners to override and add custom validation logic. With this extension it’s possible to override the serial number input and validation workflow.
• The code will now query whether any extension can handle a custom payment operation request and then displays a dialog box based on the handler implemented in the extensions. If there is no handler, then POS will not display that particular operation button.

Financials & statement posting

• A new parameter has been introduced in Retail parameters called as "Disable counting required" that allows retail statements to post without having to enter the counted amount in HQ. This fix allows retailers to continue batch posting statements even when there are variances in the counted quantity. The posting process can continue and the variances can be reviewed after the posting process.
• It is now possible to do parallel calculation of the Retail statements.
• An update has been made so that statement posting is allowed with a retail kit if the components of the kit are batch controlled.

Inventory management

• The cross-dock date field on the purchase order is now populated with the ship date for the associated transfer orders instead of the transfer order creation date.

Merchandising

• It’s now possible to set the Vendor item number when creating a released product and access the External item description form for future updates of an item record.
• You can now add an additional set of product variants to an assortment that already has other variant combinations without losing previously added variants to the same assortment.
• Supplemental hierarchy no longer allows users to define values for additional product properties.

Pricing & discounts

• The user experience for advanced date validation for discounts has been improved.
• The price simulator now honors the coupon expiration date to calculate the final amount for a sales line.
• Fixed trade agreements generation using the Category price rules that uses the 'Fixed amount' setting as a price rule.
• Fixed an issue with activation of coupon codes.
• A new configuration has been added on the Retail parameters page named "Coupon code must be manually applied to return transactions". This is set to No by default, which means that the coupon codes will be applied automatically to the return transactions without receipts. However, if the retailer wants to stop this behavior they can set the configuration to Yes, which will force the cashier to manually add the coupon code.
• The retail pricing algorithm now honors the unit of measure conversions set up for the item. For example, if a trade agreement is available for the unit "ea" and the unit of measure conversion exists for the product as 1 box = 5 ea, then the price will be calculated automatically when the item is sold in Box unit.
• BundleID property has been added as a part of RetailTransactionDiscountLineEntity.

Order Management

• The header level discounts on call center sales orders will be evident when a sales order is retrieved in the point of sale.
• Multiple sales quotation lines can be deleted at the same time.

Store operations and POS

• Fixed an issue when selecting sign-in in POS.
• Info codes of type numeric now allow decimal inputs.
• Updated the logic around switching from offline to online so that open shift records are not created for already closed shifts.
• Improved the visual indicator when switching to offline mode.
• Fixed an issue so that the original delivery date of the order upon partial rejection of order on POS remains unchanged.
• Fixed filtering of products with attributes' value up to 1999 characters, which equal the field's length.
• Fixed aggregation of products on receipts.
• Decimal parts of the amount are no longer rounded off for customer account deposit transactions.
• Fixed the filter so that stores only see their counting journals data in reference to cycle counts.
• Fixed an issue with printing receipts in store when customer receipt option is set to Email.
• Fixed an issue with inventory look up for stores that have special characters in their names.
• Fixed an issue with loading the transaction page on mobile point-of-sale (phone layout).
• Fixed an issue with hidden customer attributes accidentally appearing on the POS.
• The screen layout and the language settings for a new cashier, using the extended log on to sign-in, is used instead of the settings for the cashier who previously locked the POS.
• Fixed an issue with manager override failing to recognize manager credentials using the extended logon feature.
• Fixed an issue if the quantity is zero. The system now checks the "Quantity becomes negative" flag to see if the value should be -1, instead of always defaulting to 1.
• POS in compact mode no longer throws application errors when rendering dialog boxes.
• Blank POS button titles will no longer be re-populated automatically.
• Fixed an issue with Show journal showing different times when using Advanced filter. These changes make the date from RetailTransactionTable.TransDate combined with TimeWhenTransClosed when you click the Advanced filter, so that it can be synced with ax.RetailTransactionTable.CreatedDateTime.
• Fixed Z report to only show the currency if it is used.
• You can now provide starting amounts for blind closed shifts while in non-drawer mode.
• Fixed an issue to make sure that the new issued credit memo can get registered in the system and is available for the future use.
• Tender denomination details can now be printed on receipts via custom POS reports using receipt extensibility.
• The return transaction date is now set as the current date of the return transaction and not the original date of the actual transaction.
• The POS transaction screen designer now allows users to define up to ten button grids.
• Fixed an issue with shift IDs showing as zero. The shift IDs now show the related shift's ID data on the Retail transactions page for the closed shift operation.