Clarity: PMO Portlet Actuals by Transaction Type does not expand and generates an error in the application log

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Description:

Environment: Oracle 11
PMO Add-In Version 2.2.0.0006
Portlet Name = Actuals by Transaction Type (ID=cop.prjTrxTypeHierarchy)
NSQL Query Name = Actuals by Transaction Type (ID=cop.trxTypeHierarchyLinkable)

In Microsoft Internet Explorer, when the end-user attempts to expand the rows of data; nothing happens and a javascript error message is generated in the browser lower left corner.
In Mozilla Firefox, when the end-user attempts to expand the rows of data; the row is repeated each time the '+' symbol is clicked
Only one resource is shown each time it is expanded.
The [More...] link only indicates there are only 3 resources; but we know there are many more resources with much more data

Steps to Reproduce:

1. In a Clarity system with PMO Accelerator Add-In installed, navigate to a Project > Dashboard tab
   
   
2. The Project should have actual financial transactions for various types of resources (Labor, Expense, Equipment or Material)
   
   
3. Click to expand the rows - not getting expected results
   
   
4. If the portlet is configured to add the 'HG_HAS_CHILDREN' to the layout, when the end-user clicks to expand the rows, the value will show with hash (#) symbols ; such as ######################0000000000

Expected Result: Portlet to function and show appropriate data

Actual Result: Portlet is not functioning as expected

A snippet of the following error message may be seen in the application log file:

ERROR 2011-09-01 09:05:29,432 [http-14001-12] web.WebActionController (admin:5010129__-727416bd:npt.gridNode)
com.niku.union.web.WebException: Service call failed for portlet: npt.gridNode
at com.niku.union.web.PortletController.processAuthorizedPortlet(PortletController.java:921)
at com.niku.union.web.PortletController.processPageActionRequest(PortletController.java:385)
...
Caused by: com.niku.odf.griphendor.GriphendorException: com.niku.union.persistence.nsql.NSQLException: com.niku.union.persistence.PersistenceException:
SQL error code: 1722
Error message: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-01722: invalid number

Executed:
select * from (select row_number() over ( order by dim_id asc) row_num, count(*) over () num_rows, q.* from ( SELECT A.TranTypeId_ResId_TrxId Dim_Id,

Solution:

WORKAROUND:

The construction of the NSQL Query needs modification to ensure that Clarity & Oracle can interpret the SELECT statement correctly when creating the concatenated fields.

Using the attached xml file, perform a XOG write action to update the existing NSQL Query Actuals by Transaction Type (ID=cop.trxTypeHierarchyLinkable)

STATUS/RESOLUTION:

Resolved in PMO 2.2.1

Keywords: CLARITYKB, PMO-627, pmo2resolved, pmo221resolved.

Environment

Release: ESPCLA99000-12.1-Clarity-Extended Support Plus
Component: