Sync Records Smart Service - full sync

Hi

How do you use Sync Records Smart Service to fully sync a record type that was just modified by a back end stored procedure

My case is new data comes in daily in CSV files - which gets uploaded into a set of temporary tables

After this a stored procedure inserts them into the main tables that are connected with the record types.

As of now we are syncing these record type manually from the web page

I though this smart service would have an option to do a full sync, but it needs the IDs of the record types to sync - well these are unknown since they were just inserted by the stored procedure in DB so not available yet.

Do I need to come up with another data base query to retrieve the new ID - form the database?

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Senior Developer

    I'm revisiting this topic once more, and I see we still face the same challenges.

    The problem is getting the updated/inserted ids back, if for example we had more ids than the capacity of the result set of the stored procedure smart service. 

    I think setting a timestamp, and later using some classical Datastore/CDT query to retrieve just those ids of interest, and then, loop to re-sync should be the approach, but that is much work for such a trivial or straightforward necessity. 

    Or shaping your stored procedure to work with 1k record batches, and so on, but that just adds more complexity to achieve an "on demand" synchronization. 

Reply
  • 0
    Certified Senior Developer

    I'm revisiting this topic once more, and I see we still face the same challenges.

    The problem is getting the updated/inserted ids back, if for example we had more ids than the capacity of the result set of the stored procedure smart service. 

    I think setting a timestamp, and later using some classical Datastore/CDT query to retrieve just those ids of interest, and then, loop to re-sync should be the approach, but that is much work for such a trivial or straightforward necessity. 

    Or shaping your stored procedure to work with 1k record batches, and so on, but that just adds more complexity to achieve an "on demand" synchronization. 

Children
No Data