Dynamics 365 Commerce

The Idea is while excluding products or categories inside the assortments it should be removed also from the retails offline database specifically from ECORESPRODUCT table instead of removing it from the view level only.

We used MPOS with a Windows Kiosk account locked down to just run MPOS. When we upgraded to Store Commerce, we lost the option to add the Store Commerce App in the Windows Kiosk mode drop down set up. Can we get this re-added so we can move away from everyone having to log into Windows with their AAD account? We manage 850 registers.

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.

Customer is able to apply a price override in a call center order, and they are using the override permissions and order price control settings, however, the price override is not tracked in any reports. they do not see it in order events, marked as a price override in customer service or in the price override report. so please consider to activate this behavior so the customers can track easily the price override on the call center

To better server companies in the industry with a longer sales cycle, the ability to fully service the customer from the POS is essential.

As of current functionality, we can create the quotation and confirm the quotation into a sales order. However, there is no function to either cancel or lose a quotation.

To fully flesh out the solution, parameters could be added for default reason code when the quotation cancelation/loss call is sent to the back office for tracking purposes.

Hi,

We got so many comments from the users that the text and some buttons in MPOS really could be bigger, to help the users to work with the product.

Small text and buttons lead to error when clicking and a hard time reading the instructions in ex pop ups.

The buttons in the left menu (transaction view, home view and products) is most critical since it is very small.

Also over all, all text could preferably be bigger and alsomaybe bold or better applied for the eye to catch.

Is this a possible thing for you to look into?

As a partner, allowing read access to the customer environment Channel databases would enable more rapid support for the customer problem scenarios in multiple levels:

- validate Channel database SQL schema regarding new or deleted fields

- validate data problem scenarios when data on POS does not seem to reflect the correct data structures

- validate download & upload issues

- valildate missing or invalid data

- validate P-job runs

- validate individual job runs

- validate POS generated data

- validate transactions, lockdowns and shift issues

And most of all, allowing accesss would increase the issue solving productivity, and decrease the throughput of support issues and the total costs of Microsoft and partner support, since we could quickly investigate ChannelDB issues without first contacting Microsoft. 

Regarding minor issues, ticket-by-ticket-based ChannelDB problem solving involving MS support is highly inefficient action and prevents us from serving and supporting our customer base properly. 

When using EntraId single signon for Store Commerce in combination with shared installation (Multi user, --UseCommonApplicationData) there are two main challenges we need to handle:

- Adding users to the local security group RetailChannelUsers is a challenge when installing in userspace since we cannot easily add all users that need to use the computer to that local security group. Using group policy is not always possible due to security setup so a way to add users centrally in HQ and allow for replication to the local group or similar using Entra ID groups would be preferred.

- Automatically killing or otherwise handling the requirement to have only one instance of the Store Commerce application running is a challenge since users are not always clear that they need to shut down the application when locking the screen temporarily. Either allowing users to terminate the running instance or otherwise allowing multiple users to use the same device using entraid without needing to reboot the computer would be needed.

While creating a customer in store commerce app these constraints needs to be added:

Phone numbers: It allows adding characters and special characters -> Customers wants the phone number field to only add numbers.

Customer Name: It allows adding numbers and special characters -> Customer wants the name to only allow characters.

Customer Email: It allows adding anything if it has these two sympols "@", "." -> Customer wants it to validate if the email is correct

Currently To request a full or partial return of a sales order from a B2B and B2C e-commerce site, it is necessary to enable a Call Center channel within the headquarters to process returns. In electronic commerce, there is no direct possibility of issuing a return; The process must be managed through a Call Center, but it will be a better option to perform this directly from the B2B and B2C e-commerce sites as per some customers' process does not match the call center return process.