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; } } }

Category attribute non editable after inserting null

Jordi Masip

Hi,

We developped a framework sending requests to cws and we realized a problem after informing a category attribute with a null value. After this update, we verified that category attribute field was showed as non editable when this attribute was displayed accessing to corresponding associated folder.

In order to avoid it, we decided to substitute null value by a blank. Then, this attrubte was displayed as editable. However, it is a problem as this attribute is computed as informed by the system when really it is should be computed as empty.

Below you can see code portion used for informing a value to the attribute (one of them can be null):

if (dataValue instanceof StringValue) {

log.debug("DataValue {} {} es StringValue", dataValue.getDescription(), dataValue.getKey());

log.debug("DataValue StringValue con valor {}", value);

StringValue strValue = (StringValue)dataValue;

strValue.getValues().clear();

strValue.getValues().add(value);

}

Any advices?

Find more posts tagged with

Comments

Todd_Martindale

I am having this same issue. Anybody have an idea how to resolve it?

Thomas Werry

Having the same issue. I've logged a call with support re this - we can reproduce on both CS10 and 10.5.

We're using CWS on IIS. Our software is C#.

We can also recreate the issue using the standard LLTreeView sample application (steps below) Add a comment on a document with a category, update it and it entirely removes any blank string attribute fields from the category tab. Any attributes in the category that are ‘set’ with a value are retained.

Looking in the database table LLAttrData it’s also removed the row for that attribute.

Oddly the LLTreeView sample doesn't even look at the category - we're simply updating the basic node properties, but the act of 'round-tripping' the node and updating it seems to delete the attributes.

I only have an issue with string values. (Set integer values to 0 seems to work ok - but setting string to anything doesn't work - setting it to a 'space' (e.g. " ") it works - but of course a TKL attributes where a empty string isn't valid value in the lookup list it will fail!). More importantly I get the issue just opening a node then re-saving it - the LLAttrData database table row and control for blank attributes is removed entirely.

Below are my steps to reproduce this issue using the current C# LLTreeView sample, unchanged:

1. Create Category with an attribute (with a String value, a Text:Popup, and a Text:Table Key Lookup - all optional)

2. Apply that category to folder to inherit to folder contents

3. Create a couple of documents via CS10 web interface

4. Set the attributes on one document, leave other document with blank attributes (they show "" in CS web interface or are blank)

5. Using LLTreeView edit the comments on both documents

Someone must have a work-around for this issue?

The only work-around I've thought of is to add " " (a space) to the lookup lists and use that instead to set it to blank (but we won't get the '' prompt in browser.

I did also wonder if removing the 'blank' attibutes from the nodes metadata before updating the node might also work? (Not tried this yet - but having to visit any categories applied to a node and remove any unset attributes would be a pain)

Tom

AKropp

Hi folks,

I picked up Todd's support ticket regarding this and after a quick in-house repro have determined that the behavior is a bug, which I just finished logging moments ago as LESAPI-1820.

No particularly elegant workarounds that I can see at this point. Either use CWS to set some non-null value back on the affected attribute, or a complete remove/re-add of the category.

Strongly recommend anyone affected open a support ticket so we can add your reports to the bug.

Thanks,

Alex

AJ Gorczyca

I did create a ticket about this same issue and ended up being directed to this existing bug. Is there a way I can find information about it's progress / get some sort of idea on when the hot fix might be released?

David Henshaw

Hi,

If an OpenText rep/consultant is monitoring this thread would it be possible to get an update on ETA for fix?

Kind regards,

David H

INACTIVE_Vlad_Kozlov

I've found a workaround for this issue. It seems that the values in the SegmentBlob column in the LLAttrBlobData table are missing a question mark between the curly brackets when the node is updated using the web services.

Correct null value, when the node is updated using the UI:

A<1,?,{23241,2}=A<1,?,'CustomID'=0,'ID'=1,'Values'={A<1,?,3=A<1,?,'ID'=3,'Values'={?}>,4=A<1,?,'ID'=4,'Values'={'abc'}>,5=A<1,?,'ID'=5,'Values'={?}>,6=A<1,?,'ID'=6,'Values'={?}>>}>>

Incorrect null value, when the node is updated using web services:

A<1,?,{23241,2}=A<1,?,'CustomID'=0,'ID'=1,'Values'={A<1,?,3=A<1,?,'ID'=3,'Values'={}>,4=A<1,?,'ID'=4,'Values'={'abc'}>,5=A<1,?,'ID'=5,'Values'={}>,6=A<1,?,'ID'=6,'Values'={}>>}>>

