By using this website, you agree to our Terms of Use (click here)
So far, this is the only bug that we've run into with AugSQL and, at this point, we haven't been able to reproduce it in a local environment. We've only heard of it happening in a couple of Acumatica SaaS environments.
Here's an example from an actual AugSQL User.
They can successfully run the following SQL Code without any problems:
SELECT * FROM CustomerClass
But, when they try to add a WHERE clause like this:
SELECT * FROM CustomerClass WHERE CompanyID=2
They get this error message
ErrorCode: 406.
For this particular AugSQL User, they get the error message in Acumatica Version 24.105.0036, but they don't get the error (running the same SQL code) in Acumatica Version 23.207.0025.
But we couldn't reproduce the error in a local Acumatica 24.105.0036 environment.
So, we're not sure at this point if it's an Acumatica Version problem or a SQL Version problem.
If you get the ErrorCode: 406. error, please reply to this Discussion Topic with both the Acumatica Version that you're running (ie. 24.105.0036) and the SQL Version that you're running. You can find the SQL Version that you're running by running the following SQL command:
SELECT @@Version 'SQL Version'
You can simply copy and paste the gigantic string that you see and reply to this Discussion Topic with it. It will be something like this:
Microsoft SQL Server 2019 (RTM-GDR) (KB5040986) - 15.0.2116.2 (X64) Jul 2 2024 17:41:57 Copyright (C) 2019 Microsoft Corporation Developer Edition (64-bit) on Windows 10 Pro 10.0 <X64> (Build 19045: )
The good news is that:
1. So far, this is the only AugSQL bug that we've run into.
2. There is a workaround!
The workaround is to add the TOP command. If you want to return all records, just pick a really big number that will be larger than the number of records returned.
Something like this:
SELECT TOP(999999) * FROM CustomerClass WHERE CompanyID=2