The information in this article applies to:
Product: Metastorm BPM
Version: 7.5.1 and later
Issue
A Failed to commit action error is generated when a custom variable is updated directly in the database. In the Windows application event log, the following error is seen for SQL Server:
ErrorCode: '-2147217864' Description: 'Row cannot be located for updating. Some values may have been changed since it was last read.' Source: 'Microsoft Cursor Engine' SQL State: '' NativeErrorCode: '32'
For example, in a map named Map1 with a variable Text1, the following code is executed at an action: %ExecSQL("Update Map1 Set Text1 = 'A' Where eFolderID = '%folderid'").
Note that the variable being updated must be on the form associated with the action.
Resolution
- Although this may have worked in previous versions of Metastorm BPM, using SQL to directly modify Metastorm tables, including custom variable tables, has always been unsupported. Only the Process Engine should update these tables. This can be done through variable assignments in expressions and scripts.