Dynamics 365 Commerce

Today when a receipt is printed out, then code is run to query and create the receipts based on a setup. If the receipt setup is changed then the original receipt will not be shown but the receipt based on the new setup.

Would it be possible to save the receipt information as JSON document to keep a copy of the receipt that is printed and thereby avoid re-creating the same receipt each time it is displayed or re-printed.

This could save some RetailServer - CPU time in the long run although it will use some extra disc space to store the information..

Not sure how this will fit with future plans on archiving old Retail transaction data.

After trying to use the attributes to extend some products data, we gave up due to slow performance in POS. The attribute code in Retailserver was/is complex and slow.

As SQL Server has some great support for querying and using JSON data, would it be possible to handle the attribute data or extended data for products as JSON documents?

So when a POS solution needs to extend the product information a JSON document could be a field in the product table. That JSON information could then be handeld by extension code to display it or use in it any extension logic.

This could open up a very flexible and fast way of extending product information were no new ext.InventTable is needed and replication does not need to be extended as the extended information is all in one JSON document column.

Same thing could be done around customers if needed..

The performance should be much faster than the current attribute solution.

There is a setting "Allow manual card numbers" on the card setup that will open the card number field for all the issue, redeem and balance check operations on the POS. Ideally, we'd be able to isolate these operations and only enable manual entry on redemptions and balance check, but not on issue. This would force store staff to use the MSR or scanner to issue the card (and prevent bad data), but would still allow them to redeem against the card later if the MSR/scanner is no longer able to read the card after some wear and tear.

Hi,

I saw in threshold discount when using calculation type Discount Lines just apply only one tier.

For Eg :

Bill total over 1000 -usd from list A get free 1 item from list B

Bill total over 2000 -usd from list A get free 2 item from list C

With this Eg, we need created 2 threshold discount ID, it's take time and inconsequential.

it's great to support multi tiers. Thanks

In the Lease-to-own industry, Retail and E-commerce customer transactions are usually Tax exempt because of State Stipulations. In my customer's case, they are planning to Incorporate Progressive Lease-to-own payment method on their website and there is no Out-of-Box way for a Transaction to be marked as Tax-exempt upon the selection of a Payment Method.

This seems to be a Gap in the functionality. It would be great if this could be built into the product to cover the greater use case for the Lease-to-own industry.

Thanks

Actual Result:  The changed value should be reflecting on the order event page, but no data is available on this page.

Expected Result: The transactions for which the values have been changed should reflect on the order event page.

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.

At the moment the RSAT is hindered by the lack of ability to note values throughout the process. Primarily this makes any sort of testing through saves/edits of customer orders and quotes less than ideal. We either A. Create the order, use HQ to try to find the order and then go back to the POS, Or we need to pre-create the order numbers in HQ so we can note the generated orders before testing. I've not been able to come up with a better solution thus far.

When we create a product number sequence currently system will not allow category-specific.

Ideally when we have a category breakup example:

Electronics

Laptop

Mobile

it will be good if we can assign different number sequences for laptops and mobile, which will help to easily identify the category

Currently we only have access to column style List. We're trying to create a dialog that matches the look and feel of other dialogs in the system (Sales Rep). We have the ShowListInputDialogClientRequest option, but it allows no flexibility in the behavior of the dialog. such as pagination or adding search functionality. The ability to create a card style list would be appreciated to allow for matching the look and feel of the rest of the system.