Extracting Attributes from the LLATTRDATA table

It is my understanding that an attribute can existing in any of the value columns (i.e. VALINT, VALREAL, VALDATE, VALSTR, or VALLONG) depending on the ATTRTYPE value. Can anyone tell me what the values are the ATTRTYPE and to which columns they translate to in the LLATTRDATA table?

Find more posts tagged with

Comments

Bhupinder_Singh

Message from Bhupinder Singh via eLink<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

Here's some information I have on the AttrType field:

(see attachment LLAttrData.txt)

Let me know if that helps...

- Bhupinder

------------------------------------------------------
Bhupinder Singh, B.Math., B.Ed.
Senior Product Specialist, Customer Support
Open Text Corporation, Waterloo, Ontario, Canada
Customer support e-mail: support@opentext.com
Customer Support Telephone: 800-540-7292
------------------------------------------------------

From: eLink Discussion: Livelink LiveReports Discussion [mailto:livereportsdiscussion@elinkkc.opentext.com]
Sent: Tuesday, June 12, 2007 12:26 PM
To: eLink Recipient
Subject: Extracting Attributes from the LLATTRDATA table

Extracting Attributes from the LLATTRDATA table

Posted by enmaxappsupport (Szczesny, Jan) on 06/12/2007 12:21 PM

komments

Message from Greg Kellogg via eLinkOne thing I have found is that since LL adds a line to LLAttrData foreach attribute that is entered you have to join the table to itself topull all attribute data out on one row. I generally use something likethe following:SELECT a.valstr, b.valstr, c.valstrFROM llattrdata a, llattrdata b, llattrdata cWHERE a.id=b.id and a.id=c.id and a.attrid=1 and b.attrid=2 andc.attrid=3You would change the select to reference the appropriate datatype foreach specific attribute ID. This is from memory - I will test latertoday and verify but I think this is the appropriate WHERE clause. --Greg KelloggCertified Livelink Systems AdministratorLead Technical ConsultantOpenText Global Servicesgkellogg@opentext.com(361) 815-8950-----Original Message-----From: eLink Discussion: Livelink LiveReports Discussion[mailto:livereportsdiscussion@elinkkc.opentext.com] Sent: Tuesday, June 12, 2007 12:33 PMTo: eLink RecipientSubject: RE Extracting Attributes from the LLATTRDATA table

Drane_Matthew

Another option rather than linking another instance of the LLATTRDATA table for each attribute each time is to use a GROUP BY and MAX CASE statements to achieve the same effect.An example could be something like:SELECT DTree.Name, max(CASE WHEN LLAttrData.AttrID = 7 THEN LLAttrData.ValStr ELSE null END) as [Attr7], max(CASE WHEN LLAttrData.AttrID = 8 THEN LLAttrData.ValStr ELSE null END) as [Attr8] FROM DTree LEFT JOIN LLAttrData ON DTree.DataID = LLAttrData.ID AND DTree.VersionNum = LLAttrData.VerNum AND LLAttrData.DefID in () WHERE DTree.DataID = GROUP BY DTree.Name

komments

Message from Greg Kellogg <gkellogg@opentext.com> via eLink

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

A client has recently undergone an upgrade from Livelink 9.1.4 to Livelink 9.7. This process included upgrading to a UTF-8 environment. The upgrade process fixed the Shift-JIS characters in the system but not in the customview.html pages themselves. They are still encoded as Shift-JIS.

Has anyone developed a LiveReport that will find all customviews in a system and provide, at best, links to them, or at least, the ParentID and NodeID of each of them?

Thanks.

Greg Kellogg

Certified Livelink Systems Administrator

Lead Technical Consultant

OpenText Global Services
gkellogg@opentext.com
(361) 815-8950

komments

Message from Greg Kellogg <gkellogg@opentext.com> via eLink

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

Sorry, I thought I had set this up in its own thread. If an admin can move it to its own thread I would appreciate it.

Greg Kellogg

Certified Livelink Systems Administrator

Lead Technical Consultant

OpenText Global Services
gkellogg@opentext.com
(361) 815-8950

From: eLink Discussion: Livelink LiveReports Discussion [mailto:livereportsdiscussion@elinkkc.opentext.com]
Sent: Friday, November 09, 2007 10:06 AM
To: eLink Recipient
Subject: Locating CustomViews Throughout the Enterprise

Locating CustomViews Throughout the Enterprise Posted by gkellogg (Kellogg, Gregory) on 11/09/2007 11:06 AM
In reply to: RE Extracting Attributes from the LLATTRDATA table Posted by bsingh (Singh, Bhupinder) on 06/12/2007 01:32 PM

Message from Greg Kellogg <gkellogg@opentext.com> via eLink

A client has recently undergone an upgrade from Livelink 9.1.4 to Livelink 9.7. This process included upgrading to a UTF-8 environment. The upgrade process fixed the Shift-JIS characters in the system but not in the customview.html pages themselves. They are still encoded as Shift-JIS. Has anyone developed a LiveReport that will find all customviews in a system and provide, at best, links to them, or at least, the ParentID and NodeID of each of them? Thanks. -- Greg Kellogg Certified Livelink Systems Administrator Lead Technical Consultant OpenText Global Services
gkellogg@opentext.com
(361) 815-8950

Nair_Krishnankutty_(nairkrishnankutty_-_(deleted))

The new livelink started using subtype=146 for customviewso if they got upgraded to the new object subtype one should be able to writeselect dataid,parentid,name from dtree where subtype=146iF they didnot convert I think we could not call it anything other than customview.html in time immemorialso you could use select dataid,parentid,upper(name) from dtree where lower(name) like ( 'customview.html')