microsoft / microsoft/Dynamics365Commerce.Solutions
Preselected dimensions are ignored during ProductSearch/Scan in all inventory views
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 80
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
Discussed in https://github.com/microsoft/Dynamics365Commerce.Solutions/discussions/311
Originally posted by alexanderkurilenko July 10, 2024
Dear experts,
Our customer has a customization to search/scan product by custom identificator; The response of this custom Search/Scan is product master with preselected color dimension; (So cashiers need to select only size dimension to select a variant); This logic works as expected from the cartView(salesFlow) but not in inventory (e.g. StockCount or InventoryAdj);
- Open any inventory view
- Search/Scan for the product (Response is Product master color dimension populated)
- Prepopulated dimension (color) is ignored (during variant selection); Undefined value is passed;
Our customer extremely wants Scan to work the same way in all views in POS; Is it possible to add preselected dimensions to the call
var selectProductVariantClientRequest = new Commerce.Products.SelectProductVariantClientRequest(product, undefined, editResult.correlationId, editResult.title); Replace undefined <-> Populated dimensions;
Many thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace SelectProductVariantClientRequest from the inventory views and compare it with the cartView salesFlow path. Check how the populated product dimensions are handled during ProductSearch/Scan; done when the preselected color is passed into variant selection instead of undefined and inventory scanning behaves like the cart flow.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100