How to Parse a Node’s categories in C# WCF code

****************************************** ***START UPDATE 10/3/2016*****************

LAPI and its client installer has become very hard to find. Moreover clients written in LAPI  in say Java/.NET will only work if your Livelink a.k.a Content Server is of version less than CS16.Readers who are new to LL programming is encouraged to read this to the approach and not to the exact lines of the code.What I mean is when you used to program in LAPI you were basically passing parameters to discrete calls by modelling it based on the webgui of livelink .SOAP based webservices called CWS is also the same,so if you do not try to do the task in the webgui and try to understand the business rules you will almost have no success in CWS too. OT is notorious for not putting fully functioning use cases and a walk through,so whenever possible I write code assuming the user has not worked in Livelink for X number of years and try to educate you all. Livelink,Content Server,Enterprise Server all of this has been Livelink’s marketing brand name changes over the years.CS i sused in many of the integrations like AGA, XECM, RMLINK  and you know you are programming against livelink if you see a link that looks like this  http(s)://somefriendlyURL/livelink.exe|cs.exe|llisapi.dll|cs.dll|livelink.In many places SAP/ SP /Exchange will be configured to talk to Archive Server and then they will use Livelink to read into archive server and turn that into LL objects for better presentment/RM and other aspects. The AGA product is moving away from LAPI(not sure totally or not) to REST API in LL.

**********************************************END UPDATE****************************

Recently a programmer asked me how you would show the values in a nodes categories.He had done all except up to the fact that he did not know how to get the

real values hidden in Stringvalue, Integervalue, boolean etc.I don’t remember seeing a good example but C#’s good debugger helped me.Also quite a posts form people like Sean Walker,Rob Vanderpoel

helped me understand the structure although I like seeing simple full samples rather than snippets

After you get the AttributeGroups,you have to go into that and get the DisplayName and keys and based on the type you have to cast that value making sure to handle nulls as well

perhaps now I can write better set attributes because i was wondering how one would write a generic call with the examples in OT.

I was able to do this in about 1.5 hrs and learned something as well.The code was done in a hurry and based off Jason Smith’s starter examples

here’s a link in case somebody needs it

 

Or email exchange hiding the actual names etc

Hi Appu,

Thank you for this information, it is very similar to what the REMOVED NAME consultant has produced so far, however the part we are stuck with is getting from the “Key” value to the actual data shown in Livelink.

For example the output for the document you reference below looks something like:

Display Name: Title –- Its key is: 122343.9.24

We would like to see:

Display Name: Title –- Its value is: WEB SERVICES NEED BETTER EXAMPLES

Is this something that you have been able to accomplish? There doesn’t seem to be any calls to make the jump from Key to Value.

Thanks,

 

Advertisement