Update Version Metadata

Hakan_Colak

Hi,

I want to upgrade the metadata of the document's old version.Like this,

OpentextDoc.Version vs = new OpentextDoc.Version();

vs = docClient.GetVersion(ref otAuth, 1775486, 1);

vs.Metadata.AttributeGroups = new AttributeGroup[] { categoryTemplate };

try
{
docClient.UpdateVersion(ref otAuth, vs);
}
catch (Exception e)
{

Console.WriteLine(e.Message);
}

However I get no error message nor It changes anything.Can you help please?

Find more posts tagged with

Comments

eLink User

I think the metadata on a object is allowed to be changed only on the highest or current version so even if you supply a version code will ignore it.AFAIK the immutability is actually put by OT but some other programming interfaces did not obey that rule.You may want to ask OT for whether what I am saying is true and see if your qn is a valid one and probably you can write a patch or override to change it.

..appu appnair appunair

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

On Sat, Dec 26, 2015 at 6:48 AM, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

Update Version Metadata Posted byColak, HakanOn 12/26/2015 07:46 AM

Hi, I want to upgrade the metadata of the document's old version.Like this, OpentextDoc.Version vs = new OpentextDoc.Version(); vs = docClient.GetVersion(ref otAuth, 1775486, 1); vs.Metadata.AttributeGroups = new AttributeGroup[] { categoryTemplate }; try
{
docClient.UpdateVersion(ref otAuth, vs);
}
catch (Exception e)
{ Console.WriteLine(e.Message);
}However I get no error message nor It changes anything.Can you help please?
[To post a comment, use the normal reply function]
Forum: Content Web Services Forum
Content Server: Knowledge Center

Kyle_Swidrovich

Appu is correct.

In particular, your code is trying to modify category data on non-current versions.

The UI restricts you from doing so as does the underlying logic that the Content Web Services API makes use of.

This behaviour is intentional and has been like that for years (I believe since version 9.0) to preserve the concept of metadata as a matter of record on old versions.