HI, I found out if there is update in API, kinetic will have 2 row request, is it necessary to follow this way and why? could we straight put the updated row when manual putting request for API?
More and more methods are now requiring 2 rows when calling them. This is to provide a “before image” to the method. If you expand the request you will notice that there is a key difference between the rows which is that one of them will contain a RowMod value (U, D). Some methods will still work if you only send a single row and some will not. If you are integrating externally you can also have a look at the UpdateExt method which exists on nearly every BO. UpdateExt will first check to see if the key fields for the BO you’re talking to in your dataset match an existing record. If they do not, a new record will be created. If they do, the existing record will be updated with the new information you have provided (assuming that the fields you are changing support being updated).
2 Likes
there are so many field have to restructure object, was thinking are they necessary to put previous row?
What’s your goal? What are you trying to build?
I am actually like to update inspection process but trying to figure out simple and easy maintain way to update row using kinetic api.