How to get the data which are not successfully inserted in database?

HI Sudipta Biswas

Do you want to say, when you are persisting an array of CDT to the database using smart service function, only few rows are being inserted and rest all are getting fail? Are you facing this issue? If so, did you try inspecting the error root cause?

And if so, then following points you should consider here:

1. Here difference will not able able to help you, because before persisting the data, your Primary Key values will be null but after persisting, each successfully persisted row will hold their Primary Key Value, means it's not the same, and every single row will be treated as different (irrespective of whether that row was successfully persisted or not).

2. You need to manually check the error root cause (e.g. some fields are marked as Not Null but you are trying to push null values for those fields in few of the indexes of this CDT || your content exceeding the max number of character limit etc..) and then you need to perform some sort of validation for making sure that the content is not exceeding the max character count. Also either alter the column to nullable else make sure, a column shouldn't hold Empty values and other additional checks (if any).

As per my understanding, this is something you need to take care before persisting the data into the database. So that we can avoid the partial failure.

Hope this will help you in analysing & debugging this issue.

HI Sudipta Biswas

Do you want to say, when you are persisting an array of CDT to the database using smart service function, only few rows are being inserted and rest all are getting fail? Are you facing this issue? If so, did you try inspecting the error root cause?

And if so, then following points you should consider here:

1. Here difference will not able able to help you, because before persisting the data, your Primary Key values will be null but after persisting, each successfully persisted row will hold their Primary Key Value, means it's not the same, and every single row will be treated as different (irrespective of whether that row was successfully persisted or not).

2. You need to manually check the error root cause (e.g. some fields are marked as Not Null but you are trying to push null values for those fields in few of the indexes of this CDT || your content exceeding the max number of character limit etc..) and then you need to perform some sort of validation for making sure that the content is not exceeding the max character count. Also either alter the column to nullable else make sure, a column shouldn't hold Empty values and other additional checks (if any).

As per my understanding, this is something you need to take care before persisting the data into the database. So that we can avoid the partial failure.

Hope this will help you in analysing & debugging this issue.

Hi,

My understanding is that the write to datastore entity is executed as a single transaction, therefore if insert fails for even a single row then the entire transaction is rollled back which means there is no scenario of a partial commit.

Isn’t that how it works? Or I’m I missing something?

Yes, in fact that's what my understanding is. But also i am curious about the Auto Commit feature of DB.

As per my understanding, this Smart Service/function should be setting the autocommit to false upon startup and upon successful operation they would be committing the transaction. And hence we should not expect partial commit here.

Happy to be corrected by the practitioner, if i am wrong!

Hence, curious to know, Sudipta Biswas are your facing this partial commit issue?

I am not getting partial commit issue, as sunilz said its about single transaction. Either all the fields of the records are getting written or the total row is failing to get written. I want to get the records which are failing.