Share
Report
84Hello Experts,
I have extended the Sales Document Type enum by adding a new value, Proforma Document (Value: 50XXX).
I now want the Tax Engine to calculate tax for this new document type as well.
What I have tried
1. Adding the new document type as a constant in the Use Case Condition
I added the new document type as a constant in the Use Case Condition, but the use case is not executed.
2. Using a Tax Attribute
I then created a new Tax Attribute based on the Sales Document Type, mapped it to the Sales Line, and used that attribute in the Use Case Condition.
However, this results in the error shown below.
Investigation
From the code, I found that Codeunit 20293 "Use Case Execution" acts as the gatekeeper for use case execution.
- Extension:
Microsoft_Tax Engine_27.8.50894.0.app - Codeunit:
20293 "Use Case Execution" - Procedure:
ExecuteUseCase()
The CanExecuteUseCase procedure evaluates all use case conditions before executing the use case. Therefore, the condition for Sales Document Type must evaluate to true for my new enum value.
Has anyone implemented a similar scenario or knows the correct approach to support an extended Sales Document Type in Tax Engine use case conditions?
Any guidance or recommended setup would be appreciated.
All responses (
Answers (
