How to Change attribute value from backend so that changes could be seen from function->info->catego

Anuradha_Deo_(PATCOM01User2_(Delete)_2735478)

Hi,We have attached category/attribute to every document uploaded in Livelink.We want to change attribute value for all documents. We tried changing it from database.(Replaced text by text)But when we check attribute value from function->Info->category, still oldvalue of attribute is displayed.Could you please tell us how to change attribute value from database and how to reflect those changes in livelink function->info->category screen also? We want to replace character "&"in document name by "and" for all documents. Changing it for each documentthrough function->info->category will be very time consuming.

Find more posts tagged with

Comments

Support_Lloyds_Register

Changing the attribute value for a category in Livelink v9 is possible through direct SQL code run in the Livelink Builder.I have achieved the same. The DAPI (Document Application Programming Interface) does allow access to the maintained hierarchical database of nodes and their related attributes.Each node can have multiple versions of data, in the form of BLOBs (Binary Large Objects). But the changes done via the same do not show the required results on the front end HTML Interface, since most of them are read-only attribute value definitions. My initiative was to search for a way to edit/change the BLOB data in the SEGMENTBLOB column of the LLATTRBLOBDATA table in livelink database, which i was able to do via SQL code run using the built-in functions in the CAPI package.I am happy to send across the working code to anyone who is interested in doing the same for his Livelink application.You can contact me at :Shashank AmbekarSenior ConsultantCap Gemini Consulting Plc.Mobile : 91-22-9820690525Email : shashank.ambekar@capgemini.com

Alex_Kowalenko_(akowalen_(Delete)_2285456)

Message from Alex Kowalenko via eLinkWhy not use the LLIAPI AttrObjects constructs to do this? For example,$LLIAPI.AttrData.New( etc ) creates a frame from where you change attributevalues. The DBPut method of this frame takes care of the duality ofoperating between LLAttrBLOBData and LLAttrData tables.-alex------Original Message-----From: eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com]Sent: Monday, May 24, 2004 12:03 PMTo: eLink RecipientSubject: Changing the category attribute value via backend is possible.Can help you ? ( Posted By -> Shashank Ambekar )Changing the category attribute value via backend is possible. Can help you? ( Posted By -> Shashank Ambekar )Posted by Campbell, Philip on 05/24/2004 12:02 PMChanging the attribute value for a category in Livelink v9 is possiblethrough direct SQL code run in the Livelink Builder.I have achieved the same. The DAPI (Document Application ProgrammingInterface) does allow access to the maintained hierarchical database ofnodes and their related attributes.Each node can have multiple versions of data, in the form of BLOBs (BinaryLarge Objects). But the changes done via the same do not show the requiredresults on the front end HTML Interface, since most of them are read-onlyattribute value definitions.My initiative was to search for a way to edit/change the BLOB data in theSEGMENTBLOB column of the LLATTRBLOBDATA table in livelink database, which iwas able to do via SQL code run using the built-in functions in the CAPIpackage.I am happy to send across the working code to anyone who is interested indoing the same for his Livelink application.You can contact me at :Shashank AmbekarSenior ConsultantCap Gemini Consulting Plc.Mobile : 91-22-9820690525Email : shashank.ambekar@capgemini.com[To reply to this thread, use your normal E-mail reply function.]============================================================Topic: How to Change attribute value from backend so that changes couldbe seen from function->info->categoryhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2886395&objAction=viewDiscussion: Development Discussionhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=786303&objAction=viewLivelink Server:https://knowledge.opentext.com/knowledge/livelink.exe

Support_Lloyds_Register

Dear Alex,Your method of using the LLIAPI AttrObjects constructs to change the attribute values for a category may also be a good alternative solution to the issue.But you shall definately agree with me on the fact, that when the same task can be done in 4-5 lines of code , and which is simpler to understand and implement is a better bet.Your's is definately a good alternative.By the way, are you with OpenText (Australia Asia-Pacific Region.) CheersShashank AmbekarSenior Consultant Capgemini Consulting Plc. Mobile : 91-22-9820690525 Email : shashank.ambekar@capgemini.com

Alex_Kowalenko_(akowalen_(Delete)_2285456)

