Vernum 0 in LLATTRDATA for documents uploaded through LAPI/CWS

Content Server Version is 10.5 SP1 2016-12. When we are uploading documents through CWS or documents from Kofax to Content Server, the uploaded documents are having Vernum 0 entry in LLATTRDATA table. This is causing duplication in reports.

This issue is not available if we are uploading documents via Browser UI.

Anyone had come across an issue like this ?

Find more posts tagged with

Comments

Kevin_Cartwright

Hi,

Yes we just applied 2016-12 to CS10.5 SP1 on July 16, 2017 and we have exactly the same scenario in production and in dev/test environments. We happen to use Kofax too, but any document added using CWS has both vernum 0 (zero) and 1 in llattrdata; so duplicate entries. Coincidentally or not, now the facet building queries are running 24x7 and we add documents and folders primarily for 18 of 24 hours every day. Facet queries are now (again) the largest consuming resource on our Oracle 11 RAC servers. We will have to update our custom livreports to provide a work around while we determine how to patch/fix this issue.

We have custom wrapper web services code which points to IIS/.NET CWS. I will change to use Tomcat java implemenation of CWS and I suspect this issue might not occur.

Thanks,

Kevin

Nizar Ghazal

Hi,

I've recently seen this come up, and this looks like a change in the behaviour for when you are setting metadata explicitly by passing it into CreateDocumentContext(), in Content Server 10.5 (2016-12) and later, like so:

contextID = docCli.CreateDocumentContext(ref otAuth, PARENT_ID, fileInfo.Name, null, false, metadata);

Don't add the metadata at this stage, to avoid getting a duplicate entry. Change it to:

contextID = docCli.CreateDocumentContext(ref otAuth, PARENT_ID, fileInfo.Name, null, false, null);

Keep in mind, that you did this, when you are performing the upload through the ContentService, like so:

objectID = contentServiceClient.UploadContent(ref otAuth, contextID, fileAtts, fileStream);

Make sure that you capture the ObjectID, and convert it into a long, so we can use it for setting metadata:

long tempObjID = Convert.ToInt64(objectID);

Take that tempObjID, and then pass in your original desired metadata using SetNodeMetaData();

docCli.SetNodeMetadata(ref otAuth, tempObjID, metadata);

Review the newly created object in LLAttrData, and notice that you only have a Vernum 1, and not a Vernum 0 and a Vernum 1.

I hope that helps!

Kevin_Cartwright

Actually this fix doesn't work for all scenarios because we have some folders which have metadata applied to it, hence making the metadata required, so can't add the document with no metadata and then apply metadata after. We will have to leave the code as is and figure out how to (sql script???) delete the extra rows in the llattrdata table.

Nizar Ghazal

Oh, yes, that seems a valid scenario.

I'll play around with this a bit, and see what's feasible.

Nizar Ghazal

Quoted Kevin Cartwright on 02/06/2018 08:42 AM:

Hi Kevin,

Not ideal, but you could try to set it so that you do not need to immediately fill out required metadata, via:

?func=admin.AttrRequiredValue

Uncheck "Document", and try again.

Thanks.

Kevin_Cartwright

Nizar,

This looks like a system level setting. It wold work for the my specific scenario, but it wouldn't work for other business cases where we have set metadata as required (and want it to be). Do you have an eta for the OT patch to fix this issue where we can add a document and include metadata at same time?

Thanks,
Kevin

Nizar Ghazal

Quoted Kevin Cartwright on 03/12/2018 07:53 AM:

Nizar,

Thanks,
Kevin

Hi Kevin,

I currently have no precise ETA on a fix for the issue, unfortunately. I anticipate that in the next 3-6 months, we will schedule something, but I cannot say for what version it may come to.

If you need to raise the issue with support, due to business requirements, please open a ticket, referencing LESAPI-2247, with a summary of the business case. We will attach it do the existing bug, highlighting your concerns.

Thanks.

Regards,

Nizar