Process Mapping Logo

Process Mapping - Forums

Sharing 19 years of knowledge and experience

 
Metastorm BPM forums
Sign up Latest Topics
 
 
 


Reply
  Author   Comment  
Srinivas

Member
Registered:
Posts: 13
Reply with quote  #1 

We designed a procedure and at the particular action in a stage, we associated a form.

We are able to open the form at this particular action for the very first time and we are able to fill and submit the form without any errors. The folder is now progressing to next stage

When I come back to earlier stage (return action/ button where form is assigned to users todo list dynamically) and open the earlier form to edit the values, the form is getting opened with all the earlier filled details but when I click on submit button this time (either by modifying any field values or by leaving details unaltered), I am getting failed to commit action error.

I am unable to find any errors logged either in elog table or in designer logs in service manager. Request your help to debug and fix the error.


__________________
Thanks in Advance

Regards
Srinivas
0
Srinivas

Member
Registered:
Posts: 13
Reply with quote  #2 
I identified from the event viewer application log  that the error is
ErrorCode: '-2147217864' Description: 'Row cannot be located for updating.

Unable to sort it from here, any help is much appreciated.

__________________
Thanks in Advance

Regards
Srinivas
0
praxkan

Veteran
Registered:
Posts: 142
Reply with quote  #3 
That looks like an SQL error with Access database or ADO, some custom code that you've written. Check if your table has a primary key violation when you return for the second update
0
Srinivas

Member
Registered:
Posts: 13
Reply with quote  #4 
Quote:
Originally Posted by praxkan
That looks like an SQL error with Access database or ADO, some custom code that you've written. Check if your table has a primary key violation when you return for the second update


Thanks for your response.

There is no custom code written and the only proimary key on the table is efolderid.

I have observed on further analysis that the issue is due to presence of memo fields in the form. If we are removing memo fields in the form and performing the earlier action, it is working fine. Not sure if we have to remove the memo fields to fix the issue.


__________________
Thanks in Advance

Regards
Srinivas
0
praxkan

Veteran
Registered:
Posts: 142
Reply with quote  #5 
weird..never seen anything of that sort. What version of metastorm are you using?
0
Srinivas

Member
Registered:
Posts: 13
Reply with quote  #6 
Quote:
Originally Posted by praxkan
weird..never seen anything of that sort. What version of metastorm are you using?


Metastorm BPM Designer 7.6.0
Metastorm BPM Common 7.5.0
Metastorm BPM Utilities 7.0.0

__________________
Thanks in Advance

Regards
Srinivas
0
praxkan

Veteran
Registered:
Posts: 142
Reply with quote  #7 
ohok... I probably wont be of much help then, sorry. Never worked on 7.5.

My best guess is check the data type being generated for the memo field. Maybe designer 7.6 is generating a different type than what the engine/common (7.5) expects. Not really sure.


0
praxkan

Veteran
Registered:
Posts: 142
Reply with quote  #8 
check if this is relevant...

http://metastorm.processmapping.com.au/post?id=2154247&trail=
0
BMellert

Guru
Registered:
Posts: 688
Reply with quote  #9 
I know we has something similar, though not exactly the same, in V9.  I never encountered in V7, so I don't know if this applies.

You mention its the primary key.  How is the key defined?  If its a "true" key (such as a unique identity column) I'm not sure.  However, if the data elements are the key, or part thereof, and the value is changed somehow, this may be part of the cause.

We have this issue on V9 especially when deleting a row if a data key or part was changed.  It may not be quite what you are experiencing though.
0
KarlD

Avatar / Picture

Guru
Registered:
Posts: 113
Reply with quote  #10 
The error is about an update not finding a row to update.

My guess, and it is only a guess, would be that there is logic on the submit activity. On first submit do a create, after that do an update.

The create is working but the logic of the update isn't.

Does the row you are trying to update actually exist?

Are you perhaps modifying the data in some way before doing the create then not using the same modifications in the matching for the update?

You say this has something to do with a memo field. Is the field part of the update? What happens if you just replace the field with another, exactly the same purpose and activity but a new field?
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:


Create your own forum with Website Toolbox!