Reading/Updating Custom Attributes in LL v9.x

Tom_Fontanella_(genzymeuser1_-_(deleted))

What is the correct method for reading and updating custom attributes in LL v9 using OScript code? I've seen several threads that mention differences between v8 and v9 and LAPI, but am having difficulty locating the proper methods in v9 using OScript. Seems as if the old DAPI methods do not work anymore?We need to select based on attribute values, then update specific attributes. Would also like to have these updates show in appropriate LL audit logs if configured to log those types of updates.Any info appreciated.Thanks,Eliot Gorman

Find more posts tagged with

Comments

Kevin_Ward

Message from Kevin Ward <<A HREF="mailto:kward@opentext.com">kward@opentext.com> via eLink

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

There are two useful Knowledge Base Articles here:

https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=2509054&objAction=browse&sort=name

Kevin

-----Original Message-----
From: eLink Discussion: LAPI Discussion [mailto:lapi@elinkkc.opentext.com]
Sent: May 23, 2003 9:57 AM
To: eLink Recipient
Subject: Reading/Updating Custom Attributes in LL v9.x

Reading/Updating Custom Attributes in LL v9.x Posted by GenzymeUser1 (Gorman, Eliot) on 05/23/2003 09:43 AM

What is the correct method for reading and updating custom attributes in LL v9 using OScript code? I've seen several threads that mention differences between v8 and v9 and LAPI, but am having difficulty locating the proper methods in v9 using OScript. Seems as if the old DAPI methods do not work anymore?

We need to select based on attribute values, then update specific attributes. Would also like to have these updates show in appropriate LL audit logs if configured to log those types of updates.

Any info appreciated.

Thanks,

Eliot Gorman

Tom_Fontanella_(genzymeuser1_-_(deleted))

Thanks for the reply Kevin.I've been thru both of those tech tips, but for some reason when I use these methods, my node appears to have no custom attribute data, at least nothing is getting returned. I must be missing something?Are there different ways to store attribute data in v9, that may require different ways to retrieve/update the attribute data?Thanks,Eliot

Kevin_Ward

Message from Kevin Ward <<A HREF="mailto:kward@opentext.com">kward@opentext.com> via eLink

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

Eliot,

Try setting the attributes through the browser and then load the structure in Builder (f.DBGet()). Make sure the data is there including the newly set attribute values. If it isn't, you're loading the attributes from the wrong node or version.

Kevin

-----Original Message-----
From: eLink Discussion: LAPI Discussion [mailto:lapi@elinkkc.opentext.com]
Sent: May 23, 2003 11:06 AM
To: eLink Recipient
Subject: RE Reading/Updating Custom Attributes in LL v9.x

RE Reading/Updating Custom Attributes in LL v9.x Posted by GenzymeUser1 (Gorman, Eliot) on 05/23/2003 10:48 AM
In reply to: RE Reading/Updating Custom Attributes in LL v9.x Posted by kward (Ward, Kevin) on 05/23/2003 10:13 AM

Thanks for the reply Kevin.

I've been thru both of those tech tips, but for some reason when I use these methods, my node appears to have no custom attribute data, at least nothing is getting returned. I must be missing something?

Are there different ways to store attribute data in v9, that may require different ways to retrieve/update the attribute data?

Thanks,

Eliot

Tom_Fontanella_(genzymeuser1_-_(deleted))

Kevin,Thanks, I believe it was the version number. I passed the Node.pVersionNum instead of a hard coded 0 (assuming it would use current) and I now get the data returned as the documentation states. Now I just need code up the put to do the update which looks straight forward.I trust that an update using f.DBPut() will automatically add these to the indexing pool with the updated attribute information?Thanks for your help - Eliot

Kevin_Ward

Message from Kevin Ward <<A HREF="mailto:kward@opentext.com">kward@opentext.com> via eLink

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

That's correct Eliot, the DBPut() should mark the node for indexing.

Kevin

-----Original Message-----
From: eLink Discussion: LAPI Discussion [mailto:lapi@elinkkc.opentext.com]
Sent: May 23, 2003 1:28 PM
To: eLink Recipient
Subject: RE Reading/Updating Custom Attributes in LL v9.x

RE Reading/Updating Custom Attributes in LL v9.x Posted by GenzymeUser1 (Gorman, Eliot) on 05/23/2003 01:21 PM
In reply to: RE RE Reading/Updating Custom Attributes in LL v9.x Posted by kward (Ward, Kevin) on 05/23/2003 11:34 AM

Kevin,

Thanks, I believe it was the version number. I passed the Node.pVersionNum instead of a hard coded 0 (assuming it would use current) and I now get the data returned as the documentation states. Now I just need code up the put to do the update which looks straight forward.

I trust that an update using f.DBPut() will automatically add these to the indexing pool with the updated attribute information?

Thanks for your help - Eliot

Tom_Fontanella_(genzymeuser1_-_(deleted))

Thanks much Kevin.Eliot

Tom_Fontanella_(genzymeuser1_-_(deleted))

When using the frame.DBPut() method to update my attribute, is this method updating all of the attribute values contained in the frame object or only the "dirty" attribute value?If LL is not aware of the "dirty" attribute value, is there a more specific method of updating only a single attribute?Is there a way of "locking" the frame or attributes such that I can retrieve the values, perform some processing, then update the attribute without running the risk of some other user or process possibly updating another attribute value while I have the frame buffered in my code? The answer to updating only the "dirty" attribute issue may solve this question.One more! The frame.DBPut() does not seem to log attribute updates in the LL audit log, is that something that needs to be done separately?Thank you,Eliot Gorman

Magnus_Salgo_(IDNordicAdmin_(Delete)_2300172)

Some answer 1. I am not aware of just updating the dirty values with DBPutWhat maybe is possible is that you implementing this locking mechanism yourself done in the LLAttribute code of your attribute ( I assume then that you create your own attributes ==> you get more controll see other discussions and first look sample package)Audit is done by the llAPI.Kernel.LLNode operations it is not fired by DAPI calls or Attribute data operations ==>you need to call $LLIApi.NodeUtil.Audit yourselfRegardsMagnus S?lg?salgo@ids.se

Tom_Fontanella_(genzymeuser1_-_(deleted))

Thank you for the information Magnus.Eliot