microsoft / microsoft/Dynamics365Commerce.Solutions
ConcludeTransactionClientRequest auto logoff not getting triggered in 10.0.38. Was working in 10.0.35
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 80
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
Problem Statement: Has the framework of ConcludeTransactionClientRequest changed in v10.0.38 from what was in v10.0.35.
Problem Description:
V10.0.35:
On executing the ConcludeTransactionClientRequest in v10.0.35 it was found that Cashdrawer/Open, CashDrawer/IsOpen and logoff request runs after the ConcludeTransactionClientRequest has run successfully without separately executing it. Please check the “Pos with extension console V35.txt” in attachment for logs.
V10.0.38:
While in v10.0.38 it is seen that the ConcludeTransactionClientRequest after executing doesnot automatically tiggers the CashDrawer/IsOpen and logoff request. Please check the console logs in “Pos with extension console V38.txt” attached.
When executing base cash operation it was seen that after ConcludeTransactionClientRequest completed it run Cashdrawer/Open, CashDrawer/IsOpen and logoff request. Can be seen in console logs “Pos without extension console V38.txt”.
Questions:
- Were CashDrawer/IsOpen and logoff request requests added manually in the base Cash form after ConcludeTransactionClientRequest in V10.0.38?
- If this change was made in the framework of ConcludeTransactionClientRequest are there any released notes for this?
- At what version this change was made V36,V37,V38?
We added extra requests as below to achieve the same console logs as the base:
Please check the logs in file “POS with extension V38 with extra code.txt” attached.
Pos with extension console V35.txt
Pos with extension console V38.txt
POS with extension V38 with extra code.txt
Pos without extension console V38.txt
Thanks,
Deepak Tomar
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
Start with the ConcludeTransactionClientRequest flow and compare the attached POS extension logs for v10.0.35 and v10.0.38 with the base Cash operation log. Trace whether CashDrawer/Open, CashDrawer/IsOpen, and logoff are invoked automatically in each version. Done means identifying when the behavior changed and documenting whether the extra requests are required.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100