Population extendedData in DTREE for URL SUBTYPE

Primavera_General_Account_(primav021_-_(deleted))

Is it possible to populate the extendedData field for URL subtype using LAPI for 9.0.0.1. I am using CreateObjectEx function. I need to populated some values in extendedData field which we will use for special application purposes. when I am creating a URL subtype with extendedData, the URL is added correctly in the DTREE but the extendedData field appears to be NULL always.Please help me out.regards,Abhishek Pandeyhere is the piece of code

/ for URLRequest.setAssocNotSet();Request.add( "Comment", "URL Comment" );Request.add( "TargetURL", "http://www.primecontract.com" );extendedData.setAssocNotSet();extendedData.add("Type", "AFP TASK");extendedData.add("Name", "Review Application For Payment");extendedData.add("DueDate", "None");extendedData.add("Priority", "Medium");extendedData.add("Status", "Outstanding");extendedData.add("From", "Lisa Ann");extendedData.add("Location","http://www.yahoo.com");node_in.add( "Request", Request );node_in.add( "extendedData", extendedData);if ( documents.CreateObjectEx( pVolumeID, pNodeID, documents.VERSIONOBJECTTYPE, documents.URLSUBTYPE, "AFP Task URL", node_in, objInfo ) == 0 ){System.out.println( "\nURL Created Using CreateObjectEx" );nodeID = objInfo.toInteger( "ID" );nodeVol = objInfo.toInteger( "VolumeID" );//documents.DeleteObject( nodeVol, nodeID );}

Find more posts tagged with

Comments

Norman_Leung_(ImvecAdmin_(Delete)_2148619)

As told by OpenText support, LAPI does not support ExtendedData updating. It is because there is a potential risk for developers to destroy the node's original data completely.They, however, provided us a solution on this issue and we have written a patch to allow updating on ExtendedData through LAPI. You may simply put the attached file to the patch directory and you can then update the ExtendedData.We STRONGLY recommend you to do the following:1. Try to pack your data into a List ( e.g., {'TypeValue','NameValue','DueDateValue'} )2. Convert the list into string (e.g., '{\'TypeValue\',\'NameValue\',\'DueDateValue\'}')3. Use an assoc key with your company to store the converted string (e.g., A<1,?,'YourCompanyName_Data'='{\'TypeValue\',\'NameValue\',\'DueDateValue\'}'>)4. Make sure everything works fine in both the development environment and testing environment before deploying to the production environment.To store your data in one assoc key could avoid the conflict of key name.Hope this helps,Desmond YeungProject Manager, Imvec (HK) Limited

eLink User

Message from Hans Stoop <<A HREF="mailto:hstoop@opentext.com">hstoop@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

You forgot point 5:

5. Retain the original content of the extendedData field, only touch your own part.

Hans Stoop

--------------
Register your subtypes in the OScript Registry:
https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2454603
Consultant Partner Programs Europe
hstoop@opentext.com
+31 23 5652333
http://www.opentext.com/

-----Original Message-----
From: knowledge@opentext.com [mailto:knowledge@opentext.com]On Behalf Of eLink Discussion: LAPI Discussion
Sent: vrijdag 10 augustus 2001 4:24
To: eLink Recipient
Subject: See if this helps

See if this helps Posted by ImvecAdmin (Leung, Norman) on 08/09/2001 10:21 PM
In reply to: Population extendedData in DTREE for URL SUBTYPE Posted by PRIMAV021 (Kulkarni, Vinit M) on 08/09/2001 01:24 PM

As told by OpenText support, LAPI does not support ExtendedData updating. It is because there is a potential risk for developers to destroy the node's original data completely.

They, however, provided us a solution on this issue and we have written a patch to allow updating on ExtendedData through LAPI. You may simply put the attached file to the patch directory and you can then update the ExtendedData.

We STRONGLY recommend you to do the following:

1. Try to pack your data into a List ( e.g., {'TypeValue','NameValue','DueDateValue'} )
2. Convert the list into string (e.g., '{\'TypeValue\',\'NameValue\',\'DueDateValue\'}')
3. Use an assoc key with your company to store the converted string (e.g., A<1,?,'YourCompanyName_Data'='{\'TypeValue\',\'NameValue\',\'DueDateValue\'}'>)
4. Make sure everything works fine in both the development environment and testing environment before deploying to the production environment.

To store your data in one assoc key could avoid the conflict of key name.

Hope this helps,

Desmond Yeung
Project Manager, Imvec (HK) Limited

Primavera_General_Account_(primav021_-_(deleted))

thanks for your input. I applied the patch to my livelink instance. After that I run my java code, but IT DID'NT WORKED. Still the extendedData is NULL.I am trying to Add a URL type in DTREE using LAPI calls. The 'extendedData' field is always empty for URL so adding in extendedData is not going to affect node's original data.so, I guess the piece of code which i had posted in the original question, should have worked.now, Is it because I am populating the extendedData Field for a URL subtype, which is always NULL otherwise. please help me out....Abhishek Pandey(610-949-6657)

Norman_Leung_(ImvecAdmin_(Delete)_2148619)

I tried it for a document node, and it works fine. According to the modification of the patch, it should work for all types of object. You may want to give it a try on a document object to see if it works. (Just a reminder, you need to restart the service after applying the patch.)As I told you in the previous reply, you are suggested to change the extendedData keys to some unique names to avoid conflict. I know that there is current nothing in URL extendedData, but who knows if it will be used in the future version. After you deploy the solution and all the URL objects contain values in their extendedData, it will then be extremely difficult to make changes. So, think thoroughly before proceed.Good luck!