Category creation: use partner set (sub)item in subsequent TKL

[jdoor0]

Hello,

I wonder if it is possible to use a (sub)item from a partner set attribute (e.g. CP Id) in the query of a subsequent attribute of type table key lookup. Thx.
I also wonder if I can get hold of the DataId of the item on which the attributes are defined or any other "system" id, like the currently logged in user. Thx again.

 

[appnair]

Not exactly sure what the qn is but the partner database which is part of contracts lifecycle management and case management is basically a new attribute type that they developed to alleviate the pain of using a TKL. A TKL works based on a previous value selection in a sql statement,the next attribute could be prefilled and so on.Just by selecting one value of the partner database a oscript capi query is fired which pulls all the rest of the info and populates the several fields on the screen.Obviouslsy the partner set when applied to a document is in llattrdata so if you know a dataid in livelink that has the partner data set applied I am pretty sure you can find that row in llattrdata.

I would like to help but I have a hard time understanding your requirement.Not many people in livelink uses case managment framework or contracts lifecycle management so you may get better help if you asked the core developers of this OT product line for a speedier answer.

For one of my projects I used the CLM product and I populated the partner dtabase from a people soft systems as the company I was working for did not have a SAP sytem.At that time even though it looked formidable at one point i found it not be too much of challenge.




Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

 

[jdoor0]

Appnair,

I guessed that there would be no easy way to find the (sub)item of a contact, that's why I also wanted to know how I can get to the current document id, so as to be able to query llattrdata directly ;-)

Somewhat more info: I created a category with just 2 attributes: firstly a partner set, to select a supplier (why duplicate what's already present), and secondly a field where documents, related to this supplier can be selected from (a query, based upon the CP Id of the partner set).

 

[appnair]

see if I understand you correctly with this e.g
You have a Supplier let's call it 'SAP AG Germany' in CPDB
You also have in livelink about 1000 documents that pertain to this partner that came previously or in otherwords llattrdata has that partner set value in these 1000 documents

The user is adding a new Document.They select 'SAP AG GERMANY' for the partner set value ,you want the TKL to lookup llattrdata for the 1000 documents using some kind of efficient query.Is my understanding correct.

If it is then I think what you are trying to do is cross referencing documents,which again is available to you by a Xref function.

Or is this a reporting interface where you are trying to show the user a set of documents for that supplier ?

In either case I do not know the right answer but the CPDB schema is not that difficult.

I will see if I have some documentation on how i reverse engineered this for my own purposes.if i can find it I will post it at my perosnal workspace in the KB.Hope you have a KB login ,you must have as I see you have posted this in the KB as well.



Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

 

[jdoor0]

Appnair,

The document being uploaded is indeed supposed to reference another one from the same supplier - I cannot see how the Xref function could help me out here, though...
Anyway, the cpdb_lepa table and its few satellites are not that difficult to navigate, and the link to llattrdata is also easy, once you know the id of the attribute.
I'm just stuck in the category creation: I have a partner set attribute, where the uploader can easily select a contact/supplier. And then there is a second attribute with the "previous" item/document that needs to be referred/linked to.
Just how do I get to the first attribute's "CP Id" field? Either this is possible in the custom sql directly, through some undocumented feature so you can get the subitem or maybe you can - after obtaining the dataid of the current object (through an equally obfuscated feature) retrieve the needed value by sql-ing through llattrdata/cpdb_lepa.
Or maybe I should leave the partner set altogether and roll my own attribute set, linking parter and document in one fell swoop...