Dynamics 365 Commerce

Steps to reproduce:

1) Open any inventory operation

2) Scan product (add new line)

3) Scan result is Product Master with pre-selected Color dimension

4) Pre selected Color dimension is ignored in variant selection dialog

Method:

Pos.Core.js

GetInventoryDocumentProductWithLocationAndQuantityClientRequestHandler.prototype._getVariantAsync

 var selectProductVariantClientRequest = new Commerce.Products.SelectProductVariantClientRequest(product, undefined, editResult.correlationId, editResult.title);

Undefined value is passed as second parameter to variant selection dialog which ignoring the already selected dimension;

Idea:

To pass selected deimensions instead of undefined value

It is possible to select a counting reason code on inventory adjustment journals in D365 F&O. However, if I perform an inventory adjustment journal from the POS, there is no possibility to select a counting reason code. There is not functionality in the POS for me to add a reason code. It needs to be added from D365 F&O.

We believe this should be possible in POS, as it is possible in D365 F&O. We have tried to challenge Microsoft on this without success. Please vote for this idea, thank you!

As a developers we need a possibility to modify the Content-Security-Policies to handle No Card Present payment provider scenarios for Hybrid Store Commerce Application.

Without this it is not possible to open an iframe from payment provider.

Similiar functionality already exists for e-Commerce web application.

When issuing a pre-printed manual gift-cards in POS, there is no validation on gift card numbers.

Instead of scanning the preprinted gift cards, cashiers sometimes manually enter a different number, for ex the amount, leading this to be the gift card number, and the customer leaving the store with a gift card with no value.

Adding a validation feature for manual gift cards in POS systems would significantly benefit retail operations by reducing errors, streamlining transactions, and enhancing user experience.

Recommend this feature for future development consideration.

Proposed Solution:

Integrate a feature to validate the sequence and format of gift card numbers upon issuance and use.

This would:

1. Ensure only correctly formatted numbers are accepted.
2. Reduce errors and enhance transaction efficiency.
3. Improve overall customer satisfaction by ensuring gift card validity and accuracy.

When importing the 'Assortment Product Lines' entity without filling in the 'LINENUMBER' field, the import outcome consistently results in an error. This hinders different users from working simultaneously on the same assortment locally. The idea is to simply disregard this field so that assortment updates can be performed by adding product lines without taking into account the line number in the local file, while still respecting the products that are already included in the assortment in the system.

Currently, in order to update assortment product lines, it is required to always view the last line in the assortment beforehand to insert the subsequent one into the local file. This practice impedes different users from working locally on the same assortment and slows down the assortment update process.

We propose enhancing the SalesOrders API in Dynamics 365 Commerce to support warranty items for e-commerce. Currently, warranty transactions via API do not register in the RetailWarrantyTransactionSales table. This enhancement would align API functionality with standard behavior

If there has only been a login on a store's POS, a transactional statement is created for the store. This statement is empty, and the posting of statements always show 'error' if an empty statement is included in the posting process. These empty statements must be manually deleted, and shouldn't be created at all.

There is a need for smart rounding functionality when adjusting prices through 'Margin Component Price Adjustment' for at least 2 reasons:

• The "Get active price" data entity holds both ordinary prices and alternative prices, where 'alternative price' is populated by the result of the 'Margin Component Price Adjustment' functionality. If ordinary prices (i.e. trade agreements) are rounded off, alternative prices should also be rounded off.
• 'Margin Component Price Adjustment' can only be applied with 'Percentage' calculations. Calculating an adjusted price with a percentage will always create decimals. External sales prices with random decimals is not something retailers (or any business) can work with. Calculationg with 'Amount' is a work around on individual prices. But when calculating price adjustments on multiple (hundreds or thousands) of SKU's, this option is not feasible in the same way.

For retailers to work with 'Margin Component Price Adjustment' as a tool for campaigns, smart rounding is essential.

Customer is using "Replace alternative item defaults on sales lines" feature which is working fine for HQ. 

However, they also want to implement such a feature to work with retail Ecommerce B2B website, not only SCM.

The scenario is that B2B customers buy spare parts or items through the website and due to huge number of parts available sometimes they're not available or there's a replacement. 

If the order is through HQ and the feature is in use, it works fine and we can automatically replace the item if there's an alternative setup for it.

However, if the order is created from the B2B website, the CST doesn't get a notification or a prompt that this item isn't available, or if there's a replacement for it. This has to be done manually from HQ and due to that, sometimes the replacement they get is a complete different item, or a much more expensive item.

So, if we can implement that the same feature for Retail Ecommerce B2B websites that would be great as many business will rely on such feature especially for selling spare parts that has many alternatives.

With self-checkout being all the rage, many retailers with loyalty programs will want to make it simpler for a customer checking themselves out to add their loyalty information to a transaction.

With current functionality, the customer would need to add themselves to the transaction, and remember to do so. The only standard function that could be done is an info code that prompts the customer to add themselves.

A more streamlined approach to this would be to allow an operation to be triggered from an info code subcode (where we can currently trigger another info code or a product). This would allow the following scenario:

• Info code prompt: Are you a loyalty customer?
• Subcode 1 = Yes, trigger function = Operation, Operation = Add customer

Many other possibilities are opened with this functionality, but from an SCO perspective this will be extremely helpful to have customer-prompted operations.