-
Retail Cross docking orders - once created you are unable to edit
When goods on a purchase order is cross docked for delivery to stores, the user calculates the cross docking quantities and the orders are created. Once the Sales orders are created, there is no way to edit these cross-docked orders. This is an especially big issue, since the cross dock performs an on order reservation, and there is no other way to place a reservation against the inventory until the order is received into a DC. This is a disruption to the supply chain. If quantities on the Purchase order are changed, it is not possible to recalculate the allocation on the cross docked orders or when deleting a purchase order line, the cross docking is not updated.
-
Cannot modify Cross dock\Buyers Push once orders created from Purchase orders
If a Buyer's push or a retail cross dock is created and orders are created, the buyer's push and cross dock cannot be modified. This is an especially big issue, since the cross dock performs an on order reservation, and there is no other way to place a reservation against the inventory until the order is received into a DC. This is a disruption to the supply chain. When goods on a purchase order is cross docked for delivery to stores, the user calculates the cross docking quantities and the orders are created. Once the orders are created, there is no way to edit these cross-docked orders. If some of the quantities on the Purchase orders are changed , it is not possible to recalculate the allocation on the cross docked orders or when deleting a purchase order line, the cross docking is not updated -
MPOS Receipt: Credit Memo Number Scannable Bar Code
The receipt number and Customer Order is a scannable bar code, but the Credit memo is not on the Receipt and needs to be. The credit memo number sequence is usually pretty long and has to be keyed in by a user to be consumed in the POS. No credit memo bar code field is available in the receipt designer to bring in this number as a scannable barcode for users. Instead they have to key in a 10+ character number manually, this can lead to consuming the wrong credit memo or errors in finding the credit memo number. -
Retail Post Statements in Batch will not be picked up Statements in the batch task if transactions older than 30 days
When the store statement closing method is set to Date\Time and statements with Transaction date older than 30 days are scheduled to post statements in batch, the statements will not be added to the batch task. There is a limitation in the RetailStatementPostChecker class to check for Transaction dates older than 30 days. Customers who import retail transactions from legacy systems or statements with errors than need to be fixed, may need longer than 30 days to processes statements in batch. Imported statements may be too large to post manually so batch posting is needed. We would like to see a parameter that allows customer to set their own days to check when transactions should be selected to post statements in batch. -
POS Show Journal for Void Transaction item should be displayed with a strikethrough and should not display totals
When voiding with Void Transaction, the Header information shows as voided, but the lines do not show as voided. There is also a Total Amount. This is causing confusion in the Show Journal form. When using Void Transaction, this updates the EntryStatus to void in the RetailTransactionTable, but does not update the TransactionStatus in the RetailTransactionSalesTrans. The Suspended Transaction will show the items with a strickthrough when you use Void Suspended Transaction. POS Show Journal should be consistent with Sales transactions and Suspended transactions that have the entire transaction voiced. -
Set quantity resetting to 1 after scanning a barcode with OPOS driver
There is an option to set quantity by using “set quantity” button on the mpos but in retail sector, every operational effort is not acceptable and it takes time to use all the time the “set quantity” button. When you try to set quantity by using the numpad, enter in the quantity and right after click the "*" button, and then scan the barcode with opos, the product’s quantity is being added as just 1 whatever you enter in to the numpad as quantity. In addition, when I enter in the barcode on the numpad manually, it works. But with opos scan, it doesn't work. You should be able to set a quantity, scan a barcode and the quantity should stay at the entered quantity and not reset to 1. -
Credit Management holds for Sales orders include Call Center and Omni Channel orders
Per the document below, Call Center and Omni Channel Sales Orders will not be included in the Credit Management hold list. Is there a plan to add Call Center sales orders to the hold list? https://docs.microsoft.com/en-us/dynamics365/finance/accounts-receivable/cm-sales-order-credit-holds#free-text-invoices-orders-and-project-invoice-support-in-credit-management Section: Free text invoices, orders, and project invoice support in Credit management Credit management can only be used currently for sales orders. Free text invoices, point of sales orders and call center orders will use the temporary credit limits and insurance/guarantees that you add to adjust the credit limit. They will not use the blocking rules and they will not be placed in the hold list if there is an issue with the credit limit. There is no support for project invoices in credit management. -
Commerce Retail Sales should be supported by Advanced Credit Management
We would like to see Commerce orders be supported by Credit Management as there has been a few customer asks for this.
Commerce orders does not support Credit Management and Credit Management Blocking Rules. This should not block the Customer Credit Limit Check.
Below is the documentation and section of the document advising that Commerce is not supported:
A bug (572582) was created because Commerce orders were not bypassing the Credit Management Blocking Rules and we were seeing errors when posting Commerce Statements (error: While processing aggregation state Sales order is invoiced for this aggregation. transaction state Customer order invoiced, the invoice ID was empty after invoicing for this aggregation XXXXX) and Dead Lock errors as an example.
This fix was implemented in 10.0.22. After upgrades to 10.0.22, Class RetailCreditManExcludesSalesOrderToggle sets SalesTable.CreditManExcludeSalesOrder to "Yes" for Commerce orders (Point of Sale, Online and Call Center).
Free text invoices, orders, and project invoice support in Credit management
Credit management can only be used currently for sales orders. Free text invoices, point of sales orders and call center orders will use the temporary credit limits and insurance/guarantees that you add to adjust the credit limit. They will not use the blocking rules and they will not be placed in the hold list if there is an issue with the credit limit.
There is no support for project invoices in credit management.
We have seen customers who have added the Exclude from credit management flag to the Sales order form and set the flag to "No". The ask was to have a parameter that will turn this toggle off.
After investigating the feature and the customer scenarios, having this feature enabled should not be blocking the customer credit limit check. The bug was intended to disable advanced credit management for Commerce orders.
Disabling the feature will create more problems than fix for other scenarios such as the one in the bug.
See ideas asking for a parameter to turn the toggle off
https://experience.dynamics.com/ideas/idea/?ideaid=c1f685b9-4058-ec11-a3ee-0003ff45e3f6
https://experience.dynamics.com/ideas/idea/?ideaid=c6803f0a-cd59-ec11-a3ee-0003ff45e3f6
-
Prevent deletion of payment connector when there are orders associated
If a payment connector is configured and sales orders are created with credit cards authorized and for some reason the payment service is removed from the online store, accounts receivables payment processing or the hardware profile, the sales order will not be able to be processed because you will receive an error message:
“A merchant account for Service account ID %1 was not found. Reestablish merchant account information for the payment service account.”
Due to the complexity of the behavior change and risk of regressions, this would be a feature request and I have created this Product Suggestion.
-
Store Sales report displays no data when Category is populated because RetailTransactionSalesTrans is not populated when transaction is created for Online sales or Customer order sales
After a eCommerce order or a Customer order is placed in POS, when you go to Retail and Commerce > Inquiries and Reposts > Store sales, populate a date range and mark all transactions, the Category has no data.
Cash and Carry transactions for the same item does have a Category populated. This is true even when you added the item to the cart by navigating to the navigation hierarchy and add the item.
Because the Category is not populated, you cannot filter the report on Category.
You’re offline. This is a read only version of the page.
