CMS 16.2 syntax error

[justcatplease]

In both report designer and custom report options, I'm getting a syntax error (despite double checking the query). I was told this was a bug and there was a patch. My vendor says there isn't. Does anyone know of this issue?

 

[Stinney]

Are you saying that all reports in designer and custom reports are giving you a syntax error or just a specific report?

What does the error say?

Does it give this error for every user?

Can you post the query?

- Stinney

I love learning and passing on knowledge. "Because knowing is half the battle".... GI JOOOOOE!

 

[justcatplease]

The query was: sum(TI_AUXTIME10)

 

[Stinney]

So your select statement is just sum(TI_AUXTIME10)?

What's in your WHERE clause?

- Stinney

I love learning and passing on knowledge. "Because knowing is half the battle".... GI JOOOOOE!

 

[justcatplease]

No that wasn't all there was to it - but that was the database item in question that it was getting the syntax error. Since it's actually IN the database, it shouldn't be getting an error. From what someone told me, this is a known bug in my version of CMS (16.2), but I need the patch and my vendor doesn't have it.

 

[Stinney]

Without more information I'm going to go out on a limb and say your issue is in your where clause.

I'm surmising that you took an agent report and are looking at multiple agents or days and want to summarize them.

Your SUM of the AUX time will require you to set up a group by in your where clause for data items that are not calculated to have a sum or average, such as a date, time and agent ID.

- Stinney

I love learning and passing on knowledge. "Because knowing is half the battle".... GI JOOOOOE!

 

[Stinney]

Can you provide the list of what's in your select statement and where clause?

- Stinney

I love learning and passing on knowledge. "Because knowing is half the battle".... GI JOOOOOE!

 

[justcatplease]

Actually, I'm working with someone who does custom reports professionally, and knows there's a bug in this version. So I'm not looking for help in correcting the query, because we tried it in both report designer and custom and we know it's correct. I'm really just looking for someone who has run across this bug before and knows the fix. Thank you.

 

[Stinney]

If there is a known issue and patch then it should be on support.avaya.com

- Stinney

I love learning and passing on knowledge. "Because knowing is half the battle".... GI JOOOOOE!

 

[Stinney]

BTW, running a query in designer vs custom doesn't do anything different.

- Stinney

I love learning and passing on knowledge. "Because knowing is half the battle".... GI JOOOOOE!

 

[justcatplease]

Yeah we thought it was odd, which is why we decided to try it in custom reports after it failed in report designer.

 

[Stinney]

I'm working off of 16.1, but I'd like to see if I get the same erorr. Is there anyway you can export the report and put it on an ftp location I can grab it from?

- Stinney

I love learning and passing on knowledge. "Because knowing is half the battle".... GI JOOOOOE!