Note the missing question marks in the second snippet.

There are two potential workarounds:

1. After each node update, run a SQL update query to replace all '{}' with '{?}' on the latest version of the affected node:

update LLAttrBlobData
set SegmentBlob = replace(SegmentBlob, '{}', '{?}')
where id = @nodeId
and VerNum = (select MAX(VerNum) from LLAttrBlobData where id = @nodeId)

2. Replace the '{}' with '{?}' in oScript, before the value is saved to the database:

This part is handled in:

Core -> LLIAPI -> AttrObjects -> AttrData -> _DBPutAttrBlobData

add:

blobDataRec.segmentBlob = Str.ReplaceAll(blobDataRec.segmentBlob, "{}", "{?}")

right after variable declaration.

I have run multiple tests using the first approach and it seems to solve the issue. However, updating the database directly is a matter of last resort and is not recommended by any means. But, as far as I know there are currently no other solution at the moment.

Please chime in if you see potential issues with this approach or if you have a better solution.

Riten

Technically if you have empty value ({}) in LLAttrBlobData and you replace it with Null ({?}) by database table updates, you are missing one critical information in LLAttrData table. In general, the empty value in LLAttrBlobData means there is no corresponding row for that attribute in LLAttrData table. As you have mentioned, direct database updates are not supported.

There is one custom module that I’d created that resolves such rows that are now left in the system without any option to edit that attribute via user interface. Let me know if you are interested.

Thanks,

Riten

From: eLink Entry: Content Web Services Forum [mailto:otdncontentwebservices971forum@elinkkc.opentext.com]
Sent: Monday, February 02, 2015 4:55 PM
To: eLink Recipient
Subject: Category attribute non editable after inserting null 3

Category attribute non editable after inserting null 3

Posted byvkozlov@gennet.com (Kozlov, Vlad) On 02/02/2015 04:50 PM

Correct null value, when the node is updated using the UI:

A<1,?,{23241,2}=A<1,?,'CustomID'=0,'ID'=1,'Values'={A<1,?,3=A<1,?,'ID'=3,'Values'={?}>,4=A<1,?,'ID'=4,'Values'={'abc'}>,5=A<1,?,'ID'=5,'Values'={?}>,6=A<1,?,'ID'=6,'Values'={?}>>}>>

Incorrect null value, when the node is updated using web services:

A<1,?,{23241,2}=A<1,?,'CustomID'=0,'ID'=1,'Values'={A<1,?,3=A<1,?,'ID'=3,'Values'={}>,4=A<1,?,'ID'=4,'Values'={'abc'}>,5=A<1,?,'ID'=5,'Values'={}>,6=A<1,?,'ID'=6,'Values'={}>>}>>

Note the missing question marks in the second snippet.

There are two potential workarounds:

1. After each node update, run a SQL update query to replace all '{}' with '{?}' on the latest version of the affected node:

update LLAttrBlobData
set SegmentBlob = replace(SegmentBlob, '{}', '{?}')
where id = @nodeId
and VerNum = (select MAX(VerNum) from LLAttrBlobData where id = @nodeId)

2. Replace the '{}' with '{?}' in oScript, before the value is saved to the database:

This part is handled in:

Core -> LLIAPI -> AttrObjects -> AttrData -> _DBPutAttrBlobData

add:

blobDataRec.segmentBlob = Str.ReplaceAll(blobDataRec.segmentBlob, "{}", "{?}")

right after variable declaration.

Please chime in if you see potential issues with this approach or if you have a better solution.

[To post a comment, use the normal reply function]
Topic:	Category attribute non editable after inserting null
Forum:	Content Web Services Forum
Content Server:	Knowledge Center

Kyle_Swidrovich

Hello all,

Just an FYI… The fix for the root cause of this issue is targeted for the 2015-03 update for Content Server.

Regards,

Kyle

INACTIVE_Vlad_Kozlov

Thanks for the insight Riten! Sure, it would be great if you could share your fix

CIBC Illymeister

Kyle,

We have upgraded from CS10 sP12 to CS16.0.1. In CS16.0.1, we are now experiencing this issue (we did not experience this in CS10). Has this bug been fixed? or is this an outstanding issue in CS16?

I will also open up a support ticket for this.