Transactions are implemented throughout Microsoft Dynamics GP. In most cases, integrating products won’t need to deal with transaction issues. If your integrating application registers a trigger that is activated within a Microsoft Dynamics GP transaction, any table operations your script performs will become part of the transaction. If the transaction is committed, your database operations will be committed. If the transaction is rolled back, your database operations will be rolled back.
If you use transactions in your trigger processing procedures, be sure to verify that no transaction is in progress before starting a transaction. Otherwise, an exception will be thrown indicating that the transaction level has changed, since a transaction was already in progress.