Clarity: Filters values disappear and the entire list is displayed.

Document ID : KB000051548
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Details:

When you click the filter button the values that you entered may disappear and the entire list will be displayed.

Note: This problem is no longer reproducible in 8.1.3 and above or 12.0.1 and above. (CLRT-20166)

Steps to Recreate:

  1. Create a user defined lookup (static list, hidden key = enum, add some values).
  2. Create a custom lookup attribute using the lookup defined in step 1 on the project object.
  3. Delete the user-defined lookup.
  4. Go to Home -> Projects.
  5. Click on Build Power Filter.
  6. Build a power filter on project name = 'proj1'.
  7. Submit. You're back on the project list with the project list filtered for projects who's name='proj1'.
  8. Click Show All to get the entire project list again.
  9. Enter 'proj1' in the Project Name field and Click Filter.

Expected Results: The project list is filtered for projects who's name='proj1'
Actual Results: All projects are shown. The project filter doesn't work again, except for power filters.

Solution:

Workarounds:

If you know the lookup-type or have a single orphaned attribute, run the following query:

SELECT INTERNAL_NAME FROM ODF_CUSTOM_ATTRIBUTES WHERE LOOKUP_TYPE='my_lookup' AND OBJECT_NAME='my_object'

To determine if multiple attributes are orphaned as well as their names and ids, run the following query:

select O.ID, O.INTERNAL_NAME, O.OBJECT_NAME, CAP.NAME
FROM ODF_CUSTOM_ATTRIBUTES O
INNER JOIN CMN_CAPTIONS_NLS CAP ON (O.ID=CAP.PK_ID AND
CAP.TABLE_NAME='ODF_CUSTOM_ATTRIBUTES' AND CAP.LANGUAGE_CODE='en')
WHERE O.LOOKUP_TYPE IS NOT NULL AND O.LOOKUP_TYPE NOT IN (SELECT LOOKUP_TYPE
FROM CMN_LOOKUP_TYPES)

Once you have located the attribute(s), go to the list of attributes for the object identified by your query and delete the attribute(s).

Note: Don't forget to check inactive attributes.

Status/Resolution:

CLRT-20166 which was fixed in 8.1.2 and 12.0.1. When you delete a lookup, there is no check done for attributes pointing to that lookup on the object. Even though the problem was fixed, attributes orphaned by deleting the lookup that are still in the database can cause this issue.

Keywords: CLARITYKB, CLRT-20167, CLRT-20166, filter, orphan, lookup, clarity12resolved, clarity1201resolved