Maximo Open Forum

I am creating a new dashboard and adding work queues.  I have added a few from wotrack and  1 from purchase requisitions and was adding from purchase orders when i received this error message.  I checked all of the objects structures and security but still keep getting this message.  I didn't see this error until i added the purchase orders and now none of my work views are visible can someone please assist. Below is a screen shot of my error. 

You can check the server logs to get the exact error, but I would assume the saved query has an order by in it which is leading to the REST API error. At a high level, when the query has an order by and the REST API tries to provide an order by, it leads to a query like below (replacing querycolumns with the columns in the saved query and restcolumns with the order by provided by the REST API query parameters):

order by querycolumns order by restcolumns

The REST API doesn't replace the order by from the saved query and just adds to it which leads to an invalid SQL query. If you want to use the query in the Operational Dashboard you unfortunately need to remove the order by in the query. 

I am creating a new dashboard and adding work queues.  I have added a few from wotrack and  1 from purchase requisitions and was adding from purchase orders when i received this error message.  I checked all of the objects structures and security but still keep getting this message.  I didn't see this error until i added the purchase orders and now none of my work views are visible can someone please assist. Below is a screen shot of my error. 

Hi, Steven. Any idea if this is something IBM may eventually fix, or is this just the direction Operational Dashboards are moving in? We rely pretty heavily on ORDER BY statements in our classic Start Center result sets. Sounds like queues/tables in ODs don't handle saved queries the same way. Just curious whether this is a temporary limitation of the new architecture, or if they're just moving away from MBO-based sorting and filtering and handling it differently going forward. Thanks!

You can check the server logs to get the exact error, but I would assume the saved query has an order by in it which is leading to the REST API error. At a high level, when the query has an order by and the REST API tries to provide an order by, it leads to a query like below (replacing querycolumns with the columns in the saved query and restcolumns with the order by provided by the REST API query parameters):

order by querycolumns order by restcolumns

The REST API doesn't replace the order by from the saved query and just adds to it which leads to an invalid SQL query. If you want to use the query in the Operational Dashboard you unfortunately need to remove the order by in the query. 

I am creating a new dashboard and adding work queues.  I have added a few from wotrack and  1 from purchase requisitions and was adding from purchase orders when i received this error message.  I checked all of the objects structures and security but still keep getting this message.  I didn't see this error until i added the purchase orders and now none of my work views are visible can someone please assist. Below is a screen shot of my error. 

It would be interesting to see what IBM say if someone raised a PMR for this.

Technically the OOB functionality is causing a failure and generating an error.... so it could be raised with IBM

I suspect that they would publish a technote but the best long term solution would be a code change

Hi, Steven. Any idea if this is something IBM may eventually fix, or is this just the direction Operational Dashboards are moving in? We rely pretty heavily on ORDER BY statements in our classic Start Center result sets. Sounds like queues/tables in ODs don't handle saved queries the same way. Just curious whether this is a temporary limitation of the new architecture, or if they're just moving away from MBO-based sorting and filtering and handling it differently going forward. Thanks!

You can check the server logs to get the exact error, but I would assume the saved query has an order by in it which is leading to the REST API error. At a high level, when the query has an order by and the REST API tries to provide an order by, it leads to a query like below (replacing querycolumns with the columns in the saved query and restcolumns with the order by provided by the REST API query parameters):

order by querycolumns order by restcolumns

The REST API doesn't replace the order by from the saved query and just adds to it which leads to an invalid SQL query. If you want to use the query in the Operational Dashboard you unfortunately need to remove the order by in the query. 

I am creating a new dashboard and adding work queues.  I have added a few from wotrack and  1 from purchase requisitions and was adding from purchase orders when i received this error message.  I checked all of the objects structures and security but still keep getting this message.  I didn't see this error until i added the purchase orders and now none of my work views are visible can someone please assist. Below is a screen shot of my error. 

It's not accepted as a defect but was accepted as an idea a while ago: Support for "order by" | IBM Sustainability Software - Ideas Portal

It would be interesting to see what IBM say if someone raised a PMR for this.

Technically the OOB functionality is causing a failure and generating an error.... so it could be raised with IBM

I suspect that they would publish a technote but the best long term solution would be a code change

Hi, Steven. Any idea if this is something IBM may eventually fix, or is this just the direction Operational Dashboards are moving in? We rely pretty heavily on ORDER BY statements in our classic Start Center result sets. Sounds like queues/tables in ODs don't handle saved queries the same way. Just curious whether this is a temporary limitation of the new architecture, or if they're just moving away from MBO-based sorting and filtering and handling it differently going forward. Thanks!

You can check the server logs to get the exact error, but I would assume the saved query has an order by in it which is leading to the REST API error. At a high level, when the query has an order by and the REST API tries to provide an order by, it leads to a query like below (replacing querycolumns with the columns in the saved query and restcolumns with the order by provided by the REST API query parameters):

order by querycolumns order by restcolumns

The REST API doesn't replace the order by from the saved query and just adds to it which leads to an invalid SQL query. If you want to use the query in the Operational Dashboard you unfortunately need to remove the order by in the query. 

I am creating a new dashboard and adding work queues.  I have added a few from wotrack and  1 from purchase requisitions and was adding from purchase orders when i received this error message.  I checked all of the objects structures and security but still keep getting this message.  I didn't see this error until i added the purchase orders and now none of my work views are visible can someone please assist. Below is a screen shot of my error. 

I am creating a new dashboard and adding work queues.  I have added a few from wotrack and  1 from purchase requisitions and was adding from purchase orders when i received this error message.  I checked all of the objects structures and security but still keep getting this message.  I didn't see this error until i added the purchase orders and now none of my work views are visible can someone please assist. Below is a screen shot of my error. 

Steven's advice sounds valid. It would help if you could post the actual error message that is being seen in the logs.
If we can see the error message then we can confirm that there are no other problems

I am creating a new dashboard and adding work queues.  I have added a few from wotrack and  1 from purchase requisitions and was adding from purchase orders when i received this error message.  I checked all of the objects structures and security but still keep getting this message.  I didn't see this error until i added the purchase orders and now none of my work views are visible can someone please assist. Below is a screen shot of my error.