Content Server Database Tables

ask your OT Account person for the NDA for the schema, be sure to list all your modules as you may need additional notes for RM etc. Then you can use this with the Schema Companion guide (https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=16448243&objAction=View) to work with the DB. The OT course is also very good.

Please find the above category information information for a particular employee workspace, we have to fetch only "Location" attribute which is present in Categories —> Personal Information —> Location. We already have an query to fetch the workspace name of employee workspace and folders and files inside it. But now we have to add the new lines into in the query to fetch Location of that employee workspace. Please help me with the LLAttrData table info and what is the attribute I'd ifor this Location attriute.

?func=attributes.dump is a RH that is used,it reads the table CatRegionMap that Greg mentions

I have a query here that I used to pull Similar things the LLA1, and LLA2 are multiple joins to the same table. This is a common pattern one uses, there's an official one as well. The clue is to find the

LLA1.AttrID in (2) and 3 and so on which you get from CatRegionMap or ?func=attributes.dump.In my case all the data was defined as String hence the use of ValStr.Note that I am pulling from two categories

Enterprise Global,

Facility Global hence the differing numbers (270280 and 2331738)

select DT.DataID,DT.Name,

LLA4.ValStr "Facility Global:Discipline",

LLA5.ValStr "Facility Global:DocType",

LLA6.ValStr "Facility Global:ContentType",

LLA7.ValStr "Facility Global:Collection",

LLA8.ValStr "Facility Global:Business Function",

LLA1.ValStr "Enterprise Global:Business Function",

LLA2.ValStr "Enterprise Global:Collection",

LLA3.ValStr "Enterprise Global:Content Type",

DT.OwnerID,DT.ParentID,DT.SubType,DT.VersionNum

from DTree DT 

left   join  LLAttrData LLA1  on DT.DataID=LLA1.ID 

and LLA1.DefID=270280 and DT.VersionNum=LLA1.VerNum and LLA1.AttrID in (2)

left   join LLAttrData LLA2  on DT.DataID=LLA2.ID 

and LLA2.DefID=270280 and DT.VersionNum=LLA2.VerNum and LLA2.AttrID in (3)

left   join LLAttrData LLA3  on DT.DataID=LLA3.ID 

and LLA3.DefID=270280 and DT.VersionNum=LLA3.VerNum and LLA3.AttrID in (4)

left   join LLAttrData LLA4  on DT.DataID=LLA4.ID 

and LLA4.DefID=2331738 and DT.VersionNum=LLA4.VerNum and LLA4.AttrID in (2)

left   join LLAttrData LLA5  on DT.DataID=LLA5.ID 

and LLA5.DefID=2331738 and DT.VersionNum=LLA5.VerNum and LLA5.AttrID in (7)

left   join LLAttrData LLA6  on DT.DataID=LLA6.ID 

and LLA6.DefID=2331738 and DT.VersionNum=LLA6.VerNum and LLA6.AttrID in (11)

left   join LLAttrData LLA7  on DT.DataID=LLA7.ID 

and LLA7.DefID=2331738 and DT.VersionNum=LLA7.VerNum and LLA7.AttrID in (8)

left   join LLAttrData LLA8  on DT.DataID=LLA8.ID 

and LLA8.DefID=2331738 and DT.VersionNum=LLA8.VerNum and LLA8.AttrID in (12)

where  DT.DataID in (select TOP 30000 DataID FROM DTreeAncestors where AncestorID=2332140);

OT used to have a BI tool not sure if they still do. Its developers created these however this actually creates database objectshttps://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=12740255&objAction=ArticleView

No, the auto livereport is intended when you don't need to alias names. The standard LR format allows automatic hyperlinks in the output if certain key table columns are used DTree.dataid, KUAF.ID,webnodes, etc.

in an autolivereport, if you wrote select * from DTree it will spit out columns

in LR you would have to say the column names(aliases)

in your WR you will need to read the column returned either using positional parameters or column names.

The WR/LR should not be made by hand in production use a transport.