Question
1
Replies
1140
Views
Posted: May 31, 2016
Last activity: June 2, 2016
Closed
Solved
pzTransactionid and pxclientExchange
What values do the parameter pztransaction id and the property pxRequestor.pxClientExchange hold? And also when exactly do these change?
We are facing an attachment issue due to these properties in 6.3 sp1. Any response would be helpful.
Thanks,
Gaurav
Moderation Team has archived post,
Close popover
This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Hi Gaurav
Every time the client speaks to the server, it needs to provide a transaction id (pzTransactionID). Once a commit is made in the database, the server provides in exchange a new transaction id via the pxClientExchange so that going forward the client could use the new one as its transaction id.
I have a feeling you are running to an error like so "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'"
There are lots of PDN articles and mesh posts that discuss this topic.
You mention that you are facing an attachment issue in 6.3 sp1. Please take a look at this PDN link.
https://pdn.pega.com/support-articles/posted-transaction-id-frame-pyworkpage-does-not-match
Here are few others that talk about the error in detail:-
https://pdn.pega.com/support-articles/transaction-id-mismatch-data-ui-screen-not-getting-saved
Re: Posted transaction id DOES NOT match record?
Bhuvana.