Support Article
Posted transaction ID for frame pyWorkPage does not match
SA-17168
Summary
A Transaction mismatch error is generated in the log file, and the command fails, when submitting a form after using the "attach-a-file" control from a modal window.
Error Messages
2015-11-20 18:03:41,862 [ WebContainer : 10] ( mgmt.base.ThreadUITransaction) ERROR - ERROR: posted transaction id '9143f677524349fe81f16da214216fec' for frame 'pyWorkPage' DOES NOT match record '6f1c6a4cbb8b60b138adc9207a85d32b'
Steps to Reproduce
- Launch a flow action in a modal window.
- From the modal window, attach a file using the FilePath control.
- Close the Modal window.
- Submit the originating form.
Root Cause
An issue in the custom application code or rules. Attaching the file performs a commit which updates the Transaction ID on the server without refreshing the content in the background window. As a result, the next FinishAssignment uses the previous (stale) Transaction ID, and the command fails.
Resolution
Perform the following local-change:
Instead of using the FilePath control, use the "Attachments" icon provided through the interface:
This correctly handles refreshing the background window so that no subsequent error occurs.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.