nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

CreateCategory

Guy_Turton

Hello,

I'm trying to create a categroy using the web services and I keep getting the following error:

DocumentManagement.CreateCategory() failed on the Livelink Server. No results were returned. Check the Livelink Server thread logs.

The category is created, however, the attributes are not. I don't see any useful info in the thread logs as well.

here is my code:

DocumentManagement. Attribute attr1 = new DocumentManagement. Attribute ();

attr1.DisplayName = "Test field 1" ;

attr1.Required = false ;

attr1.Searchable = false ;

attr1.Type = "String" ;

attr1.MaxValues = 1;

attr1.MinValues = 1;

DocumentManagement. Attribute [] attrs = new DocumentManagement. Attribute [1];

attrs[0] = attr1;

DocumentManagement. Metadata metadata = new DocumentManagement. Metadata ();

try

{

dm.CreateCategory(dmOTAuth, 2004, categoryNm, "" , attrs, null );

}

catch ( Exception ex)

{

lblResults.Text = ex.Message;

}

Am I missing something? or do I have the Attribute settings correct? Any ideas?

Any help would be appreciated. Thanks.

Find more posts tagged with

Comments

Kyle_Swidrovich

Hi Guy,

You may see more useful information in the logs once you enable API logging.

In the [options] section of your /config/opentext.ini file, set the following:

wantLAPILogs=TRUE

With thread logging on, try again, then grab the inArgs and outArgs values from the thread log and see if you see some more detailed information.

Regards,

Kyle

Jason_Smith

Try this instead:

DocumentManagement.StringAttribute attr1 = new DocumentManagement.StringAttribute();

attr1.DisplayName = "Test field 1";

attr1.Required = false;

attr1.Searchable = false;

attr1.MaxValues = 1;

attr1.MinValues = 1;

attr1.DisplayLength = 32;

attr1.MaxLength = 32;

dm.CreateCategory(dmOTAuth, 2004, categoryNm, "" , new DocumentManagement.Attribute[] { attr1 }, null );

Let me know if that helps.

Thanks.

Jason_Smith

I ran your sample code posted and now see the issue. There is a bug when trying to use the parent Attribute object instead of one of its child objects (ie. StringAttribute, IntegerAttribute, etc.) which causes the failure on the server.

I've logged this bug under LESAPI-1431. The fix for the bug will just simply provide better error handling for passing in the invalid object. For this to work you'll have to change your code to use the StringAttribute object instead of the parent Attribute object as I suggested above.

Thanks.

Guy_Turton

Yep, that did the trick. Thanks for your help!