OOTB Sponsor attribute doesn't copy from idea to project conversion

book

Article ID: 129174

calendar_today

Updated On:

Products

CLARITY PPM FOR ITG CLARITY PPM FEDERAL Clarity PPM SaaS - Application Clarity PPM On Premise

Issue/Introduction

The OOTB Sponsor attribute doesn't copy from idea to project conversion. I am getting error message when i try to add attribute mapping through XOG.

XML INPUT: 

<?xml version="1.0" encoding="UTF-8"?> 
<NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../../../xog/src/webroot/WEB-INF/xog/xsd/nikuxog_objectMapping.xsd"> 
<Header action="write" externalSource="NIKU" objectType="objectMapping" version="8.0"/> 
<objectMappings> 
<objectMapping mappingCode="ideaToProjectMap" srcObjectCode="idea" destObjectCode="project"> 
<nls description="Map From Idea to Project" languageCode="en" name="ideaToProjectMap"/> 
<attributeMappings> 
<attributeMapping srcAttributeCode="obj_business_owner" destAttributeCode="obj_stakeholder1"/> 
</attributeMappings> 
</objectMapping> 
</objectMappings> 
</NikuDataBus> 


Output 

<?xml version="1.0" encoding="UTF-8"?> 
<XOGOutput xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/status.xsd"> 
<Object type="objectMapping"/> 
<Status elapsedTime="0.033 seconds" state="SUCCESS"/> 
<Statistics failureRecords="1" insertedRecords="0" totalNumberOfRecords="1" updatedRecords="0"/> 
<Records> 
<Record> 
<KeyInformation> 
<column name="mappingCode">ideaToProjectMap</column> 
<column name="srcObjectCode">idea</column> 
<column name="destObjectCode">project</column> 
</KeyInformation> 
<ErrorInformation> 
<Severity>FATAL</Severity> 
<Description>XOG-3371: Failed to import object mapping.</Description> 
<Exception><![CDATA[ 
java.lang.Exception: XOG-3378: Data type mismatch between the source attribute code "obj_business_owner" and the target attribute code "obj_stakeholder1". 

Environment

Release:
Component: ODXOG

Resolution

System is doing the right thing. You can't map an attribute that uses one dynamic lookup to another attribute that uses a different dynamic lookup. The value stored is a number derived from the query - an ID in this case - and how that ID was derived from the query may be totally different between the two lookups. One ID retrieved from the first lookup might not ever be returned by the second lookup depending on how the queries were written.

This is working as designed.

Workaround: create custom attribute on the source object (idea) and point to the same lookup used in the destination object (project).