Support for Database Transactions

Data integrity is insured during database transactions.

To ensure data integrity Aurea CRM.Web automatically uses transactions when:

  • creating/updating records in Expand view
  • updating records List view
  • editing multiple records
  • merging records (companies, persons).

Although not recommended, transactions can be deactivated (via the useTransaction input argument) when merging records. For further details, see Merging Companies and Persons.

Note: If records were created or changed with the option AddNewCatalogValues = true, new catalog values are created by design even if the transaction is rolled back.

Sometimes when saving records, a failed insert operation might roll back the entire transaction. To prevent such situations you might want to disable the database transaction mode. To prevent a save operation in an expand page, from being in transaction scope set the url parameter disableTransaction=true and append it to an expand url. This prevents rollback on a database save operations in case of any failures. See the following example:

crm/expand?uid=FI%3Bx0000000100000001&mode=Show&infoAreaId=FI
&_action=A_Expand&disableTransaction=true

In addition, methods for server-side add-on programming (BeginTransaction, CommitTransaction, RollbackTransaction and IsActive) are available.