Why can't I add a column to a freehand SQL statement?

[nscheaffer]

The re-introduction of freehand SQL is great and opens up a lot of possibilities. We are on BOE 4.1 SP06 Patch 4.1.

I have run into a situation that seems like a bug, but maybe I am doing something wrong. Once I run a freehand SQL query I am not able to adjust the columns that are returned. I can change the criteria in the where clause, but I cannot add a column.

We have a simple Calendar table in a SQL Server 2014 database that contains various data points about each date going quite a few years into both the past and the future.

When I drop that into a new freehand SQL query...

Everything works as expected. Here is a sample of the first few rows...

Now I want to add another column, DW...

I do not get any errors when I run the query. The new column "DW" shows up in the Available Objects pane. However, you can see the issue starting to appear in that the new column is not in the sample data in the grid on the right.

When I try to add "DW" to my table I get two errors...

1. The report cannot be generated. Please contact your administrator.

2. Unable to get the first page of the current report. Check the validity of your report. (ERR WIJ 20003).

The only way I have found around this issue is to create a new freehand SQL query and rebuild the table in my report based on that new query.

Any thoughts?

Thanks for your help,

Noel

[former_member185603 · Accepted solution]

Looks like your issue is known issue with your version. Check this KB

2191510 - Errors appear in Web Intelligence documents based on Free-Hand SQL after conversion from Desktop Intelligence

[nscheaffer · Accepted solution]

Thank you for tracking that down for me.

Noel