Dynamics 365 Commerce

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

Sometimes the POS can have an active cart with no item lines or tender lines. When switching to offline, recalling orders or anything that requires the an empty cart, the POS should automatically void the "ghost" transaction.

Idea Proposal: Enhancing Purchase Agreement Selection in D365 F&O

Problem Statement: Customers need the ability to manually select purchase agreements for planned purchase orders during the firming process. Additionally, they require an extensibility point to customize the purchase agreement selection logic.

Solution Overview:

• Identify Relevant Code:Locate the code responsible for automatic purchase agreement selection during firming (e.g., within the PurchAgreementFirmingService class).
• Understand the existing logic that determines which agreement to select based on criteria such as vendor, item, and date.
• Create an Extension Point:Collaborate with the development team to introduce an extensibility point in the code.
• Consider the following options:Event Handler: Add an event handler before or after the assignment of the agreementId variable. This allows custom logic to execute during the firming process.
• Chain of Command (CoC): Extend the existing method using CoC to modify the agreement selection behavior.
• Custom Service: Develop a custom service that handles agreement selection and replaces the standard service.
• Customize Agreement Selection:Once the extensibility point is in place, developers can create custom logic:Manual Selection: Implement a user interface where users can manually choose the purchase agreement during firming, overriding the system’s automatic selection.
• Business Rules: Apply business rules (e.g., priority, preferred vendors) to determine the most suitable agreement.
• User Preferences: Allow users to set preferences for agreement selection.
• Testing and Validation:Rigorously test the customized agreement selection process to ensure accuracy and reliability.
• Validate the solution with real-world scenarios and user feedback.

By enhancing purchase agreement selection, we can empower D365 F&O users to tailor their experience and improve efficiency in procurement processes.

Currently, we can setup manager's override on all Line discount % givem by the cashiers even though their permission says they can give 10% discount as an example.

So, if the POS operations 301 is setup with managers override, if will ask for all Line discount % given by cashier.

We want Cashiers to be able to give the discount defined in the Users permissions but then anything above should ask for the manager's override.

In customer's business, we often need to apply discounts to fresh products near their expiry date.

These discounts are applied at the point of sale by overriding the total price for a specific quantity of a product.

However, the current price override operation in Dynamics 365 Commerce only allows us to override the unit price, not the total price for a specific quantity.

This behavior does not align with customer's business process and results in incorrect pricing at the point of sale.

We request a feature that allows the price override operation to apply to the total price of a specific quantity of a product, rather than the unit price.

This feature would greatly improve our pricing flexibility and accuracy at the point of sale.

Example:

If you are selling ginger for 9.95 a kilo, and customer is buying 400 grams, so that's going to be 3.98, so 50% discount on that would be 1.99, so the cashier tries to override the price in the cart to be 1.99, but when he does that, it's the unit's price that's what's overridden, so the price in the cart will be 0.796 which is 1.99*0.4, instead of being 1.99 directly. 

A common requirement among D365 Commerce customers is to alter the customer view to there need. Rarely all functionalities are used which leads to empty data in the column. There is currently no option to hide or configure the column display order which means that the user needs to scroll to the right to catch relevant information, or worse case might miss it.

Requirements:

1. Possible to hide columns
2. Possible to set the display order of the columns

Image sample (will be disappear 6 months after this post was created): https://ibb.co/0cNtDdX

We want Bing maps enabled for our ecommerce sites, but not in the POS. Currently the flag controls both.

Customer wants to use excel add in when he is looking for data entity to use to use DMF projects to import the data instead of the add in.

We checked the data entity the excel add-in uses RetailTmpBulkProductAttributeValueEntity and data management is set to no.

Can we change the behavior of this entity to be set to yes? Or add any other entity that supports DMF projects?

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.

The Document Routing Agent requires a manual refresh of it's Azure service token every 90 days to enable its connection to D365 F&O. This is regardless of if the DRA is run as an application or as a service.

If the DRA is ran as a service and Azure service token expires, it will continually attempt to connect to re-authenticate and generate endless files in the user's INetCache\IE folder. Consequently all extra space on the machine where the DRA is installed can and will be consumed if left unchecked.

Two possible solutions:

-Allow the Azure service token to be refreshed automatically or at least via script instead of manually through the application (preferred solution)

-Limit the DRA's attempts to re-authentication when the token is expired. If a manual refresh is required, the DRA shouldn't be attempting to connect endlessly.