Updating a physical object through LAPI

I'm looking for some code that will update a physical object's from and to date through LAPI. I'm having trouble with UpdateObjectInfo. Here's some bare bones sample code:LLSession session = new LLSession( "localhost", 2099, "", "moo", "moo" );LAPI_DOCUMENTS documents = new LAPI_DOCUMENTS( session );LLValue llvalue = new LLValue( );documents.GetObjectInfo( 0, 28795, llvalue );documents.UpdateObjectInfo( 0, 28795, llvalue );This works for regular documents but not for boxes. I've traced the error to line 34 in NodeUpdateSubclassPre in PHYSICALOBJECTS.PhysObj LLNodes.PhysicalItems. For some reason, it is expecting updateInfo.Request to be a record whereas everywhere else seems to expect a Dynamic (including in NodeCreateSubclassPre for the same object).

Find more posts tagged with

Comments

Taavi_Ilves

Hi.I can't help you Libby, because I'm messing with somewhat the same problem. I'm trying to update one assoc inside a documents EXTENDEDDATA. This assoc keeps some integers, I have to read and later change. I'm trying to do it something like that:LLValue docInfo = new LLValue().setAssocNotSet();LLValue extData = new LLValue().setAssocNotSet();doc.GetObjectInfo( volId, docId, docInfo );extData = docInfo.toValue("EXTENDEDDATA");String number = extData.toString("valfield2"); extData.add("valfield2", Integer.valueOf(number).intValue()+1 ); //this simply increases valfield2 by 1docInfo.add("EXTENDEDDATA", extData);dok.UpdateObjectInfo(volId, dokId, docInfo)When I debug and compare original docInfo and modified docInfo (I just print them out to console), they differ only by this valfield2 variable inside EXTENDEDDATA, but this change never gets written into database, though UpdateObjectInfo returns 0.When I tried to reset docInfo and extData before using add function and then updating, the result was the same - everything is OK, but nothing gets really written into database.I'm using LL 9.5 SP1 LAPI...Any ideas what I'm doing wrong?

Taavi_Ilves

(Again... "Modify Post" button could be very handy here. I left some typo's://doc, docId, volId are correctly pre-defined variables...LLValue docInfo = new LLValue().setAssocNotSet();LLValue extData = new LLValue().setAssocNotSet();doc.GetObjectInfo( volId, docId, docInfo );extData = docInfo.toValue("EXTENDEDDATA");String number = extData.toString("valfield2");extData.add("valfield2", Integer.valueOf(number).intValue()+1 ); //this simply increases valfield2 by 1docInfo.add("EXTENDEDDATA", extData);dok.UpdateObjectInfo(volId, docId, docInfo)

Kyle_Baley

Don't think I can help but hopefully the number of posts in this thread will warrant a look from OpenText.My EXTENDEDDATA always gets returned as LLUndefined. Besides which, UpdateObjectInfo always throws an error for me, even if I pass in the same data I did with GetObjectInfo.

Taavi_Ilves

I'm quite insecure about this volumeID to use value 0 just like that, like you did on your illustrating example. I remember battleing with all strange things until I used correct volumeID. LLValue myEntValues=new LLValue(); if (doc.AccessEnterpriseWS(myEntValues) == 0) { volID = myEntValues.toInteger("VolumeID"); docID = myEntValues.toInteger("ID"); } And later on I can modify docID, but leave volID alone. If you are sure about your volume ID, then it's ok, but if you are not then check that code out. It works for me.I hope to see some official comment about that EXTENDEDDATA issue, because my development waits behind that. Pretty please!

David_Caughell

Message from David Caughell <dcaughel@opentext.com> via eLink

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

Hi Libby,

Looks like a bug. Please contact customer support (support@opentext.com) and have them open a ticket for you, and provide the version of the Physical Objects module you are using. We will look into creating a patch for this.

Regards,

David.

From: eLink Discussion: LAPI Discussion [mailto:lapi@elinkkc.opentext.com]
Sent: Monday, March 27, 2006 1:55 PM
To: eLink Recipient
Subject: Updating a physical object through LAPI

Updating a physical object through LAPI Posted by libbyrome (Rome, Libby) on 03/27/2006 01:51 PM

I'm looking for some code that will update a physical object's from and to date through LAPI. I'm having trouble with UpdateObjectInfo. Here's some bare bones sample code:

LLSession session = new LLSession( "localhost", 2099, "", "moo", "moo" );
LAPI_DOCUMENTS documents = new LAPI_DOCUMENTS( session );
LLValue llvalue = new LLValue( );
documents.GetObjectInfo( 0, 28795, llvalue );
documents.UpdateObjectInfo( 0, 28795, llvalue );

This works for regular documents but not for boxes. I've traced the error to line 34 in NodeUpdateSubclassPre in PHYSICALOBJECTS.PhysObj LLNodes.PhysicalItems. For some reason, it is expecting updateInfo.Request to be a record whereas everywhere else seems to expect a Dynamic (including in NodeCreateSubclassPre for the same object).

Michael_Crandall

Has anyone had any luck with this?

I would like to be able to update custom physical properties using the UpdateObjectInfo method but I am getting an error: "com.opentext.api.LLIllegalOperationException: get(name) not implemented for this datatype".

When I call the GetObjectInfo, I don't see any intuitive way to get at the custom physical properties. EXTENDEDDATA comes back "undefined".

Thanks for your help in advance!