I am fairly new to working with Tax Connect and Avalara. While debugging a BPM conflict with Tax Connect, I turned on the Tax Connect Debug Mode and found that I was getting …xml.out xml files. When I opened one, I found that it was an Error return. Here is an example:
My question is how should Epicor be handling any error return from Tax Connect? Should this not display for the end-user in the Sales Order Entry screen? How would we go about capturing and displaying this error?
Thanks,
I know this is an old post but did you ever decide on a solution for handling error handling with Tax Connect? We have the same question.
You getting the error in a BPM, or just during regular use (in order entry, AR invoice, etc …)?
I’ve been working on a BPM to show a message to the users when Tax Connect Results are not equal to Success. Tried Method Directives and Data Directives many different ways and can’t get the Method Directive to fire but can get the Data Directive to work.
Problem with the Data Directive is it seems to prevent the Address Validation process from working after the message pops up. Thought maybe I was spinning my wheels and someone else had already done this.
Actually, after a bit more trial and error, I got it to work. Thank you, Calvin, for replying.
Hi Kara,
We are trying to do a similar thing at order entry. Display a message to the user if the address validation failed. Can you share how you set this up on your environment?
Thanks for help on this.
