We need the list api's to include the time that it was updated

When you ask for a list (e.g. ConstituentList, etc) we need to know when this list was updated.  When I run a list in NXT it has at the top the number of minutes since the list was updated.  There are some processes (such as add new records)  that you do not want to run unless the list was updated since the last time the process was run.  It would be best if we had the time that the list was updated and possibly the current time on the server return as a parameter in the json with the list. 

  • Joseph Gordon
  • Apr 13 2017
APIs
  • Attach files
  • Guest commented
    May 15, 2017 11:12

    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 information. After a new DYN contact is PUT to NXT (actually it is added directly to RE7 with the API) 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 (unfortunately). 

    Now we have to wait 70 minutes minimum to be sure the update to NXT has been run. We would rather 'ask' NXT when the last sync has been, so we can then react on that.

    Hope you understand.

     

    Greetz

    Martin

    Attachments Open full size
  • Joseph Gordon commented
    April 28, 2017 18:06

    I have a data sync process that adds constituents, but it pull as list to see if they are there first.  If you run it again before the list is refreshed, it see them as needing to add again.  I would like to stop (or at least warn) the user if the are running it again before the list has been updated.

    Thanks

    Attachments Open full size
  • Deleted User commented
    April 27, 2017 14:14

    This is a good suggestion. We will start looking into it.

    Could you give me some information about what your use case is here? Do you intend to surface the minutes since last refresh to end users of your application? Or are you leveraging it for figuring out when automated data syncs should occur? Or something else entirely? I'm not sure I entirely understand the POST scenario that you alluded to.

    Thanks,

    Halley

    Attachments Open full size

Related ideas