Skip to Content
avatar image
Former Member

Agentry duplicating transactions during transmit

Hi Experts,

We have an issue on avoiding duplication of records due to same Update transaction getting triggered.

When a transmit is triggered calling a transaction with Update step but wifi is not available, the transaction is getting queued on the client. When the user hits transmit again, a new instance of the same transaction is triggered causing a duplication of records sent to the backend. The number of duplicates depends on how many time the transmit was triggered before a successful transmit happens. There are no errors in the client or in the backend, but only the wifi connection prevents the successful transmit of the transaction.

We tried to use "Merge transaction" but it does not work for same Edit transactions.

How do we prevent or overwrite the transaction in the queue with the same key?

Thanks!

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • Jan 08, 2015 at 07:38 PM

    Hi Parker,

    Can you please elaborate on the Merge Settings that you did?

    Also,When configuring the Update Step did you choose "Delete client object" or "Replace client object" for the Response to client Field ?

    Selecting one among these two will avoid creation of duplicates in the client.

    Thanks,

    Deepak.M

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Judith,

      Somehow this issue is not happening using our actual Windows devices. We noticed this issue when using the simulator. I suggest you check your merge settings and test in a controlled scenario.

      Thanks!

  • Jul 16, 2015 at 07:18 PM

    John or Judith,

    Judith said: "We are facing the same issue. Our reponse to client is set to 'Delete client object' Have you found a solution/workaroud for this?"


    Our answer:


    We have received issues tied to transmits that can cause this problem on certain Agentry client versions. This will depend on your Agentry SMP 2.3 or 3.0 versions. We believed we have improved the transmission capability of the Agentry client when the user press the transmit button to prevent this problem from occurring.

    I believed that there was at one point an SMP 3.0 Agentry bug number that tracks this (tied to a transmit hanging or the window pop up got stuck and the user had to press transmit again thinking that the transmit didn't go through the first time - this causes the duplication of transaction) - Judith you may confirm if this is your issue.

    Our suggestion is to try to use the latest Agentry SMP 3.0 SDK client at best. If your version is the latest then the bug was not properly address in this version and may be coming out on newer versions.

    You may share your Agentry client version for reference.

    Best Regards,

    Mark Pe
    SAP Senior Support Engineer (Mobility)

    Add comment
    10|10000 characters needed characters exceeded

    • Judith,

      The next strategy is use the later version of the server/client to make sure yours work. I believe this was fix in newer versions. Our current versions are in the SP8 - you may want to try to see if you can get the better clients.

      Best Regards,

      Mark Pe
      SAP Senior Support Engineer (Mobility)

  • Jul 17, 2015 at 06:43 PM

    SAP Work Mgr - Duplicate transactions get created if Transmit fails to connect to Server. Please take look at the following SAP Note for SAP WM 6.1

    http://service.sap.com/sap/support/notes/2151097

    Add comment
    10|10000 characters needed characters exceeded