on 09-27-2015 3:04 PM
Hello experts ,
If there is any problem in any order or notification, unless it is removed it does not transmit the other data .
How this can be resolved?
Regards
Manus
Hi Manish,
you can skip transactions on the client if you do the following:
enableTransactionFailureHandling=False
failedTransactionFilenameFormat=%{userid} %{transaction_name} %{date} %{time}-%{count}.xml
failedTransactionsQueue=FailedTransactionsQueue
Also create a folder named "FailedTransactionsQueue" in your deployment.zip. Do a new deployment and restart your agentry app.
Next time you get an error, the client will ask if you want to "continue" or "stop". If you continue, the data from the transaction will be stored as an xml file on the server where your Agentry app is deployed in the folder "FailedTransactionsQueue". The sync will continue. If you stop the sync will be stopped and you can change the transaction.
We're using this approach at several customers using Inventory Manager and Work Manager and it work well.
Regards,
Michel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is no way to skip one transaction (on the client side) if there is an error. The reason for this there may be an transaction that would needto be sent that is the first one needed to be sent first.
What you can do is look at the Error handling which can post the data into a temp table in the backend if it errors, so the client can remove the transaction and keep on the pocessing.
Stephen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.