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

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


Article ID: 129174


Updated On:


Clarity PPM SaaS Clarity PPM On Premise


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 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"/> 
<objectMapping mappingCode="ideaToProjectMap" srcObjectCode="idea" destObjectCode="project"> 
<nls description="Map From Idea to Project" languageCode="en" name="ideaToProjectMap"/> 
<attributeMapping srcAttributeCode="obj_business_owner" destAttributeCode="obj_stakeholder1"/> 


<?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"/> 
<column name="mappingCode">ideaToProjectMap</column> 
<column name="srcObjectCode">idea</column> 
<column name="destObjectCode">project</column> 
<Description>XOG-3371: Failed to import object mapping.</Description> 
java.lang.Exception: XOG-3378: Data type mismatch between the source attribute code "obj_business_owner" and the target attribute code "obj_stakeholder1". 


Component: ODXOG


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).