Dynamics 365 Commerce

We are importing category/Product images for which the image is uploaded to a folder in Azure blob storage.

Currently we are unable to setup the Storage account --> Blob container --> Public read access = 'Off' to have private access. instead of "Blob" i.e., Public access and successfully import an image from Azure storage.

If this is the case, if we open a product with an image in D365FO (within the browser somewhere out in the world) it will then be able to connect media URL by private network / endpoint.

Which might raise an alert regarding the image security for the customer.

In my opinion it will be possible for everyone to read the blob data in this container if we change the access level to “Blob (anonymous read access for blobs only)”.

It will be good to have the option to copy the button properties of an existing button while creating a new one. An option to define the button color and appearance properties at a grid level can really help configure buttons fast.

We should be able to choose the color of the button on a button grid by entering either RGB or HEX codes. We can only see the RBG codes only once the color is set on the button properties window.

With the current setup, it is difficult to choose a color for multiple buttons. If you are adding a new button to an existing grid and don't really know what is the color of the current buttons, we have to waste a lot of time doing trial and error methods until we get the exact match.

In the Price simulator you have the possibility to use the field "Channel Date and time". This date will be used to find prices on a specific date.

It would be great if there is a possibility to make this field (and functionality) also available in All customers and in All sales orders.

Because we have customers who don't accept a price increase right from the start and therefore it will help us if we can insert a date on the customer (and also to be flexible on the sales order) and the sales prices will be found due to this date.

Example: we have a price increase which is valid from 01.07.2023. The customer who doesn't accept the price increase for this date (he accepts the increase only a few months later), will get in All customers the "Channel Date" 30.06.2023. So the system finds the old prices which are valid before the price increase.

I believe the “Improve discount computation performance by using flattened discount tables” feature needs to be reviewed. It creates a batch job for each variant when created. This does not suit our business needs as each product we produce can have many different sizes and colours. For example one product could have up to 200 variants and if we create 50 products as we have purchase or created a new range of product it will create 1000's of batch jobs. Which it did in production and overloaded our batch servers.

A common scenario for e-coms and retailers is to start and/or end a campaign at a specific time, e.g. "Buy product X at 50% discount as long as there are stock available".

D365 Commerce supports configuration of "Effective date" and "Exparation date", but nothing defining a particular start and/or end time. There is a the concept of "Date validation period", but that does not meet the requirement.

Idea:

1. Implement the possibility to define "Start time" together with "Effective date"
2. Implement the possibility to define "End time" together with "Expiration date"

Customers would want to discover a product based on multiple factors like category, brands, etc. While this can be achieved using navigation hierarchy by creating 1st level node named "brand" and listing all the brands under it, it requires a lot of manual work. In most cases, the brand is listed as an attribute, and maintaining the same as product category assignment requires manual work.

Like other CMS, it will be good to have the option to create a Product List Page based on an attribute (that is PLP for each brand) which can be addressed using a direct URL. Automatically generating a navigation menu-like structure will make life a lot easier for content managers.

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?

At a client a Commerce product hierachy has been build to easily set new product information from one base setup.

The standard is already providing a lot of options but it would be nice to also have the Financial dimensions(DefaultDimensions) available as legal entity specific values.

Path to the hierarchy: Retail and Commerce > Products and categories > Commerce product hierarchy

Recently, Microsoft added a new Retail device type was added. The Store Commerce App. When users in D365 F&SC go to the 'Devices' form and add a new record they need to select what device type the device record is. ModernPOS, CloudPos, StoreCommerce, ect.

The only way to add the new drop-down option 'Store Commerce' is to go to the Commerce Parameters form, and then click on the 'initialize' button on the 'general' tab. While this work, pushing this button in production is a high impact. It creates seed data, if it doesn't exist. If a client removed any of this seed data in their system, this button would re-create this un-needed data in production, along with inserting the new 'store commerce' record into the RetailDeviceTypes table.

There exists a RetailDeviceTypes form that does allow users to create and delete records. However, whenever a new record is created, the 'Type' field is not shown. If you add it with personalization, the field is un-editable.

Suggestion: Allow the 'Type' field on the RetailDeviceTypes form to be editable so that a user can manually add the 'Store Commerce' record, instead of letting the 'initialize' button create it, along with potentially other records that they do not want.