GET the constituentID directly from RE7 (without latency)

We are developing a synchronization process between Microsoft Dynamics and NXT. In that process IDs from NXT and Dynamics are exchanged after new contacts (From Dynamics to NXT) or constituents (from NXT to Dynamics) are added, in order to be able to synchronize bio-, address, commpref, and other information.

After a new DYN contact is PUT to the NXT API it is added directly to RE7, which is great. But after that, we need to GET the NXTID back to write it to Dynamics. The GET from NXT will reflect the information that is last synced, not directly from RE7.

Now we have to wait 70 minutes minimum to be sure the update to NXT has been run. 

Is it not possible to make an endpoint that GETs (only) the constituentID directly, without latency, from RE7?

  • Guest
  • May 15 2017
  • Already exists
Constituent API
  • Attach files
  • Deleted User commented
    June 26, 2017 15:00

    Hi Martin,

     

    When you POST a new constituent, you should get the constituent ID back immediately in the body of the response. That ID can be used immediately in conjunction with the GET Constituent endpoint to retrieve that information from the transactional database. Once you have that ID, you will also be able to perform PATCH operations on that constituent, regardless of if they have been updated as part of the ETL process for the Constituent list or not.

     

    Let me know if that helps. Because this functionality does already exist (ie: returning the constituent ID on creation), I will be closing this idea as "Already Exists". Please post in the Developer Community if you have any follow up questions.

     

    Thanks,

    Halley

    ×

    Attachments Open full size

  • Joseph Gordon commented
    May 26, 2017 20:28

    Hi,

    I to am sync data too.  I think the latency (which can be too long) is only in the GET of the lists.  I am able to retrieve the constituent information right after a PUT.  Also, the PUT to the 'constituents' returns the Constituent ID in the response to the call and is labeled "id".  I then call get GET of the 'constituents' with that id to obtain the 'lookup_id' for that constituent.

    Thanks,

    Joseph Gordon

    ×

    Attachments Open full size

  • Guest commented
    May 23, 2017 07:08

    I now have a latency of 249 minutes!!

    Totally unacceptable

     

    snip_2017052309...
    ×

    Attachments Open full size

Related ideas