SQL query results not matching Portlet results
I created a portlet that get data from an NSQL query. The results displayed in the portlet do not match what is returned when the SQL query is run directly on the database.
In this case, the customer did not receive an error, but sometimes you may encounter the following error message displayed on the page:
NSQL NPT-217: This query produced duplicate dimensional data. The results shown here may be invalid or incomplete.
This is caused by non-unique values returned for the Dimension Key defined within the NSQL statement.
Modify the NSQL statement so that the 'Dimension Key' returns unique values within the result set. This 'Dimension Key' can be created with any field type, but the results must be unique within the result set.
If you ignore this error message and continue to use the portlet, you may be using incorrect or incomplete data displayed in the Portlet result set.
The error message that you receive cannot be turned off. This error message is important to the end user to indicate that the information or data result set displayed from the Portlet may not contain all the appropriate data. Although you may need to have duplicate rows for a particular field, you can still construct your query in a manner that will retrieve a unique Dimensional Key. You are not required to display the Dimensional Key on the published Portlet. You may also consider creating a multiple dimensional portlet, that may resolve your issue. If you have a multiple dimensional portlet containing more than one Dimensional Key, the value in the Dimensional key can be non-unique if the combination of the data in all Dimensional Keys are unique.
Reference the Clarity Studio Guide for more information on Portlet syntax and construction or consult CA Clarity Technology Services (CATS) for further assistance in creating Portlets to meet your business needs.
Keywords: CLARITYKB, 7033, 5644