Skip to Content
avatar image
Former Member

Sender Rest Polling - Duplicate Detection


I am consuming an Odata service via GET method (JSON payload) with REST polling at the sender side . It keeps polling the same record for every polling interval and creates message in PO.

There is no mechanism at the sender side to archive or delete the data once read. Only new record will replace the old record and there is no frequency information at which the new record will be created.

I tried using Duplicate detection specifying the JSON element/path. It doesn't identify both JSON element or path.

Kindly help how to use this duplicate detection option to avoid reading the records multiple times.


Sudarvizhi P

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Aug 14, 2017 at 12:27 PM

    Basically, duplicate handling should work fine in your sender REST polling CC. Make sure you are using correct parameter to detect duplicate data.

    If there is no provision in your REST data provider to use incremental token then I will suggest you to change this interface from async to sync.

    I believe in your case it is REST Service -> PI -> ECC.

    Make it like so that one outbound proxy will start the flow in some intervals then PI will send the request to REST service and eventually send back the response to ECC. ECC will check for duplicate data and update the table accordingly.



    Add comment
    10|10000 characters needed characters exceeded