Hi @Demah , When the SMO is created K2 will detect the Primary key on the table and then make that required for the Update and Delete methods. 

When you edit the SMO, you will not be able to change these. 

Is there a reason why you would not use ServiceID as your primary key?

 

Hi @Demah , When the SMO is created K2 will detect the Primary key on the table and then make that required for the Update and Delete methods. 

When you edit the SMO, you will not be able to change these. 

Is there a reason why you would not use ServiceID as your primary key?

 

 

Thank you, Deon, for your replay!

I solve it by setting (ServiceID & RelatedDeptID) as key of the table and discarded ID column.

the reason of I don't use ServiceID as your primary key, because the ServiceID alone is not unique in my case.

When ever you are creating the smartobject please dont tick mark as its required by you as its a autonumber so dont do this after doing this your problem will be solved few days back was also receiving the same error