microsoft / microsoft/Dynamics365Commerce.Solutions

CreateTenderRemovalTransactionClientRequestHandler Not Executing When "Cash Management" is Enabled

Open
#386 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
80
Forks
38
PR merge metrics
No merged PRs in 30d

Description

I have implemented a trigger in the Commerce SDK, but I am experiencing an issue where my custom POS request handler, CreateTenderRemovalTransactionClientRequestHandler, does not execute when the "Cash Management" feature is enabled in the POS Functionality Profile. some behavior for others like starting amount handler

Steps to Reproduce:
1.Implement the custom trigger in Commerce SDK.
2.Enable the "Cash Management" feature in the POS Functionality Profile.
3.Run 1070 & 1090
4.Do tender removal transaction on POS.

Expected Behavior:
The CreateTenderRemovalTransactionClientRequestHandler should execute as it normally does when the feature is disabled.

Observed Behavior:
The custom request handler is not executed

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Commerce SDK implementation of CreateTenderRemovalTransactionClientRequestHandler and reproduce the behavior with Cash Management enabled and disabled. Compare the handler's execution during the 1070, 1090, and tender removal steps; done means the custom request handler executes when Cash Management is enabled.

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
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.