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

DM_SYSOBJECT_E_VERSION_MISMATCH

Karthik_Juttu

Hi,

I have the code mentioned below,

IDfSysObject sysobj = (IDfSysObject)sessn.getObject(new DfId(strObjectId));//attach the lifecycle to PublishIDfSysObject policyObj = (IDfSysObject)sessn.getObjectByQualification("dm_policy where object_name like 'ABC_DLC'");sysobj.attachPolicy(policyObj.getObjectId(),"Publish", "");//set the ab_publish = 1 for ready to publishsysobj.setInt("ab_publish",1);sysobj.save();I'm getting DM_SYSOBJECT_E_VERSION_MISMATCH error in sysobj.save(). It is working fine for some objects and for some objects it gives the error.Thanks in advance,Regards,Karthik

Find more posts tagged with

Comments

awille

Sounds like timing issues.....
Quick guess here, are you using lifecycle actions which contain a save action?

regards,

Alex

Karthik_Juttu

No. It does not contain any save action.

DCTM_Guru

Fetch the object again after the attach. The lifecycle attachment is a separate transaction, so the i_vstamp changes afterwards. When you try to save the object, content server notices that the i_vstamp from your original fetch is no longer the same when you try to save.

Karthik_Juttu

Thanks for the reply Johnny.

This code works fine for some run and some times shows the error message.

DCTM_Guru

If you do what I suggest, then you shouldnt have problems ANY time.

Karthik_Juttu

Thanks for your help Johnny