Dirty Reads when using SQL Server

We are using SQL server as Outsystems' DB.

Do you know about the event that dirty reads occur when updating data?

And if so, is there any way to deal with it?

It would be very helpful if someone could tell me what to do.

Thank you in advance.

OutSystems provides built-in mechanisms for optimistic concurrency control. When updating or deleting a record, the platform automatically checks if the data has changed since it was read, thereby preventing dirty reads. This is controlled through the 'Version' attribute in entities.
If both manipulations come from within OutSystems simultaneously, and you do not validate the record through some sort of CRUD, you will still end up with one record taking precedence.
I would suggest implementing a CRUD for any record where this is a concern.

RAD Manage

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.