hi @ChaMylesC 

Are you passing a value for Objversion (:p2 shown below)

Hi Paul,

Yes, I am passing a value for the objversion. I’m getting it directly from a select statement.

  action_ := 'DO';

 objkey_ := '0F5D128C1A144BA0B012606AAFABDB49';

  SELECT CHANGE_CONTROL_BOARD_ROLE_CLT.ROWVERSION into objversion_
  FROM CHANGE_CONTROL_BOARD_ROLE_CLT
  WHERE CHANGE_CONTROL_BOARD_ROLE_CLT.ROWKEY = objkey_;
  

--Update Record
 attr_ := 'CF$_NAME' || chr(31) || '350109DCDE1F4A298F4F50608577D5DB' || chr(30);
 CHANGE_CONTROL_BOARD_ROLE_CLP.Modify__(info_, objkey_, objversion_, attr_ , action_);
 attr_ := '';
 

You cannot just use rowversion as it is.  You have to convert it Date to text, comme ça:

to_char(rowversion,'YYYYMMDDHH24MISS')

Hi Paul, 

I actually found out that I should be using the CLV table (the view) . to get the objversion, and objkey, and apparently the objid_. I can use it as is when getting it from the view.

Also, I found that the modify__ and remove__ methods, use the objid_ attribute not the objkey_ attribute. I’m not sure why the modify method asks for object key when the object ID needs to be passed. It’s a little confusing.

yes, in general it’s better to query the view for security reasons; unless doing so leads to poorer performance.

Also in general, these methods use objid and objversion; it’s just that in the CLT case we use the rowkey as the objid.

Thanks for the help Paul! So the rowkey is the objid for CLT tables? What is the rowid value for then in the CLT tables.

ROWID is an Oracle framework column, not something IFS put there.

For standard tables we use(d) ROWID as OBJID, and used that as the alternative key for updates and deletes.  Rowkey/objkey (on standard tables) is an IFS column that was introduced later, to support various requirements but principally custom fields.

For « insert reason here » when IFS introduced Custom LUs it was decided that the OBJID would be read from the ROWKEY, not the ROWID.  Hence, objkey and objid are the same.

I don’t know the reason, but probably to make it more IFS-y and less Oracle-y.

Thank you for the explanation Paul, that is going to be great information going forward for me and my team. Thanks!

I’m only guessing, since I’m not an IFS employee. One good reason is that it reduces vendor lock-in. Even if IFS stays with Oracle Database, moving to a more vendor-neutral architecture would improve their ability to negotiate with Oracle Corporation. Using ISO-compliant SQL increases the talent pool for employee candidates, partners, and customers.

(This is why I think everyone should use COALESCE instead of NVL, for example.)

Thanks Paul. This definitely works. I just wanted to add that you can also use the view to get the OBJKEY and OBJVERIONS for custom LU tables.

Method 1: use the CLT (table) view to obtain the ROWKEY and ROWVERSION.

SELECT ROWKEY, to_char(ROWVERSION,'YYYYMMDDHH24MISS') into objkey_, objversion_

  FROM TABLE_NAME _ROLE_CLT

  WHERE TABLE_NAME _CLT.ROWKEY = ‘the rowkey for this record’ );

Method 2: use the CLV (view) to obtain the OBJID and OBJVERSION.

  SELECT OBJKEY, OBJVERSION, into objkey_, objversion_

  FROM TABLE_NAME _ROLE_CLV

  WHERE TABLE_NAME _CLV.OBJKEY= ‘the rowkey for this record’ );