API-1013 Invalid Filter String on filters that use "Contain" in Modern UX
search cancel

API-1013 Invalid Filter String on filters that use "Contain" in Modern UX

book

Article ID: 219154

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

Users are receiving API-1013 : Invalid Filter String on search with filter on Contains.

This happens on all Grid pages such as

  • Project list 
  • Adding Roadmap Items
  • Timesheet Grid


STEPS TO REPRODUCE:

  1. Open any MUX GRID, i.e. Timesheets Grid (happens on all Grid pages in MUX) 
  2. Add a Filter
  3. Select a field such as Resource Manager - Contains
  4. Enter any text, hit Enter, click away

 

Expected Results: The filter to work correctly and filter the view

Actual Results:

  • The filter throws an error API-1013 Invalid Filter String '' Each expression must start and end with parentheses and must have attributeName, operator and value.
  • HTTP 400 in the app-access logs. No app-ca.log error.
  • Other filters are working as expected, setting no filter works too

 

Environment

Release : 15.9.2

Component : CA PPM SAAS USERS, GROUPS, OBS ADMINISTRATION

Cause

Caused by stale cached data

Resolution

Workaround: Restart the services. Note : Flushing caches does not work

This is DE61731, that could not be reproduced and fixed by Engineering (CNR)