Message from Alex Kowalenko via eLinkYes, I happen to be with Open Text Corporation (in Canada) and you are withCapgemeni. I have been involved with several joint projects between ourorganizations.As with most programming challenges, there is the supported API way and thenthere are many other ways. I have often been found guilty of direct databasemanipulation to get something done quickly. However, I cannot agree thatthis is always the best bet. I would be glad to take a look at your 4-5lines of code.Regards,Alex KowalenkoLead Consultant - Global ServicesOpen Text CorporationPh: 613-838-5220 (office & mobile)Fax: 613-838-3417Email: alexk@opentext.com-----Original Message-----From: eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com]Sent: Wednesday, May 26, 2004 10:05 AMTo: eLink RecipientSubject: That too can be done Alex, but i still believe my method issimpler.Ofcourse opinions are meant to differ. Cheers Buddy.That too can be done Alex, but i still believe my method is simpler.Ofcourseopinions are meant to differ. Cheers Buddy.Posted by Campbell, Philip on 05/26/2004 10:04 AMDear Alex,Your method of using the LLIAPI AttrObjects constructs to change theattribute values for a category may also be a good alternative solution tothe issue.But you shall definately agree with me on the fact, that when the same taskcan be done in 4-5 lines of code , and which is simpler to understand andimplement is a better bet.Your's is definately a good alternative.By the way, are you with OpenText (Australia Asia-Pacific Region.)CheersShashank AmbekarSenior ConsultantCapgemini Consulting Plc.Mobile : 91-22-9820690525Email : shashank.ambekar@capgemini.com[To reply to this thread, use your normal E-mail reply function.]============================================================Topic: How to Change attribute value from backend so that changes couldbe seen from function->info->categoryhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2886395&objAction=viewDiscussion: Development Discussionhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=786303&objAction=viewLivelink Server:https://knowledge.opentext.com/knowledge/livelink.exe

Magnus_S_(novnoruser_-_(deleted))

I think the attributes is not normalized in the db --> that they will appear at more places so to bee the cool person just upgrading directly in the db also meansthat you really should know your own limitations ;-)You will easier run into upgrade problems with the direct method as attributes is something OT redo when some smarter guys get hired at OT engineering......

eLink User

In Application programming when you are working with a Product, there are limitations. Biggest you cannot always play around with sql (db). As a good programmer you should be always taking in terms of API's rather than tables and sqls. In future opentext can change tables, correspondingly they will change the APIs. So need not worry about your existing codes.RegardsSourabh Bhattacharya

Alex_Kowalenko_(akowalen_(Delete)_2285456)

Message from Alex Kowalenko via eLinkLivelink attributes behave somewhat like the quantum mechanical nature oflight - they exist in two forms at the same time. The LLAttrBLOBData storesa representation of the attributes' internal associative data structure,while LLAttrData stores a tabular array of these same attributes for SQLquery purposes. However, there is a definite precedence relationship betweenthese dual structures. LLAttrBLOBData is the authority while LLAttrData islike a read-only view. In that "light", the attribute data are notdenormalized but rather have multiple views.-alex-PS - when you find some smart folks (smart people are not always guys)please let me know.-----Original Message-----From: eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com]Sent: Thursday, May 27, 2004 12:30 PMTo: eLink RecipientSubject: Smart guysSmart guysPosted by NOVNORUser on 05/27/2004 12:25 PMI think the attributes is not normalized in the db --> that they will appearat more places so to bee the cool person just upgrading directly in the dbalso meansthat you really should know your own limitations ;-)You will easier run into upgrade problems with the direct method asattributes is something OT redo when some smarter guys get hired at OTengineering......[To reply to this thread, use your normal E-mail reply function.]============================================================Topic: How to Change attribute value from backend so that changes couldbe seen from function->info->categoryhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2886395&objAction=viewDiscussion: Development Discussionhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=786303&objAction=viewLivelink Server:https://knowledge.opentext.com/knowledge/livelink.exe

x-scoruser8_-_(deleted)

I agree that using the api should be the preferred method, however there are many occasions where using lapi is not feasibile. For example changing attribute values in a repository with 1 million + objects would be much longer than direct updates to the database. In other cases the functionality isn't there at all, especially when you have optional modules or customizations installed. Also, there are many more developers trained in sql than in the Livelink API's. Lastly, every developer I've worked with has complained mightily about the lack of value of the LLValue object.

eLink User

LAPI may be problem but not O'Script (API's). By DBGet and DBPut we can do changes very easily that ultimately uses DAPI or CAPI to get the work done.

Support_Lloyds_Register

