Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
Highly demanded request which any Retail product should be able to fulfill as a basic feature when doing stock count. Our customer is disappointed that they have to pay for change request because the system need to be customized to improve their work efficiency.
The workflow for key-in product number manually must be same as for scanning continuous items
The idea workflow would be:
1) Go to Stock count option at home screen
2) Click “Add” button to create new counting journal, system prompt for input product number to count
3) Key-in product number manually with assumed Default 1qty.
4) For the next item to enter, the 'Add product' dialog should remain open to key-in the next item.(same as for scanning items)
5) Once all items added, user clicks 'close' button on dialog, to indicate no more items to add.
Clicking “Add” button to key-in product number increases stock count processing time if there are 1000 items. And the same process continues across number of stores, which consumes time.
Clicking add 999 times is a painful and cause a chance of human error.
When compared to the existing workflow, the ideal workflow will be much more efficient without any drawbacks. It should definitely be implemented.
Important in several presale cases we are working on.
We have a number of Lead fields that need to be captured that are Lookups so this is a very important capability to enable embedding Marketing Forms in our website.
This is also pain point for our client in counting process. We have 2 options for input either scan or key-in product, however the behaviour of both input are not the same. System should keep it consistent, when scanning in user will be prompt for quantity and able to scan next product, but why when key-in need to click "+" button (Add next product) for EVERY SINGLE line !
Great idea Cristine
How is this even a thing?
This functionality was already included in previous versions.
I agree with the above limitations of the system, not all users should be able to see certain confidential data within general ledger, bank accounts etc.