We are using this tax engine on our sandbox and production environments. Now we are facing an issue where posting a packing slip throws the error /Posting Exception has been thrown by the target of an invocation/. After extensive testing, we realized that we only get this error on the sandbox environment when the advanced tax engine has been enabled. On our local devboxes, where the tax engine is disabled, we don't get this error. Since the error gives no more details, we don't know exactly where in the code this exception is thrown, and how to debug it. And since we don't get the error on our devbox, we cannot reproduce this issue locally.
Anyone have an idea if we can enable the tax engine locally on the devbox, so we can debug this issue? Or any other tips on how to debug this?
Actually, this is a big pain. It is not possible to enable the tax calculation service on a local Dev VM or cloud hosted Tier-1 environment. We faced an issue with one of our ISV solutions when Microsoft introduced a new implementation to handle purchase order invoices. This was not noticeable in a Tier-1 environment. We had to guess what could go wrong and deployed code to test the behavior in a Tier-2 environment. When the test was not successful, we had to do analysis again.
If you don't have customizations, I would suggest logging an incident for Microsoft Support. For our issue, they were able to know where it was failing and could also disable a flight in a customer environment, so they could continue working with the application and we got time to provide a proper fix.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
133
Share
Report
All responses (
Answers (
