Mark,
That's great news, we'd definitely appreciate this feature getting implemented.
I don't think we'd be too picky about when the timer data gets synced. On case closure would work fine for our use. We'd only be creating metrics / dashboards in our BI tool based on closed cases, so we wouldn't have a need for the timer data to get synced before that.
Thanks for the info Mark!
------------------------------
Liam Mahoney
------------------------------
Original Message:
Sent: Fri April 01, 2022 08:17 AM
From: Mark Scherfling
Subject: Data Feeder Timer Information
Hi Liam,
We've had this requirement on our backlog and will look at reprioritizing it. One question is: at what point should the timer information be included: ongoing when changes occur to the case or when the case is closed. It would seem that when the case is close makes the most sense. But I'd like to know how you'd like to have this capability implemented.
Regards,
Mark
------------------------------
Mark Scherfling
Original Message:
Sent: Thu March 31, 2022 10:11 AM
From: Liam Mahoney
Subject: Data Feeder Timer Information
All,
We are working on implementing the data feeder integration with our production environment. I ran the feeder and our SQL server is now populated with data. However, one of our biggest use cases is to use data from the timer fields (data retrieved from the `POST /orgs/{org_id}/timers` endpoint). It doesn't appear to me that this information is available within our SQL server.
Is there a way to get this timer data synced into our SQL server through data feeder?
Thanks,
------------------------------
Liam Mahoney
------------------------------