I am verifying if our current Epicor version 10.2.600.9 is going to work once Avalara switch on March 31, 2022.
I was given a test user acct and key from Avalara however I get a user or acct cannot be authenticated when testing the connection. Anyone been able to successfully test the connection from 10.2.600?
If so, make sure that the company configuration settings are set up to connect to the sandbox avalara environment. Just below that is where you put in the test user and what not.
@kfierce We just received our information for testing in their sandbox. One of our network administrators verified that we have TLS 1.2 but we still want to test in the sandbox. I’ll update how it goes when I know more.
@utaylor we received a username, password, account ID and a License Key from Avalara. Did you use the Account ID and License Key for Account User Name and Key/Password?
This is exactly how we have ours set up. We have an open case with Avalara for getting the User Name and Password so I’ll reply to them on that ticket.
@utaylor - if I read the email correctly if you don’t have an active sandbox you could request access to Avalara’s universal sandbox to complete the connection test. It specifically says no transaction testing just connectivity. Right now I can’t even get connected without getting an error.
@utaylor@kfierce This is my underdstanding also. We don’t have a separate sandbox because it’s so costly. But Avalara has set up a sandbox just for testing to ensure you can connect.
Avalara will disable 1.0 and 1.1 but only for their REST V2 API, all versions up to Kinetic 2021.2 are using SOAP, so those will remain unaffected for now.