I agree with Alex , that the Livelink attributes behave somewhat like the quantum mechanical nature of light - they exist in two forms at the same time. LLAttrBLOBData is the authority while LLAttrData is like a read-only view. In that "light", the attribute data are not denormalized but rather have multiple views.There is no use changing the value string of the LLAttrData table. The value there, as mentioned above is just a read-only value, changing which, does not impact the main view. It's been practically tested to be true.The updation of the value tag in the SEGMENTBLOB column of the LLAttrBLOBData table, at this moment giving us our required functionality. This OScript function is being called by us in our code , and is performing its task as required. I have attached the file for your review and feedback.And i am happy to recieve your suggestions regarding the same, so that this functionality/approach taken can be furthur improved or changed for a better alternative. Since, i believe there is always a better way of doing things. Looking forward to your comments and suggestions.You can contact me at :Shashank AmbekarSenior ConsultantCapgemini Consulting Plc.Mobile : 91-22-9820690525Email : shashank.ambekar@capgemini.comPs : NOVNORUser : Myself and alex would surely appreciate your review suggestions regarding the above.

Alex_Kowalenko_(akowalen_(Delete)_2285456)

Message from Alex Kowalenko via eLinkI'm glad that you agree. I wrote a book on the topic. See attached slidefrom my course on Livelink attributes schema for a picture of this duality.You will note that there is s definite purpose to the read-only table. Cananyone in the world-wide developers' discussion group give me some pros andcons of Shashank's approach?-alex------Original Message-----From: eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com]Sent: Wednesday, June 02, 2004 9:47 AMTo: eLink RecipientSubject: Reply from Shashank Ambekar (shashank.ambekar@capgemini.com)Reply from Shashank Ambekar (shashank.ambekar@capgemini.com)Posted by Campbell, Philip on 06/02/2004 09:41 AMI agree with Alex , that the Livelink attributes behave somewhat like thequantum mechanical nature oflight - they exist in two forms at the same time.LLAttrBLOBData is the authority while LLAttrData is like a read-only view.In that "light", the attribute data are not denormalized but rather havemultiple views.There is no use changing the value string of the LLAttrData table. The valuethere, as mentioned above is just a read-only value, changing which, doesnot impact the main view. It's been practically tested to be true.The updation of the value tag in the SEGMENTBLOB column of theLLAttrBLOBData table, at this moment giving us our required functionality.This OScript function is being called by us in our code , and is performingits task as required. I have attached the file for your review and feedback.And i am happy to recieve your suggestions regarding the same, so that thisfunctionality/approach taken can be furthur improved or changed for a betteralternative. Since, i believe there is always a better way of doing things.Looking forward to your comments and suggestions.You can contact me at :Shashank AmbekarSenior ConsultantCapgemini Consulting Plc.Mobile : 91-22-9820690525Email : shashank.ambekar@capgemini.comPs : NOVNORUser : Myself and alex would surely appreciate your reviewsuggestions regarding the above.[To reply to this thread, use your normal E-mail reply function.]============================================================Attachment link: CustomCategoryAttribute.ziphttps://knowledge.opentext.com/knowledge/livelink.exe/3512047/CustomCategoryAttribute.zip?func=doc.Fetch&nodeid=3512047============================================================Topic: How to Change attribute value from backend so that changes couldbe seen from function->info->categoryhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2886395&objAction=viewDiscussion: Development Discussionhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=786303&objAction=viewLivelink Server:https://knowledge.opentext.com/knowledge/livelink.exe

eLink User

I think still Shashank has to go through the functions 'dbput' and 'dbget'.

Support_Lloyds_Register

Dear Friends,I find it really interesting to know the views that each one of the community has with regards to the approach taken by me to use simple SQL to change the attribute values for a category.I really appreciate and agree with what Glenn Heying (SCorUser8) has to say on this,"I agree that using the api should be the preferred method, however there are many occasions where using lapi is not feasibile. For example changing attribute values in a repository with 1 million + objects would be much longer than direct updates to the database. In other cases the functionality isn't there at all, especially when you have optional modules or customizations installed."Saurabh Bhattacharya (APPMAT03gdc) also has admitted to the fact that each product has it's limitations and we cannot always depend on the provided API's for tasks which are highly customized and require precise changes to be done. (like in our application.) By the way, Saurabh, are you still with Siemens (Nexus).In my opinion, i feel that Alex Kowalenko (akowalen) has provided us with a right approach regarding the issue. You can review the attachment (Duality.pdf) that he has attached with his reply to the approach taken by me.It's really informative. Thanks again, Alex.Anyway, i feel that this forum is surely a great way to get to know, and be in contact with the rare species (ie. Livelink Developers/Administrators) today.Cheers.You can contact me at :Shashank AmbekarSenior ConsultantCapgemini Consulting Plc.Mobile : 91-22-9820690525Email : shashank.ambekar@capgemini.com