V10.1 bug in calculated column

nhofkes

I believe there may be a bug in the feature to add a Dynamically Calculated Column. Only the type of the calculation result can be selected/added, not the column name or the calculation. See screenshot below; the first and second field of the this form are disabled.

Steps to reproduce this: Open any query, select ‘Displayed columns’ from its properties, click ‘Add Calculation’.

I tried this both with normal queries and with queries that use an EXEC_SP or EXEC_SQL statement, results are the same.

aware_support3

nhofkes

Thanks we are looking into this.

aware_admin

In our tests in normal queries the fields are enabled. The fields should be disabled for queries implemented as stored procedures or SQL. So everything works as expected.

Could you please double check?

nhofkes

aware_admin I did check for a normal query and had the same result. And as for queries implemented by stored procedure or SQL: I understand that the calculation field is disabled, but I would think that it’s still necessary to provide the column name? How does the AIM server otherwise connect the result from the SP / SQL statement to the attributes displayed in the query? It’s possible to provide the label, but I think that is only the name used for the query header and often not equal to the underlying field name. I tried various combinations but could not get the calculated field displayed in the grid.

aware_admin

We cannot reproduce the problem with normal queries - perhaps you could create a video describing what you are doing?

nhofkes

I did some further testing and found the following.

When I take a query that has always been a normal query, I can add a calculated column with all fields enabled, so all good.
When I take a query that was previously implemented by a SQL statement but now changed back to a normal query that uses the FIND question, it does not work: in this case when adding a calculated column the column name and calculation fields are disabled, as described earlier.

Therefore, it seems that the status of the query is not reset when it is changed from a SQL query to a regular FIND query. The same happens if a EXEC_SP query is changed into a regular query.

Steps to reproduce:

Create a query implemented by EXEC_SQL or EXEC_SP
Make it a normal query by changing the query text to ‘FIND ALL BO’ or something like that.
Try to add a calculated column

Last but not least, I still have the question about calculated fields when using a SQL/SP query. The form in the configuration tool says:

“If the query is implemented by a stored procedure or raw SQL, you need to provide calculation type only, as the rest will be determined by the SQL (in this case the calculation is performed by the stored procedure or SQL)”

How does this work, what field name should be used in the SP or SELECT statement to get the result in the dynamic column?

nhofkes

This is fixed in the current build. Note that if the type of an existing query is changed from SQL SELECT or EXEC_SP to regular FIND or vice versa, the query must first be closed and then reopened in order to have the Configuration Tool recognize the type and display the correct settings.