Row missing from Results set returned from SQL Query

[Former Member]

I've made a change to a Query Template adding an extra column to a Select; this works and returns the required data. This Query Template is used in an SQLQuery in a Business Logic Transaction. However, since my change to the Query Template I can no longer see the Rows beneath Results/Rowsets/Rowset under the SQL Query in the Transaction's Link Editor. In the SQL Query Configuration, I have reset and re-added the modified Query Template to no avail. The transaction still appears to be working correctly. I have also tried creating a new transaction containing nothing but an SQL Query linking to this template and this is also not showing the rows.

Why can I no longer access the rows of the query? Is there something I need to do to make them re-appear?

Thanks,

John.

[jcgood25]

DId you answer 'Yes' to the Generate Sample XML question? If so, it will run the query template and embedded the reference document in the TRX. If you don't see the Row node with your columns in it, do you see a FatalError node (hovering over it with the mouse should show you the error)?

Regards,

Jeremy

[Former Member]

I've realised what was wrong. My query was looking for rows that matched a specific set of criteria and there were none that matched at that time therefore no rows were displayed in the transaction - I thought it would still show the row structure even if the query returned nothing at the time. So I had to change the where clause in the query so that it returned some values until I had reloaded the Query Template in the transaction and Generated Sample XML. Once this was done I could see the rows. Then I changed the where clause in the query back the way it was.

John.

[Former Member]

Somtimes you have to add valid hard coded parameter values to the parameters tab of the query to get the action block to load the query result structure. I think this happens when using a fixed query. Whe you are done loading the structure you can go back to the query and delete the parameter values.

[Former Member]

Hi John,

What version of xMII are you using?

Some things I would try:

1. Clear the Java Web Start Cache - see if that makes any difference.

2. If not, what happens if you save the query under a different name, and then try using it in a new transaction?

3. Please feel free to enter you case into xMII Support via the SAP Support Portal if you are unable to make this work.

Kind Regards,

Diana Hoppe