API-1019 error in Modern UX lookup

book

Article ID: 242794

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

A lookup attribute works in Classic UX, but it throws "API-1019 : Could not process the request due to internal error." when updating from the Modern UX.

Steps to Reproduce:

  1. Create a new lookup with the following sample code:
    SELECT 
    @SELECT:to_number(concat(inv.id,inv.id)):[email protected],
    @SELECT:INV.ID:[email protected],
    @SELECT:INV.NAME:[email protected],
    @SELECT:INV.CODE:[email protected]
    FROM INV_INVESTMENTS INV
    WHERE @[email protected]
  2. Set "ID" as the Hidden Key for the lookup.
  3. Create a new Multi Valued Lookup attribute in the Project object that based on the lookup.
  4. In the Classic UX, for any Project instance, set any values for the MVL attribute.
  5. In the Modern UX, for any Project instance, set any values for the MVL attribute.

Expected Results: Classic and Modern UX save the values for the MVL attribute correctly.

Actual Results: Classic saves the values for the MVL attribute correctly, but the Modern UX throws an error "API-1019 : Could not process the request due to internal error.".

Cause

DE65280 - The '@SELECT:to_number(concat(inv.id,inv.id)):[email protected],' in the query is getting cast incorrectly by the Modern UX data parser. 

Environment

Release : 15.9.3, 16.0.0, 16.0.1, 16.0.2 

Component : Clarity Studio

Resolution

Targeted Fix in Release 16.0.3