ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

The xog of a lookup value to update a project does not resolve to the correct value

book

Article ID: 238660

calendar_today

Updated On:

Products

Clarity PPM SaaS

Issue/Introduction

You have a lookup on the project object which points to a "client" table.

In your XOG, you're updating the project as follows:

<?xml version="1.0" encoding="UTF-8"?>
<NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_read.xsd">
  <Header action="write" externalSource="NIKU" objectType="project" version="15.9.2.910">
<Projects>
 <Project name="Client_ market_ test1_March23rd_2022" projectID="PRJ123456">
  <CustomInformation>
   <ColumnValue name="eu_client_name">CLN-000100<ColumnValue>
  </CustomInformation>
 <Project>
</Projects>
<NikuDataBus>

The project is updated successfully but with the wrong lookup value.

The project was updated with CLN-0001000 when it should have been CLN-000100.

Cause

Clarity XOG is adding a wild card to the search "CLN-000100*" and coming back with the first row returned.

Environment

Release : 16.0.1

Component : Clarity XOG and REST API

Resolution

This is being pursued by Broadcom Engineering as defect: DE64713

 

Workaround:

Add the "code" attribute to the Auto Suggest for the Lookup

Attachments