How to update Category Attribute of type User

Factiva_Guest_(x-factivaguest_-_(deleted))

I'm trying to update a category version to assign it to a document and I'm failing when I try to update an attribute of type "User".Has anyone come across a similar situation and found an answer to it, because I've tried retrieving the User's name and ID from the LAPI_USERS and I don't understand what do I pass in, the Username of the UserID. There seems to be no documentation about this either.Any help will be greatly appreciated.

Richard_Boyne_(boyne_(Delete)_891609)

A UserID is the value for a Category Attribute of type User.From the attrinfo page of the LAPI 9.2.0 SP1 online help:.... A code that designates the attribute type as specified by the Attribute Type Constants. In the C++ and Visual Basic environments, constants must be preceded by LL_, thus ATTR_TYPE_DATE becomes LL_ATTR_TYPE_DATE. In the Java environment, constants must be preceded by the class name, thus ATTR_TYPE_DATE becomes LAPI_ATTRIBUTES.ATTR_TYPE_DATE. The attribute type constants are as follows: Constant Type ATTR_TYPE_BOOL Boolean ATTR_TYPE_DATE Date ATTR_TYPE_DATEPOPUP Date pop-up ATTR_TYPE_INT Integer ATTR_TYPE_INTPOPUP Integer pop-up ATTR_TYPE_SET Set ATTR_TYPE_STRFIELD Text ATTR_TYPE_STRMULTI Text multi-line ATTR_TYPE_STRPOPUP Text pop-up >>>>>> ATTR_TYPE_USER UserID >>> ATTR_TYPE_REAL Real (Workflow only) ATTR_TYPE_REALPOPUP Real pop-up (Workflow only)The users and groups support function, GetUserInfo will retrieve a user's UserID (among other info) given a user name as input.The LAPI Sample code article on the Knowledge Center at: https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=3754925&objAction=ArticleView shows how to use GetUserInfo.THe LAPI sample code article on the Knowledge Center at: https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=3744124&objAction=ArticleView shows how to update an attribute value in a category version (catVersion) data structure using the AttrSetValues function. The attribute type in this example is not a USER attribute. But, it should provide an idea for the corresponding case.regards,Richard